- From: tombaker via GitHub <sysbot+gh@w3.org>
- Date: Wed, 03 Apr 2019 07:55:43 +0000
- To: public-dxwg-wg@w3.org
@nicholascar wrote: > In fact, since a DCMI server update, the former doesn't even take you to the spec, only the folder containing it! This was indeed misconfigured in the new website and has been fixed. According to the [DCMI Namespace Policy](http://dublincore.org/documents/dcmi-namespace), first published in 2001, metadata terms are persistently identified using PURLs. DCMI makes no such commitment to the persistence of any other Web addresses, which function as locators (URLs) for Web pages, not as persistent identifiers, and could in principle change at any time. The PURL service does suffer occasional outages, but as @kcoyle hints, it would be disruptive to adopt new persistent identifiers for DCMI metadata terms - something not to be undertaken lightly. DCMI's position is that URLs such as http://www.dublincore.org/specifications/dublin-core/dcmi-terms/#terms-Standard should never be used to _identify_ `dct:Standard`. In principle, one could write ``` [http://purl.org/dc/terms/Standard](http://www.dublincore.org/specifications/dublin-core/dcmi-terms/#terms-Standard) ``` so that the PURL displays as the visible text, but since http://purl.org/dc/terms/Standard now resolves correctly, there would be no practical reason to do so. -- GitHub Notification of comment by tombaker Please view or discuss this issue at https://github.com/w3c/dxwg/pull/850#issuecomment-479380765 using your GitHub account
Received on Wednesday, 3 April 2019 07:55:47 UTC