17.06.2004 epicur kathrin schroeder erpanet-workshop „persistent identifiers“ (17th june 2004)...

16
17.06.2004 EPICUR Kathrin Schroeder ERPANET-Workshop „Persistent Identifiers“ (17th June 2004) Uniform Resource Names (URN) – Overview Die Deutsche Bibliothek Kathrin Schroeder

Upload: kevin-potter

Post on 25-Dec-2015

220 views

Category:

Documents


1 download

TRANSCRIPT

Page 1: 17.06.2004 EPICUR Kathrin Schroeder ERPANET-Workshop „Persistent Identifiers“ (17th June 2004) Uniform Resource Names (URN) – Overview Die Deutsche Bibliothek

17.06.2004

E

PIC

UR

Kathrin Schroeder

ERPANET-Workshop „Persistent Identifiers“

(17th June 2004)

Uniform Resource Names (URN) –

Overview

Die Deutsche Bibliothek

Kathrin Schroeder

Page 2: 17.06.2004 EPICUR Kathrin Schroeder ERPANET-Workshop „Persistent Identifiers“ (17th June 2004) Uniform Resource Names (URN) – Overview Die Deutsche Bibliothek

17.06.2004

E

PIC

UR

Kathrin Schroeder

● Naming Schemes and Namespaces (Identification)

– Uniform Resource Identifiers (URI), Uniform Resource Locators (URL)

– Uniform Resource Names (URN)

– further Persistent Identifiers

– XML namespaces

– ...

● Resolution of names (Resolution mechanims)

– HTTP (Redirect etc.)

– DNS (Domain Name System)

– ...

● Standardisation / Social Infrastructure

Starting Point: Naming Schemes / Namespaces and Resolution

Page 3: 17.06.2004 EPICUR Kathrin Schroeder ERPANET-Workshop „Persistent Identifiers“ (17th June 2004) Uniform Resource Names (URN) – Overview Die Deutsche Bibliothek

17.06.2004

E

PIC

UR

Kathrin Schroeder

Terminology – the „Classical view“

URI - Uniform

Resource Identifier

URN - Uniform

Resource Name

URL - Uniform

Resource Locator

URC - Uniform

Resource Characteristic

Identification of an abstract or physical resource

Persistent naming of resources.

RFC 2396

-Identification of a resource

- Provision a means of locating the resource by describing its primary access mechanism

Characteristics of a resource e.g. meta information

Page 4: 17.06.2004 EPICUR Kathrin Schroeder ERPANET-Workshop „Persistent Identifiers“ (17th June 2004) Uniform Resource Names (URN) – Overview Die Deutsche Bibliothek

17.06.2004

E

PIC

UR

Kathrin Schroeder

Report from the Joint W3C/IETF Planning Interest Group

- RFC 3305

Motivation: - Confusion in the web community over the partitioning of URI space, specifically, the relationship among the concepts of URL, URN, and URI.

Recommendations: -The importance of this additional level of hierarchy seemed to be lessen. -The W3C and IETF should jointly develop and endorse a model for URIs, URLs, and URNs consistent with the „Contemporary View“.- Generalized registration procedures for all URI schemes[...]

<http://www.ietf.org/rfc/rfc3305.txt>

Terminology – the „Contemporary view“

Page 5: 17.06.2004 EPICUR Kathrin Schroeder ERPANET-Workshop „Persistent Identifiers“ (17th June 2004) Uniform Resource Names (URN) – Overview Die Deutsche Bibliothek

17.06.2004

E

PIC

UR

Kathrin Schroeder

Registered URI-Schemes

Scheme Name Description Reference-------------------- ----------------------------------------- ----------------

