- From: Developer, SleepingDog <developer@sleepingdog.org.uk>
- Date: Tue, 9 Feb 2016 23:30:36 +0000
- To: public-schema-course-extend@w3.org
Hi Phil Thanks for your clarifications. I am happy with your interpretations of my feedback, your recent wiki additions and with the Course and CourseOffering parent-child model proposed (+1). I guess if that is acceptable then the relevant properties of each will follow a similar pattern to existing schemas: Course would have things like qualifications and level; CourseOffering would have temporal/spatial/attendance-related properties. I will need to look existing schema.org properties. I have no strong views about the Intangible or CreativeWork decision. I guess that some courses could effectively be just (collections of) authored learning objects that someone could choose to take at any time or place, which could lean towards CreativeWork; but then again, some other courses could be more like participation in some kind of event (or series of events, maybe like driving lessons), which leans towards Intangible. I just don’t know (+0). Tavis Reddick > On 09 Feb 2016, at 13:02, Phil Barker <phil.barker@hw.ac.uk> wrote: > > Consensus seems limited at the moment to > - we need a schema.org type: Course > - there are abstract and concrete aspects of courses, i.e. the (abstract ) thing that is offered year after year and instantiations of it that run between set dates and at set locations (on- or offline) > > Open for discussion: > - should Course be a subtype of Intangible or CreativeWork > - is there a need for a separate type for the instantiation? > --if there is need, can we agree to call it a CourseOffering?
Received on Tuesday, 9 February 2016 23:31:40 UTC