- From: Rob Atkinson via GitHub <sysbot+gh@w3.org>
- Date: Mon, 09 Sep 2019 08:24:00 +0000
- To: public-dxwg-wg@w3.org
@makxdekkers the example you cite is rather informative - but it supports the view in the profiles vocabulary rather than any suggestion that we need some weaker notion of "compatibility" to handle DCAT-AP profiles. " Extensions must not widen but may only narrow down the usage notes as specified in DCAT-AP v1.1, so that all information provided according to the extension remains valid for DCAT-AP v1.1" and if you wanted to argue about "thats for extensions not profiles" it makes it clear it regards these as the same in the rationale: "The proposed rules are intended to allow an extension profile to satisfy local or domain-specific requirements while preserving interoperability in a wider European and cross-domain environment," this neatly joins the dots in the proposed Profiles design that its notion of compatibility via conformance is a requirement for interoperable data exchange. -- GitHub Notification of comment by rob-metalinkage Please view or discuss this issue at https://github.com/w3c/dxwg/issues/844#issuecomment-529353982 using your GitHub account
Received on Monday, 9 September 2019 08:24:01 UTC