- From: kcoyle via GitHub <sysbot+gh@w3.org>
- Date: Fri, 21 Sep 2018 08:52:21 +0000
- To: public-dxwg-wg@w3.org
I was thinking more about data elements such as: labels, definitions, and instructions. These, to my mind, would be included in the profile and would describe entities (probably classes in RDF), properties, and value descriptions. The full human-readable document would be described in the section on publication in my mind. What is tricky about that is that the human-readable document may be the profile itself (as in DCAT-AP whose only form is as a PDF document) or it could be a transformation of the profile, like the output of an XSLT if the profile is expressed in XML. I think we have this problem of defining "what is the profile?" when it may exist in different flavors. DCAT and profileDesc could help us here because the profile could be an abstraction with one or more manifestations that have different properties. The next challenge is that some manifestations may have more than one property or role, such as something like the DCAT-AP that has terms, definitions, cardinality, and validation rules all in one "file" or "document". Plus there's the need to distinguish between conceptual and implementable, and a document like the DSP could be both. I think this isn't as easily defined as the difference between datasets and distributions. -- GitHub Notification of comment by kcoyle Please view or discuss this issue at https://github.com/w3c/dxwg/issues/369#issuecomment-423462866 using your GitHub account
Received on Friday, 21 September 2018 08:52:23 UTC