W3C home > Mailing lists > Public > public-gld-wg@w3.org > March 2013

Re: Resolving ISSUE-14, dcat:permanentIdentifier

From: Phil Archer <phila@w3.org>
Date: Fri, 08 Mar 2013 12:27:40 +0000
Message-ID: <5139D93C.5060009@w3.org>
To: Richard Cyganiak <richard@cyganiak.de>
CC: public-gld-wg@w3.org
Instinctively I dislike this intensely. It encourages bad practice by 
suggesting that identifiers for data sets should all be treated as 
ephemeral except the special case of the dcat:permanentIdentifier. Gah!

If you create a catalogue as an aggregate of other catalogues (like 
publicdata.eu) then you jolly well SHOULD use the original URIs from the 
original catalogue. If you don't/can't/won't, then at least have the 
decency to include owl:sameAs links.

As ever, I am aware that I take a purist view and that practicality can 
play a trump card - meaning that if there are cases where the reason for 
wanting permanentIdentifier is something a lot better than "we like the 
way we do it so we're going to use our lovely 
foo.aspx?sessionID=claptrap" URIs but we recognise that your well 
designed http://{domain}/{type}/{concept}/{reference} URI might have 
something going for it" then OK, I won't be intransigent - but I don't 
like it.

So, -1 from me, but I remain open to persuasion if the evidence is there.

Phil.





On 08/03/2013 11:26, Richard Cyganiak wrote:
> There are two remaining issues on DCAT that we couldn't address in the telco. A Proposals for one of them is below. If you have any objection to the proposed course of action, please say so via email.
>
>
> ISSUE-14: add dcat:permanentIdentifier property
> http://www.w3.org/2011/gld/track/issues/14
>
> With some regret, I have to say:
>
> PROPOSAL: Postpone ISSUE-14, as there is no consensus on such a property.
>

-- 

Phil Archer
W3C eGovernment

http://philarcher.org
+44 (0)7887 767755
@philarcher1
Received on Friday, 8 March 2013 12:28:11 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:32:38 UTC