+1 This sounds like a quite reasonable possibility. Stuart On Mon, Feb 15, 2016 at 3:05 AM, Richard Wallis < richard.wallis@dataliberate.com> wrote: > > On 15 February 2016 at 11:01, Phil Barker <phil.barker@hw.ac.uk> wrote: > >> OK, I get the message that dropping CourseOffering is not an option. >> >> An alternative to reproducing all the Course properties in CourseOffering >> would be to mark up single offering Courses as both Course and >> CourseOffering, e.g. >> >> <div vocab=*MailScanner has detected a possible fraud attempt from >> "schema.org" claiming to be* "http://schema.org/" <http://schema.org/> >> typeof = "Course, CourseOffering"> >> > > A pragmatic approach to this worth considering maybe to make > CourseOffering a subtype of Course. That way all the properties of Course > would be available, if useful, when marking up a CourseOffering instance. > > ~Richard. >
Received on Monday, 15 February 2016 11:12:27 UTC