search

qudt / qudt-public-repo

QUDT -Quantities, Units, Dimensions and dataTypes - public repository
Other
116 stars 73 forks source link

Move annotation properties into separate files/graphs #20

Open dr-shorthair opened 4 years ago

dr-shorthair commented 4 years ago

Clean up the ontologies by

  1. removing deprecated properties
  2. moving annotation properties into separate files/graphs

(Copied from https://github.com/qudtdev/qudt-r2/issues/100)

steveraysteveray commented 4 years ago

I agree with your first point of getting rid of deprecated properties. But I'm wondering about the wisdom of your second suggestion. I say this because I recently finished consolidating all the separate graphs containing unit definitions. Different context, I realize, because here you are not talking about a duplicate definition. However, what problem are you trying to solve? Is it simply the size of the file? The units vocabulary file is still less than 1MB in size. Is it performance? The downside of having separate graphs is more housekeeping, deciding whether a property is an annotation property or not, etc. I'm willing to support your suggestion once I'm convinced - just not there yet.

dr-shorthair commented 4 years ago

Actually I was thinking more of the Ontology files. The core of the ontology is the classes and relationships. Too many annotations are a lot of clutter to fight through, particularly in the context of the UML-style diagrams generated by TopBraid.

dr-shorthair commented 4 years ago

I'm primarily looking for a better structure in the ontology files. Incidental property definitions can be housed in separate graphs, which then can be loaded only when needed.

ralphtq commented 4 years ago

Prefer not to have the schema split across schemas. SPARQL can do the filtering. In the Linked Data world there should also be a way to have filtering with content negotiation?