ISSUE-46: How should we handle the issue of persistent URI design?

PIDs

How should we handle the issue of persistent URI design?

State:

CLOSED

Product:

Data Usage Vocabulary

Raised by:

Phil Archer

Opened on:

2014-10-01

Description:

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).

Related Actions Items:

No related actions

Related emails:

1. Re: dwbp-ISSUE-46 (PIDs): How should we handle the issue of persistent URI design? [Use Cases & Requirements Document] (from christophe.gueret@dans.knaw.nl on 2014-10-24)
2. Re: UCR Forked (from laufer@globo.com on 2014-10-02)
3. UCR Forked (from phila@w3.org on 2014-10-02)
4. Re: dwbp-ISSUE-46 (PIDs): How should we handle the issue of persistent URI design? [Use Cases & Requirements Document] (from phila@w3.org on 2014-10-02)
5. RE: dwbp-ISSUE-46 (PIDs): How should we handle the issue of persistent URI design? [Use Cases & Requirements Document] (from Deirdre.Lee@deri.org on 2014-10-02)
6. RE: dwbp-ISSUE-46 (PIDs): How should we handle the issue of persistent URI design? [Use Cases & Requirements Document] (from mail@makxdekkers.com on 2014-10-01)
7. RE: dwbp-ISSUE-46 (PIDs): How should we handle the issue of persistent URI design? [Use Cases & Requirements Document] (from Manuel.CARRASCO-BENITEZ@ec.europa.eu on 2014-10-01)
8. Re: Related to Issue-46 (from christophe.gueret@dans.knaw.nl on 2014-10-01)
9. Re: dwbp-ISSUE-46 (PIDs): How should we handle the issue of persistent URI design? [Use Cases & Requirements Document] (from phila@w3.org on 2014-10-01)
10. RE: dwbp-ISSUE-46 (PIDs): How should we handle the issue of persistent URI design? [Use Cases & Requirements Document] (from Manuel.CARRASCO-BENITEZ@ec.europa.eu on 2014-10-01)
11. Related to Issue-46 (from phila@w3.org on 2014-10-01)
12. RE: dwbp-ISSUE-46 (PIDs): How should we handle the issue of persistent URI design? [Use Cases & Requirements Document] (from mail@makxdekkers.com on 2014-10-01)
13. Re: dwbp-ISSUE-46 (PIDs): How should we handle the issue of persistent URI design? [Use Cases & Requirements Document] (from phila@w3.org on 2014-10-01)
14. RE: dwbp-ISSUE-46 (PIDs): How should we handle the issue of persistent URI design? [Use Cases & Requirements Document] (from mail@makxdekkers.com on 2014-10-01)
15. Re: dwbp-ISSUE-46 (PIDs): How should we handle the issue of persistent URI design? [Use Cases & Requirements Document] (from christophe.gueret@dans.knaw.nl on 2014-10-01)
16. Re: dwbp-ISSUE-46 (PIDs): How should we handle the issue of persistent URI design? [Use Cases & Requirements Document] (from phila@w3.org on 2014-10-01)
17. RE: dwbp-ISSUE-46 (PIDs): How should we handle the issue of persistent URI design? [Use Cases & Requirements Document] (from mail@makxdekkers.com on 2014-10-01)
18. dwbp-ISSUE-46 (PIDs): How should we handle the issue of persistent URI design? [Use Cases & Requirements Document] (from sysbot+tracker@w3.org on 2014-10-01)

Related notes:

Display change log