-
Notifications
You must be signed in to change notification settings - Fork 825
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
We have CreativeWorkSeries but don't say how it relates to the earlier Series #1090
Comments
Pragmatically this sounds a better solution. A CreativeWorkSeries has many CreativeWork attributes associated with it that are not particularly relevant to Events (author, etc.) Properties of CreativeWork that were intended to enable EventSeries - I am presuming hasPart & isPartOf would need their range extending |
/cc @rvguha - is there any value in "Series" over and above having different kinds of series like EventSeries, CreativeWorkSeries? |
Series type was previously left as a CreativeWork subclass, which was an error dating from its role as the original name for our CreativeWorkSeries.
…supertype. We have two subtypes of it, CreativeWorkSeries (successor to the original definition of Series, which was too generally named), plus the proposed EventSeries type (currently in the Pending area). These domain-specific series types also have corresponding supertypes in CreativeWork and Event. /cc #447 #1090
+1 expanding domain of isPartOf & hasPart to Series |
There was a comment here recently that I now don't see,
I continue to resist extending isPartOf outside of CreativeWork, where it is already plenty ambiguous. We can't pack a theory of parts into one property that applies across too many diverse types. I suggest we look at this after 3.4 is out as part of stabilizing various things like EventSeries that are in Pending, but http://schema.org/subEvent looks like it could do the job. |
This issue is being tagged as Stale due to inactivity. |
Proposed actions were applied. |
Proposed actions:
The text was updated successfully, but these errors were encountered: