resourceODP module report from the 2nd evaluation

[huanyu-li]

ResourceODP 0.2

Report from OOPS!

• [x] P39, ~Ambiguous namespace~
• [ ] P13, Inverse relationships not explicitly declared
• [x] P10, ~Missing disjointness~
• [x] P11, ´ ~Missing domain or range in properties, resourceODP:hasPart, resourceODP:isRealizationOf, resourceODP:isAbout~
• [x] P04, Creating unconnected ontology elements, resourceODP:Resource, resourceODP:Composition

Report from FOOPS!

• [ ] R1, Recommended/Detailed metadata, doi, publisher, logo, status, issued, OPTIONAL: previous version, backwards compatibility, modified
• [x] F4, Error when retrieving prefix
• [x] F4/A2, Ontology not found in a public registry
• [x] I2, ~Could not find any imported/reused ...~
• [x] F1, ~Ontology URI is different from ontology ID, Your ontologyURI (e.g., its w3id) should be the same as the one used within the ontology itself. Ontology URI: http://w3id.org/CEON/ontology/resourceODP. Provided URI: https://w3id.org/CEON/ontology/resourceODP/0.2~

[huanyu-li]

Ontology URI is different from ontology ID is due to we give FOOPS! the URI including version number. It will be solved if we give the URI without version number. We need to make sure the w3id/CEON always direct to a latest version .

[huanyu-li]

Error when retrieving prefix is due to the prefix resourceODP is not registered in prefix.cc (http://prefix.cc) or LOV (https://lov.linkeddata.es). However just registering resourceODP may be not a good idea as resourceODP is a generic term. One option could be change the prefix to ceon-resourceODP. Anyway, we registered ceon:http://w3id.org/CEON/ at this moment.

[huanyu-li]

Ambiguous namespace issue doesn't reappear.