- From: Rob Atkinson via GitHub <sysbot+gh@w3.org>
- Date: Mon, 25 Jun 2018 23:10:16 +0000
- To: public-dxwg-wg@w3.org
@azaroth42 - your exercise in separation of concerns is probably also applicable to datasets and distributions. i dont think there is much appetite for a very deep model of profiles however - and everything needs to be grounded in a specific requirement. That said, the "role" qualifier on a profile definition (in word, SHACL, UML or whatever) could be used to discriminate between these levels of abstraction perhaps. PDF (text) forms of profile definitions tend to bundle multiple levels of abstraction in a single artefact, but machine readable artefacts such as the "semantic profile" could have a specific role. Materialisations could be sub-profiles - and the use of production rules, for example to control JSON-LD serialisation etc could be included as a requirement - such profiles could inherit from an additional base specification which includes such constraints. (a profile is an interoperability contract - so predictability of serialisation is definitely a profile concern). So currently, I think the profileDesc proposal can handle these concerns - and it is derived from the original proposed requirements in the UCR, (the current exercise in discussing these in plenary has not yet had significant impact by adding, deleting or changing any of these). So procedure-wise we can a) test profileDesc against your own scenario - and suggest improvements. If your scenario is not adequately addressed however... b) look for holes in the set of Use Cases such that they do not sufficiently drive or explain such requirements. to my mind, its possibly the specification of "API profile" interoperability rules applicable to dataset Distributions and services. You may need to look at DCAT practices here if this cannot be addressed as part of a profile specification. NB. An open question for profileDesc is to what extent we define a canonical set of "roles" to describe the form and function of constraint expressions. -- GitHub Notification of comment by rob-metalinkage Please view or discuss this issue at https://github.com/w3c/dxwg/issues/162#issuecomment-400124141 using your GitHub account
Received on Monday, 25 June 2018 23:10:21 UTC