The 'UML' representation was prepared in response to your suggestion @kcoyle - but it is just a convenient graphical rendering and is non-normative (as is the rest of clause 5). Regarding the alignment of properties to classes, DCAT is axiomatized using a mixed model. Some but not all of the DCAT properties have RDFS domains and ranges. However, DCAT makes extensive use of Dublin Core, and there are no axioms in DC's RDF formalization to tie any of those to DCAT classes. We discussed this agreed that the statements in the Recommendation document are definitive, where we say "The following properties are recommended for use on this class: ..." so I just reflected these up into the diagram. I might have missed a few, but was guided initially by [this diagram from DCAT-2014](https://www.w3.org/TR/2014/REC-vocab-dcat-20140116/dcat-model.jpg). -- GitHub Notification of comment by dr-shorthair Please view or discuss this issue at https://github.com/w3c/dxwg/issues/317#issuecomment-417989608 using your GitHub accountReceived on Monday, 3 September 2018 03:16:09 UTC
This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 20:28:24 UTC
