Progress update, Feb - mid March [via Schema Course extension Community Group]

If the forming-storming-norming-performing model of group development still has
any currency, then I am pretty sure that February was the "storming" phase.
There was a lot of discussion, much of it around the modelling of the basic
entities for describing courses and how they relate to core types in schema (the
Modelling Course and CourseOffering & Course, a new dawn? threads). Pleased to
say that the discussion did its job, and we achieved some sort of consensus
(norming) around modelling courses in two parts
Course, a subtype of CreativeWork: A description of an educational course which
may be offered as distinct instances at different times and places, or through
different media or modes of study. An educational course is a sequence of one or
more educational events and/or creative works which aims to build knowledge,
competence or ability of learners.

CourseInstance, a subtype of Event: An instance of a Course offered at a
specific time and place or through specific media or mode of study or to a
specific section of students.

hasCourseInstance, a property of Course with expected range CourseInstance: An
offering of the course at a specific time and place or through specific media or
mode of study or to a specific section of students.
(see Modelling Course and CourseInstance on the group wiki)

This modelling, especially the subtyping from existing schema.org types allows
us to meet many of the requirements arising from the use cases quite simply.
For example, the cost of a course instance can be provided using the offers
property of schema.org/Event.

The wiki is working to a reasonable extent as a place to record the outcomes of
the discussion. Working from the outline use cases page you can see which
requirements have pages, and those pages that exist point to the relevant
discussion threads in the mail list and, where we have got this far, describe
the current solution.  The wiki is also the place to find examples for testing
whether the proposed solution can be used to mark up real course information.

As well as the wiki, we have the proposal on github, which can be used to build
working test instances on appspot showing the proposed changes to the schema.org
site.

The next phase of the work should see us performing, working through the
requirements from the use cases and showing how they can be me. I think we
should focus first on those that look easy to do with existing properties of
schema.org/Event and schema.org/CreativeWork.



----------

This post sent on Schema Course extension Community Group



'Progress update, Feb - mid March'

https://www.w3.org/community/schema-course-extend/2016/03/16/progress-update-feb-mid-march/



Learn more about the Schema Course extension Community Group: 

https://www.w3.org/community/schema-course-extend

Received on Wednesday, 16 March 2016 14:56:18 UTC