Re: Spam Low: Re: Cost

+1 Wes.

A great example of the benefits of creating sub-types of established
Schema.org types - the ‘difficult to model’ use case has already been
handled in an established pattern.


Richard Wallis
Founder, Data Liberate
http://dataliberate.com
Linkedin: http://www.linkedin.com/in/richardwallis
Twitter: @rjw

On 18 February 2016 at 01:05, Wes Turner <wes.turner@gmail.com> wrote:

> http://schema.org/Offer
> + availabilityStarts
> + availabilityEnds
> + eligibleDuration
> * priceSpecification
> + priceValidUntil
>
> http://schema.org/PriceSpecification
> + validFrom
> + validTo
>
> ... so there would be multiple Offers for the same CourseOffering, IIUC.
>
> On Feb 17, 2016 6:10 PM, "Developer, SleepingDog" <
> developer@sleepingdog.org.uk> wrote:
> >
> > Hi all
> >
> > I think there is a case where a cost may be associated with (vary
> dependent upon) a date.
> >
> > For example, the W3CDevCampus courses may be launched with an “early
> bird” offer rate:
> > https://www.w3.org/blog/news/archives/5293
> >
> > Perhaps that is too difficult to model.
> >
> > Tavis
> >
> > > On 10 Feb 2016, at 15:19, Phil Barker <phil.barker@hw.ac.uk> wrote:
> > >
> > > Hello Alan,
> > > yes, you're absolutely right that cost can be very difficult.
> >
> >
>