- From: Alejandra Gonzalez-Beltran via GitHub <sysbot+gh@w3.org>
- Date: Mon, 09 Dec 2019 18:01:28 +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. > I meant in the W3C Process Document (https://www.w3.org/2019/Process-20190301/#rec-rescind), not in the DCAT Proposed Rec About your text - here it goes again with a few changes in italics: "DCAT 2 supersedes DCAT [VOCAB-DCAT-20140116], *but it does not make it obsolete*. DCAT 2 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 *do not* need to upgrade to it, *unless they want to use the new features*. 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." What do you think? -- GitHub Notification of comment by agbeltran Please view or discuss this issue at https://github.com/w3c/dxwg/issues/1177#issuecomment-563357893 using your GitHub account
Received on Monday, 9 December 2019 18:01:30 UTC