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

Mapping JERM to PROV-O #4

Closed
wants to merge 1 commit into from
Closed

Mapping JERM to PROV-O #4

wants to merge 1 commit into from

Conversation

stain
Copy link
Contributor

@stain stain commented Oct 12, 2017

Partial fix for #2 - mapping JERM to PROV-O as upper ontology.

I have mapped with rdfs:isDefinedBy citations rather than noisy owl import.

In particular mapping classes:

  • jerm:Person subclassOf prov:Person as a JERM person must be a member of at least one Project, and (for some reason) must be a contributor of some Asset
  • jerm:MaterialEntity subclassOf prov:Entity
  • jerm:InformationEntity subclassOf prov:Entity

And object properties:

  • jerm:isDerivedFrom equivalentTo prov:wasDerivedFrom
  • jerm:hasContributor subPropertyOf prov:wasAttributedTo (and thus also jerm:hasCreator)

While I was tempted, I did not add:

  • jerm:Process subclassOf prov:Activity -- as jerm:Process says it hasContributor some Person -- the mapping above for hasContributor would (on OWL import of the whole PROV-O ontology) cause an inconsistency because prov:wasAttributedTo has a domain of prov:Entity, which in PROV is disjoint with prov:Activity.

I am a bit confused of what the jerm:Process hierarchy means, are they plans for processes experiments, etc. that may or may not happen, or are they something that has happened (or is already happening). I would think it should be the second, which hints that it is a prov:Activity, as defined in PROV

An activity is something that occurs over a period of time and acts upon or with entities; it may include consuming, processing, transforming, modifying, relocating, using, or generating entities. [Detailed specification] Just as entities cover a broad range of notions, activities can cover a broad range of notions: information processing activities may for example move, copy, or duplicate digital entities; physical activities can include driving a car between two locations or printing a book.

In that aspect we would then presumably also map jerm:hasInput equivalentProperty prov:used and jerm:hasOutput equivalentProperty prov:generated -- but I'm not sure here again if JERM's hasInput/hasOutput are meant to be records of something that was used/made, or linking to a (template/type) of something that could be used/made - the use of present tense here makes it very confusing.

@stuzart
Copy link
Member

stuzart commented Oct 17, 2017

Thanks Stian.

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

Successfully merging this pull request may close these issues.

2 participants