Remove cardinalities from the CAV

isa-camss / CAV

The Core Assessment Vocabulary represents and defines what an “Assessment” of “assets” is and how to perform the assessment based on “Criteria”. It is a domain-agnostic vocabulary, meaning that it can be used to assess any type of assets.

3 stars 1 forks source link

Remove cardinalities from the CAV #20

Open paulakeen opened 3 years ago

paulakeen commented 3 years ago

The WG reflects on the need or not of specifying cardinalities in the CAV. One proposal is to keep 'core constraints'. Another one is to remove them completely.

This needs further discussion since it could be a relevant input for the SEMIC Style Guide.

jseguraf commented 3 years ago

The ePO (eProcurement Ontology) WG went to this very same discussion and implemented the UML model differently several times. The final conclusion, reached recently, is that having the cardinality of the class attributes specified is convenient when the UML is used for the generation of artefacts, such as an OWL TTL file containing the T-Box, or SHACL shapes derived from the XMI exportation.

jseguraf commented 3 years ago

For the current release of the CAV there is no need to define the cardinalities of the attributes, but they will be defined in future releases when shacl shapes will be generated.