costezki
commented
1 year ago The reason for avoiding complex datatypes, is that once we start structuring how data shall be organised, besides syntactic definitions, we inevitably embed semantic aspects as well. Doing so, the semantics of the structure is obscured and trapped in a technical interoperability layer. For example, xsd:duration encodes both the amount(s) and unit(s) of time into a regular expression that looks like this <period>P5Y2M10D</period>.
We have added this explanation in the section on Datatypes (https://semiceu.github.io/style-guide/public-review/gc-conceptual-model-conventions.html#sec:cmc-r18).
In § Attribute definition and usage. Ok that you would like to stick with atomic datatypes but the why is not explained. Structured datatypes are rather common, eg Geometry is definitly not a class, you would not normally attribute an identifier to a geometry, it is identified by its values.