Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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 oneProject
, and (for some reason) must be a contributor of someAsset
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 alsojerm:hasCreator
)While I was tempted, I did not add:
jerm:Process subclassOf prov:Activity
-- asjerm:Process
says ithasContributor some Person
-- the mapping above forhasContributor
would (on OWL import of the whole PROV-O ontology) cause an inconsistency becauseprov:wasAttributedTo
has a domain ofprov:Entity
, which in PROV is disjoint withprov: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 aprov:Activity
, as defined in PROVIn that aspect we would then presumably also map
jerm:hasInput equivalentProperty prov:used
andjerm: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.