ERPANET-Workshop Persistent Identifiers (17th June .ppt

1、ERPANET-Workshop Persistent Identifiers“ (17th June 2004)Uniform Resource Names (URN) Overview,Die Deutsche Bibliothek Kathrin Schroeder,Naming Schemes and Namespaces (Identification) Uniform Resource Identifiers (URI), Uniform Resource Locators (URL) Uniform Resource Names (URN) further Persistent

2、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,Terminology the Classical view“,URI - Uniform Resource Identifier,URN - Uniform R

3、esource 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,Characteris

4、tics of a resource e.g. meta information,Report from the Joint W3C/IETF Planning Interest Group - RFC 3305Motivation: - 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 ad

5、ditional 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 .,Terminology the Contemporary view“,Registered URI-Schemes,Scheme Name

6、 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),URN-Fra

7、mework,Request for Comments (RFC),URN Syntax,Resolution,Registration of NIDs,Functional Requirements for URNs,2141 17373406, 2611, 2288, 3188, 3187.3401-3406,URN Syntax (RFC 2141),:=URN“:“:“URN: resolution routine NID: namespace identifier e.g. ISBN, ISSN und NBN NISS: namespace specific stringExamp

8、le: urn:nbn:de:gbv:089-3321752945,URN-Framework,Request for Comments (RFC),URN Syntax,Resolution,Registration of NIDs,Functional Requirements for URNs,2141 17373406, 2611, 2288, 3188, 3187.3401-3406,Functional Requirements Global scope Global uniqueness Persistence Scalability Legacy support Extensi

9、bility Independence Resolution Requirements for EncodingImplications,Functional Requirements for URNs (RFC 1737),URN-Framework,Request for Comments (RFC),URN Syntax,Resolution,Registration of NIDs,Functional Requirements for URNs,2141 17373406, 2611, 2288, 3188, 3187.3401-3406,Namespace Definition a

10、nd Registration (RFC 3406),AssumptionsAssignment of a URN is a managed process.The space of URN namespaces is managed.Templates for URN-namespace registration: Experimental NamespacesInformal Namespaces Formal NamespacesConsiderations include:- URN assignment procedures- URN resolution/delegation- T

11、ype of resources to be identified- Type of services to be supported- Community considerations Review by mailing-list urn-nidapps.ietf.org,RFC 2648: A URN Namespace for IETF Documents urn:ietf:rfc:2141 RFC 3044: Using The ISSN (International Serial Standard Number) as URN (Uniform Resource Names) wit

12、hin an ISSN-URN Namespace urn:ISSN:0259-000X RFC 3188: Using National Bibliography Numbers as Uniform Resource Names urn:nbn:fi-fe19981001 . 21 Namespaces ,Examples of registered URN-Namespaces,URN-Framework,Request for Comments (RFC),URN Syntax,Resolution,Registration of NIDs,Functional Requirement

13、s for URNs,2141 17373406, 2611, 2288, 3188, 3187.3401-3406,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 registerurn.arpa“: VeriSign pin“ Voice over IP (ENUM),au,The client (Browser) persp

14、ective ,Plugins (Example),http:/www.persistent-identifier.de/?link=550,Other technical solutions exist .,Discussion pointsSteady 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! schroederdbf.ddb.de,