Code development platform for open source projects from the European Union institutions 🔵 EU Login authentication by SMS has been phased out. To see alternatives please check here

Skip to content

Inconsistencies between UML and entity tables

We note the following inconsistencies between the UML diagram (non-public profile, others not reviewed) and the tables on the specification page:

Dataset:

  • dpv:hasPersonalData cardinality 0..1 in UML (0..* in Dataset table)
  • healthdcatap:hasCodeValues cardinality 0..1 in UML (0..* in Dataset table)
  • healthdcatap:retentionPeriod range dct:PeriodOfTime in UML and examples (xsd:duration in Dataset table)

Agent:

UML diagram models new HealthAgent subtype as inheriting implementation of foaf:Agent, with one new mandatory property, and new HealthPublisherAgent as inheriting implementation of HealthAgent, with two further recommended properties.

The properties table for Health Data Access Body explicitly reproduces the name and type properties inherited from Agent. The properties table for Publisher does NOT reproduce the mandatory "name" property inherited from Agent but reproduces the recommended "type" property. For the sake of consistency, please either always reproduce all inherited properties explicitly or only state the properties specific to the sub-entity. From a usability perspective, the former (state all inherited properties) would be easier to follow.

For further information about the platform and support, please see https://code.europa.eu/info/about