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

Provenance issues #25

Closed
ptgolden opened this issue Jul 21, 2015 · 1 comment
Closed

Provenance issues #25

ptgolden opened this issue Jul 21, 2015 · 1 comment

Comments

@ptgolden
Copy link
Member

In the provenance graph we currently have, there are statements like this one:

"specializationOf": "http://n2t.net/ark:/99152/p086kj9kr9q",
"wasRevisionOf": 
{
    "id": "http://n2t.net/ark:/99152/p086kj9kr9q?version=0"
}

Couple questions:

  1. Does wasRevisionOf need to be a JSON object? Can it be a simple string, with the mapping to id done in the JSON-LD context?
  2. Should we have wasRevisionOf values for new assertions/collections? wasRevisionOf only makes sense to me when the new version was actually a revision of something that already existed.

Also, we're not currently including type information (i.e. prov:Activity and prov:Entity). Was the on purpose? Are those implied by the relationships between things?

@rybesh
Copy link
Member

rybesh commented Jul 24, 2015

Does wasRevisionOf need to be a JSON object?

No.

Can it be a simple string, with the mapping to id done in the JSON-LD context?

Yes.

Should we have wasRevisionOf values for new assertions/collections?

No.

All the above issues were addressed by periodo/periodo-server#36.

we're not currently including type information (i.e. prov:Activity and prov:Entity). Was the on purpose?

Yes.

Are those implied by the relationships between things?

Yes.

@rybesh rybesh closed this as completed Jul 24, 2015
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

2 participants