W3C home > Mailing lists > Public > public-gld-wg@w3.org > January 2012

ISSUE-14 (permanent identifier): add dcat:permanentIdentifier property [DCAT]

From: Government Linked Data Working Group Issue Tracker <sysbot+tracker@w3.org>
Date: Thu, 26 Jan 2012 10:51:03 +0000
To: public-gld-wg@w3.org
Message-Id: <E1RqMv1-0002HJ-5L@tibor.w3.org>

ISSUE-14 (permanent identifier): add dcat:permanentIdentifier property [DCAT]

http://www.w3.org/2011/gld/track/issues/14

Raised by: Fadi Maali
On product: DCAT

copied from: http://wiki.okfn.org/OpenDataCatalogues/2#Proposed_Harvest_Mechanism#Changes_to_DCAT_to_support_the_catalog_model

Add a new property on datasets specifically for an identifier that helps with deduplication when aggregating DCAT records from multiple catalogs:
> dcat:permanentIdentifier a rdf:Property; > rdfs:subPropertyOf dc:identifier; > rdfs:label "Permanent Identifier"; > rdfs:comment "A permanent, universally unique identifier for the dcat:Dataset.".
This could be a UUID or an HTTP URI or whatever else, as long as it is unique. The ID must be kept intact even if the underlying dataset or any part of the metadata is changed. Aggregators must keep the identifier unmodified, even if they modify or enrich the dataset metadata.
This is distinct from dc:identifier because dc:identifier doesn't have to be globally unique; it's just an identifier with *some* scope.
(note: Atom's atom:id is interesting here -- must be an IRI, "permanent and universally unique", can be resolvable but Atom processors MUST NOT assume that it is: http://tools.ietf.org/html/rfc4287#section-4.2.6 )
Received on Thursday, 26 January 2012 10:51:04 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 25 June 2013 15:04:56 UTC