...
Homework: Evaluation, what has been changed, what should be removed, what should be updated, building the VCARD ontology module file (Add/Retract).
Team: Tatiana Walther LEAD (TIB), Muhammad Javed (Cornell), Mike Conlon Co-LEAD (VIVO)
DELIVERABLES:
A file that contains list of VCARD entities that are used in vivo software but with a second column, specifying if the entity is current, changed or is deprecated (do not exist) in the current VCARD ontology. (current/deprecated/changed).
A new model to substitute the changed or deprecated VCARD terms.
A file that contains vcard graph that should be removed from vivo.owl
A file that contains vcard graph that should be added in vivo.owl.
Evaluate vivo_changed.owl
"SPARQL Construct Query" to find existing triples and to replace with new. - most likely a part of the next sprint
Comments:
Created a file vcard.owl which I have extracted out of vivo.owl by means of robot. Then I've made the necessary changes: *1*. I've changed the URIs if necessary, *2*. I've modified datatype properties to object properties if it was required, *3*. I removed deprecated properties and classes. I have substituted the removed classes with rdfs:Resource in range assignments of affected properties. 4. I've added the owl:equivalentProperty axiome where it was required according to the spec. All of these changes are in the vcard_changed.owl. Both of the files as well as a vcard_diff.txt where all the differences are enumerated are in the Google Drive folder (https://drive.google.com/drive/folders/1Q6ZgmxyF0wDDgvNt0zm8OOgQfAud4ydM) I have also tried to make a new vivo.owl with the help of merge / unmerge functions of robot, but not all of the deprecated things could be removed this way. So, I need to figure out, how to do this with robot. Of course, it would be no problem to do it manually. I'm not that experienced with robot yet.
...