Skip to content
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.

Sign up for GitHub

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

Closed
danbri opened this issue Apr 11, 2016 · 7 comments
Closed

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

danbri opened this issue Apr 11, 2016 · 7 comments
Assignees
@danbri
Labels
no-issue-activity Discuss has gone quiet. Auto-tagging to encourage people to re-engage with the issue (or close it!). schema.org vocab General top level tag for issues on the vocabulary status:work expected We are likely to, or would like to, or probably should try, ... to do something in this area. type:bug A mistake or malfunction whose remedy should be straightforward technical work type:cleanup + clarity Addresses wording fixes, ambiguities, confusion, bad examples etc
Milestone
sdo-deimos release

Comments

@danbri
Copy link
Contributor

danbri commented Apr 11, 2016

Proposed actions:
@danbri danbri self-assigned this Apr 11, 2016
@danbri danbri added type:bug A mistake or malfunction whose remedy should be straightforward technical work schema.org vocab General top level tag for issues on the vocabulary status:work expected We are likely to, or would like to, or probably should try, ... to do something in this area. type:cleanup + clarity Addresses wording fixes, ambiguities, confusion, bad examples etc labels Apr 11, 2016
@danbri danbri added this to the sdo-deimos release milestone Apr 11, 2016
@danbri danbri mentioned this issue Apr 11, 2016
Closed
@danbri
Copy link
Contributor Author

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

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 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 tasks
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 …
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

+1 expanding domain of isPartOf & hasPart to Series

@danbri
Copy link
Contributor Author

danbri commented Jun 14, 2018 •
edited
Loading

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 bot commented Aug 9, 2020

This issue is being tagged as Stale due to inactivity.

@github-actions github-actions bot added the no-issue-activity Discuss has gone quiet. Auto-tagging to encourage people to re-engage with the issue (or close it!). label Aug 9, 2020
@RichardWallis
Copy link
Contributor

Proposed actions were applied.
All superseded terms [of all types] now indicate their superseded state.

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 Discuss has gone quiet. Auto-tagging to encourage people to re-engage with the issue (or close it!). schema.org vocab General top level tag for issues on the vocabulary status:work expected We are likely to, or would like to, or probably should try, ... to do something in this area. type:bug A mistake or malfunction whose remedy should be straightforward technical work type:cleanup + clarity Addresses wording fixes, ambiguities, confusion, bad examples etc
Projects
None yet
Milestone
sdo-deimos release
Development

No branches or pull requests
3 participants
@danbri @Dataliberate @RichardWallis