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.

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

Pattern needed for describing change history of a creative work (TrustProject request, but broader usecase) #175

Open
danbri opened this issue Nov 28, 2017 · 5 comments
Assignees

Comments

@danbri
Copy link
Contributor

danbri commented Nov 28, 2017

"From Trust Project dialog we would like a pattern for describing errata edits to a document that distinguish errata changes from others, and that is consistent with what we're doing around CreativeWork in general (e.g. version, workExample etc.), and which makes sense for data NewsArticle aggregation usecases such as AMP HTML." (background in schemaorg/schemaorg#1688)

  • Can we describe how to use PublicationEvent to give a history of changes/revisions to a creative work?
  • Can we show some common practices for indicating via workExample or other properties, how specific versions relate to representations of "the document in general". How does this vary between e.g. books, scholarly articles, versioned releases datasets, news articles?
  • For the NewsArticle case, it is important to know which updates include errata and omissions?

/cc @RichardWallis re bibextend

@danbri danbri self-assigned this Nov 28, 2017
@tfrancart
Copy link

In the Legislation extension we rely on workExample to relate specific versions of a law to "that law in general".

Also, something that is not in the proposed Legislation extension but that is present in the ELI ontology is the difference between the notion of "changes" (law A changes law B), implying a legal change, and "corrects", implying only minor typo fixes, not changing the intellectual/legal content. Basically we have this property hierarchy :

changes
  \- amends
  \- repeals
  \- commences
  \- ...
corrects

Similar use-case : we are currently working to model (not using schema.org) the process of drafting legislation, implying the modeling of change Events in the drafted law lifecycle, and the sequence of versions of the drafted law.

My 2 cents.

@davidbarratt
Copy link

It would be helpful having a Revision type or something like that. There isn't really a way to represent changes to things. A git commit would be an example of a Revision to SoftwareSourceCode etc.

@davidbarratt
Copy link

Or There could be a difference between a Revision and a Diff

@davidbarratt
Copy link

I suppose a Diff consists of two Revision objects and perhaps also describes the difference between them.

@RichardWallis RichardWallis transferred this issue from schemaorg/schemaorg Jul 21, 2020
@RichardWallis
Copy link

See issue #7 for the context of the move from the main Schema.org issue tracker to this repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants