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 07:47:22 UTC