- From: Riccardo Albertoni via GitHub <sysbot+gh@w3.org>
- Date: Mon, 09 Dec 2019 17:43:14 +0000
- To: public-dxwg-wg@w3.org
> I couldn't find anything around backward compatiblity in the Process Document either. Well I think the first note in the Proposed Rec goes in that direction, see below >DCAT 2 maintains the DCAT namespace as it preserves backward compatibility with DCAT [VOCAB-DCAT-20140116]. DCAT 2 relaxes constraints and adds new classes and properties, but these changes do not break existing DCAT implementations. Perhaps we might want to elaborate a little more on this, and move the note earlier in the document. For example, saying > DCAT 2 supersedes DCAT [VOCAB-DCAT-20140116]. It maintains the DCAT namespace as its terms preserve backward compatibility with DCAT [VOCAB-DCAT-20140116]. DCAT 2 relaxes constraints and adds new classes and properties, but these changes do not break the definition of previous terms. Any new implementation is expected to adopt DCAT 2, while the existing implementations might not need to upgrade to it. In particular, current DCAT deployments that do not overlap with the DCAT 2 new features (e.g., data services, time and space properties qualified relations, packaging) don't need to change anything to remain in conformance with DCAT 2. -- GitHub Notification of comment by riccardoAlbertoni Please view or discuss this issue at https://github.com/w3c/dxwg/issues/1177#issuecomment-563350640 using your GitHub account
Received on Monday, 9 December 2019 17:43:16 UTC