Replies: 5 comments 1 reply
-
|
I don't have a strong view on creating a super class for these two, but I do note that they currently have different super classes, which points to the different approaches taken in modelling them. One comment: timeToComplete and timeRequired are not equivalent. For example for a typical undergraduate degree the time to complete would be 4 years, but the timeRequired i.e. the time a student spent learning would be less (something like 1600 study hours?). I led the schema course extension community group, which added Course to schema.org. The wiki from the CG might be useful to you. That work is wrapped up now, and the group dormant, but feel free to reach out to me if you think I can help. |
Beta Was this translation helpful? Give feedback.
-
Got the point.
Thanks. Will review it. |
Beta Was this translation helpful? Give feedback.
-
|
This issue is being nudged due to inactivity. |
Beta Was this translation helpful? Give feedback.
-
|
Perhaps a slight tangent, but @philbarker do you remember why EducationalOccupationalProgram was not tagged as also being a subtype of https://schema.org/LearningResource ? |
Beta Was this translation helpful? Give feedback.
-
|
I don't recall it being discussed. IIRC the proposal came from Google, partly because they wanted something that didn't fit under the CreativeWork / Event super-class split of Course and CourseInstance. LearningResource is firmly a CreativeWork, not an Event; we have EducationalEvent for those. EducationalOccupationalProgram has properties like startDate dayOfWeek, which look more like EducationalEvent properties than LearningResource. |
Beta Was this translation helpful? Give feedback.
-
|
I'm going to convert this to a Discussion for now, as it doesn't seem immediately actionable. But we can keep talking here... |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I'm leveraging EducationalOccupationalProgam and Course to model the aggregate educational offer of a European University Alliance.
In the process I noticed that the two classes share a number of properties that could be conveniently factored to a common base class (something like
EducationalOfferorEducationalActivity), e.g.Other pairs of properties share a similar semantics and could be also merged/factored, e.g.:
Other properties currently specified only for
Coursecould be considered for factoring, e.g.:The availability of a common base class would improve semantics and reduce documentation/coding efforts.
Beta Was this translation helpful? Give feedback.
All reactions