urn Uniform Resource Names [RFC2141] (please see: http://www.iana.org/assignments/urn-namespaces)

ftp File Transfer Protocol [RFC1738]http Hypertext Transfer Protocol [RFC2616]

[... more than 40 URI SCHEMES]

http://www.iana.org/assignments/uri-schemes (last updated 2004-01-26)

Page 6: 17.06.2004 EPICUR Kathrin Schroeder ERPANET-Workshop „Persistent Identifiers“ (17th June 2004) Uniform Resource Names (URN) – Overview Die Deutsche Bibliothek

17.06.2004

E

PIC

UR

Kathrin Schroeder

URN-Framework

Request for Comments (RFC)

URN Syntax

Resolution

Registration of NIDs

Functional Requirements for

URNs

2141

1737

3406, 2611, 2288, 3188,

3187...

3401-3406

Page 7: 17.06.2004 EPICUR Kathrin Schroeder ERPANET-Workshop „Persistent Identifiers“ (17th June 2004) Uniform Resource Names (URN) – Overview Die Deutsche Bibliothek

17.06.2004

E

PIC

UR

Kathrin Schroeder

URN – Syntax (RFC 2141)

<URN>::=„URN“:“<NID>“:“<NISS>

URN: resolution routineNID: namespace identifier e.g. ISBN, ISSN und NBN NISS: namespace specific string

Example: urn:nbn:de:gbv:089-3321752945

<http://www.ietf.org/rfc/2141.txt>

Page 8: 17.06.2004 EPICUR Kathrin Schroeder ERPANET-Workshop „Persistent Identifiers“ (17th June 2004) Uniform Resource Names (URN) – Overview Die Deutsche Bibliothek

17.06.2004

E

PIC

UR

Kathrin Schroeder

URN-Framework

Request for Comments (RFC)

URN Syntax

Resolution

Registration of NIDs

Functional Requirements for

URNs

2141

1737

3406, 2611, 2288, 3188,

3187...

3401-3406

Page 9: 17.06.2004 EPICUR Kathrin Schroeder ERPANET-Workshop „Persistent Identifiers“ (17th June 2004) Uniform Resource Names (URN) – Overview Die Deutsche Bibliothek

17.06.2004

E

PIC

UR

Kathrin Schroeder

Functional Requirements

• Global scope • Global uniqueness • Persistence • Scalability • Legacy support • Extensibility • Independence • Resolution

Requirements for Encoding Implications

Functional Requirements for URNs (RFC 1737)

Page 10: 17.06.2004 EPICUR Kathrin Schroeder ERPANET-Workshop „Persistent Identifiers“ (17th June 2004) Uniform Resource Names (URN) – Overview Die Deutsche Bibliothek

17.06.2004

E

PIC

UR

Kathrin Schroeder

URN-Framework

Request for Comments (RFC)

URN Syntax

Resolution

Registration of NIDs

Functional Requirements for

URNs

2141

1737

3406, 2611, 2288, 3188,

3187...

3401-3406

Page 11: 17.06.2004 EPICUR Kathrin Schroeder ERPANET-Workshop „Persistent Identifiers“ (17th June 2004) Uniform Resource Names (URN) – Overview Die Deutsche Bibliothek

17.06.2004

E

PIC

UR

Kathrin Schroeder

Namespace Definition and Registration (RFC 3406)

Assumptions- Assignment of a URN is a managed process.- The space of URN namespaces is managed.

Templates for URN-namespace registration: - Experimental Namespaces- Informal Namespaces - Formal Namespaces

Considerations include: - URN assignment procedures - URN resolution/delegation - Type of resources to be identified - Type of services to be supported - Community considerations

Review by mailing-list [email protected]

Page 12: 17.06.2004 EPICUR Kathrin Schroeder ERPANET-Workshop „Persistent Identifiers“ (17th June 2004) Uniform Resource Names (URN) – Overview Die Deutsche Bibliothek

17.06.2004

E

PIC

UR

Kathrin Schroeder

● RFC 2648: A URN Namespace for IETF Documentsurn:ietf:rfc:2141

● RFC 3044: Using The ISSN (International Serial Standard Number) as URN (Uniform Resource Names) within an ISSN-URN Namespace urn:ISSN:0259-000X

● RFC 3188:Using National Bibliography Numbers as Uniform Resource Namesurn:nbn:fi-fe19981001

[... 21 Namespaces]

<http://www.iana.org/assignments/urn-namespaces>

Examples of registered URN-Namespaces

Page 13: 17.06.2004 EPICUR Kathrin Schroeder ERPANET-Workshop „Persistent Identifiers“ (17th June 2004) Uniform Resource Names (URN) – Overview Die Deutsche Bibliothek

17.06.2004

E

PIC

UR

Kathrin Schroeder

URN-Framework

Request for Comments (RFC)

URN Syntax

Resolution

Registration of NIDs

Functional Requirements for

URNs

2141

1737

3406, 2611, 2288, 3188,

3187...

3401-3406

Page 14: 17.06.2004 EPICUR Kathrin Schroeder ERPANET-Workshop „Persistent Identifiers“ (17th June 2004) Uniform Resource Names (URN) – Overview Die Deutsche Bibliothek

17.06.2004

E

PIC

UR

Kathrin Schroeder

Dynamical Delegation to URN services via DNS (RFC 3401 - 3404)

urn.arpa (Top Level)

nbn ietf

de

URN-REQUEST

urn:ietf:..

urn:nbn:...

[...]

ch fi hu

19 ...

se...

Examples „[email protected]“:

VeriSign „pin“

Voice over IP (ENUM)

au

Page 15: 17.06.2004 EPICUR Kathrin Schroeder ERPANET-Workshop „Persistent Identifiers“ (17th June 2004) Uniform Resource Names (URN) – Overview Die Deutsche Bibliothek

17.06.2004

E

PIC

UR

Kathrin Schroeder

The client (Browser) perspective …

Plugins (Example)

http://www.persistent-identifier.de/?link=550

Other technical solutions exist ...

Page 16: 17.06.2004 EPICUR Kathrin Schroeder ERPANET-Workshop „Persistent Identifiers“ (17th June 2004) Uniform Resource Names (URN) – Overview Die Deutsche Bibliothek

17.06.2004

E

PIC

UR

Kathrin Schroeder

Discussion points

Steady browser implementation of PIs/URNs

Development of a PI independent browser-plugin

Continuing the co-operation between IANA/IETF/W3C

Interfaces between several PI-Resolution mechanisms

And the Future ?

Thank you!

[email protected]