search

SEMICeu / style-guide

SEMIC style guide to create reusable vocabularies and application profiles
https://semiceu.github.io/style-guide/
Creative Commons Attribution 4.0 International
9 stars 2 forks source link

No class datatypes #66

Closed GeertThijs closed 1 year ago

GeertThijs commented 1 year ago

In § Attribute definition and usage. Like for the issue #x, there is no explanation. If the explanation would be that it makes a diagram more simple then that is not true: it simplifies most diagrams as there is no association line on the diagram. And the toolchain makes objectproperties of associations anyhow.

costezki commented 1 year ago

The reason for this is to keep a clear separation between (a) properties that take a literal value (governed by a datatype, and conceptually corresponding to owl:DatatypeProperty) and (b) properties that take a reference value (governed by a class, corresponding to owl:ObjectProperty). Doing so has two advantages: (a) it confers homogeneity to the model, which enhances readability and decreases ambiguity; (b) the toolchain implementation is easier as there is a clear treatment and interpretation.