Skip to content

/ schemaorg

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

Jump to bottom

We have CreativeWorkSeries but don't say how it relates to the earlier Series #1090

Open
danbri opened this issue Apr 11, 2016 · 6 comments
Open

We have CreativeWorkSeries but don't say how it relates to the earlier Series #1090

danbri opened this issue Apr 11, 2016 · 6 comments
Assignees
@danbri
Labels
no-issue-activity schema.org vocab status:work expected type:bug type:cleanup + clarity
Milestone
sdo-deimos release

Comments

@danbri
Copy link
Contributor

@danbri danbri commented Apr 11, 2016

  • #417 added CreativeWorkSeries in v2.0 http://schema.org/docs/releases.html
  • the RDFS in data/schema.org says: supersededBy http://schema.org/CreativeWorkSeries
  • the schema.org site UI has no support for this construct on types or enumerated values, only properties
  • EventSeries is proposed as a subtype of Series despite it being superseded
    • We should have a unit test to make sure no proposals are in pending.schema.org that depend upon superseded vocabulary.

Proposed actions:

  • remove the supersededBy on Series, restore it as a supertype of both CreativeWorkSeries and EventSeries; polish definitions accordingly.
  • this should work with #447 as-is
@danbri danbri self-assigned this Apr 11, 2016
@danbri danbri added this to the sdo-deimos release milestone Apr 11, 2016
@danbri danbri mentioned this issue Apr 11, 2016
Open
@danbri
Copy link
Contributor Author

@danbri danbri commented Apr 11, 2016

Alternative (after chatting with @vholland ) would be to continue to retire Series, and to allow CreativeWorkSeries to continue under CreativeWork, plus adding new EventSeries under Event for #447.
@Dataliberate
Copy link
Contributor

@Dataliberate Dataliberate commented Apr 11, 2016

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
@danbri
Copy link
Contributor Author

@danbri danbri commented Apr 22, 2016

/cc @rvguha - is there any value in "Series" over and above having different kinds of series like EventSeries, CreativeWorkSeries?
@danbri danbri mentioned this issue Apr 20, 2018
Closed
10 of 10 tasks complete
danbri added a commit that referenced this issue Apr 26, 2018
@danbri
Uncommented 2nd subClassOf to /Series /cc #447 #1090
3fb492f 
Series type was previously left as a CreativeWork subclass, which was
an error dating from its role as the original name for our CreativeWorkSeries.
danbri added a commit that referenced this issue Apr 26, 2018
@danbri
Series type is now intangible, rather than the mistaken CreativeWork …
Loading status checks…
f546ddb 
…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
@RichardWallis
Copy link
Contributor

@RichardWallis RichardWallis commented Jun 12, 2018

+1 expanding domain of isPartOf & hasPart to Series
@danbri
Copy link
Contributor Author

@danbri danbri commented Jun 14, 2018 •
edited

There was a comment here recently that I now don't see,

@danbri in moving the Series, the properties isPartOf and hasPart are no longer available as their domain was CreativeWork. The JSON-LD example for EventSeries series uses hasPart, but that is not available to the Class. Should the domain of hasPart and isPartOf add Series?

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.
@github-actions
Copy link

@github-actions github-actions bot commented Aug 9, 2020

This issue is being tagged as Stale due to inactivity.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@danbri danbri

Labels
no-issue-activity schema.org vocab status:work expected type:bug type:cleanup + clarity
Projects
None yet
Milestone
sdo-deimos release
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants
@danbri @Dataliberate @RichardWallis