RE: dwbp-ISSUE-46 (PIDs): How should we handle the issue of persistent URI design? [Use Cases & Requirements Document]

Dear WG members,

Comments to several posting.

"URI persistence is a matter of policy ..."  -  http://www.w3.org/TR/webarch/#URI-persistence


Having restated this, data should be identifiable *forever* - not for foreseeable future. URI syntax is a different matter: one can put up with almost any syntax as long as it can identify the data.

One has to assume that "web-based" means accessed with HTTP(S), so this implies that the data is always accessible with HTTP(S)  and in the *same* environment: this is not the case. For example, data accessible with:

 - HTTP(S): data can be archived without the original environment - dynamic data will not be accessible
 - FILE: no server side processing - dynamic data will not be accessible

The real world is far nastier.

In a nutshell:

 - Long-term.- Think in at least 25 to 50 years: data must readable, and hence also identifiable
 - Simple.- Keep it very simple - minimal processing (this includes URI redirections) to get the data
 - Full life-cycle.- original site, archiving into archival sites, and offline data - http://dragoman.org/comuri.html#ultrapersistent-uri


Regards
Tomas

-----Original Message-----
From: Data on the Web Best Practices Working Group Issue Tracker [mailto:sysbot+tracker@w3.org] 
Sent: Wednesday, October 01, 2014 9:47 AM
To: public-dwbp-wg@w3.org
Subject: dwbp-ISSUE-46 (PIDs): How should we handle the issue of persistent URI design? [Use Cases & Requirements Document]

dwbp-ISSUE-46 (PIDs): How should we handle the issue of persistent URI design? [Use Cases & Requirements Document]

http://www.w3.org/2013/dwbp/track/issues/46


Raised by: Phil Archer
On product: Use Cases & Requirements Document

As of 2014-10-01, the UCR does not explicitly call for advice on URI design/design for persistence. It is, however, implied in R-PersistentIdentification which says "Data should be persistently identifiable."

Do we need to add any detail to this? Or an additional requirement? Or do we think we've covered it? 

Context is all. In W3C space, persistent identifier means persistent URI. For some communities, that doesn't match the culture (scientific publishing for example).

Received on Wednesday, 1 October 2014 12:31:44 UTC