W3C home > Mailing lists > Public > public-dxwg-wg@w3.org > July 2019

Re: [dxwg] Updated namespace file (#881)

From: David Browning via GitHub <sysbot+gh@w3.org>
Date: Wed, 31 Jul 2019 13:54:52 +0000
To: public-dxwg-wg@w3.org
Message-ID: <issue_comment.created-516859294-1564581290-sysbot+gh@w3.org>
This comment summarises our intentions here.

The 2014 recommendation contains links to the namespace page at `https://www.w3.org/ns/dcat#`.  (For example, in the Class tables at https://www.w3.org/TR/2014/REC-vocab-dcat-20140116/#class-catalog.).  By default this returns a simple namespace page that provides links to the rdf definitions in either turtle or rdf/xml.  The namespace also supports these alternate forms directly via the `link` header.

DCAT2 uses the same name space (so we aren't introducting a new version in the URI) and we are providing replacement turtle and rdf/xml that are backward compatible, some other representations/encodings and a new namespace file.  Simply renaming the existing resources (by addtition of 2014 perhaps) and replacing them with new resources means that links from the 2014 spec will show the new resources.  Is this acceptable?   We can ensure that the turtle. etc  files and the namespace page include appropriate text to guide any human user, but we'd appreciate guidance on doing this for machine access.  Is something like ADMS (e.g. https://www.w3.org/TR/vocab-adms/#adms-last) appropriate and/or required ?  What would this mean for what we'd need to release?

GitHub Notification of comment by davebrowning
Please view or discuss this issue at https://github.com/w3c/dxwg/pull/881#issuecomment-516859294 using your GitHub account
Received on Wednesday, 31 July 2019 13:54:53 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:42:18 UTC