search

OP-TED / ePO

The eProcurement Ontology provides the formal, semantic foundation for the creation and reuse of linked open data in the domain of public procurement in the EU.
European Union Public License 1.2
58 stars 18 forks source link

SHACL shape file creates cardinality 1:1 for any attribute. #255

Closed guascce closed 4 years ago

guascce commented 4 years ago

The assumption that each attribute is mandatory is wrong. the default is that attributes are mostly optional and only some are mandatory. This should be documented in the UML file.

paulakeen commented 4 years ago

At some point the WG decided not to represent the cardinalities of the class attributes (so not to overcomplicate innecessarily the diagrams, e.g. the cardinalities specified in eForms are different from the ones needed in the Procurement Value Chain).

However, given the fact that the OWL file is being generated from the UML XMI exportation, the absence of cardinality is interpreted by the tool used to draft the UML is 1..1).

Conclusion, at some point, the whole ePO UML will have to be modified to re-introduce the cardinalities of the attributes. This is an mid-term Action Point.

For the BDTI purposes, the pilot developers will modify manually their validation artefacts so they adapt the ePO OWL exportation to their needs.