Re: [dxwg] A profile must be packaged as a self-contained artefact

inclusion in a serialisation is an implementation concern. DCAT profiles are quite obviously declared with a hierachical specialisation model.  Confusing implementation and description will not help with an understanding of "how things work".

specialisation hierarchies can be implemented by reference (each clause references its parent), by an "import" - such as owl:imports - these are platform specific , or by "duplication" - as in the RDF file for DCAT-AP.  

A valid case for an ability to provide a flattened implementation is not a valid argument to reject a requirement for hierarchical definition.  Instead we need a Use Case to support this proposed requirement for packaging.

I dont think however we can support a "MUST" statement  - profiles may be a mixture of machine readable constraints and additional textually defined requirements, that cannot be packaged in a single constraint language.

GitHub Notification of comment by rob-metalinkage
Please view or discuss this issue at using your GitHub account

Received on Monday, 25 June 2018 00:54:39 UTC