A first cut at the Draft Charter for the proposed URNbis WG

Folks,
Based on work done by Juha Hakala in February, I have updated
and amended the Draft Charter and hereby bring it to the urn list
for discussion.   Comments welcome!

Kind regards,
  Alfred Hönes.

---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ----

Uniform Resource Names, Revised (URNbis) -- Draft Proposed WG Charter
========================================

Last Modified:  2010-04-26 [AH]

Chair(s):
  o   Juha Hakala  <juha.hakala <at> helsinki.fi>
  o   N.N.

Applications Area Director(s):
  o   Alexey Melnikov  <alexey.melnikov <at> isode.com>
  o   Peter Saint-Andre  <stpeter <at> stpeter.im>

Applications Area Advisor:
  o   Peter Saint-Andre  <stpeter <at> stpeter.im>

Mailing Lists:
  General Discussion: urn <at> ietf.org
  To Subscribe: https://www.ietf.org/mailman/listinfo/urn
  Archive: http://www.ietf.org/mail-archive/web/urn/current/maillist.html

  Related lists (used for IANA registration procedures (BCP 35/66):
    urn-nid <at> ietf.org, uri-review <at> ietf.org

Additional information will be available at:
  http://tools.ietf.org/wg/urnbis

Description of Working Group:

  Uniform Resource Names (URNs) are persistent identifiers for
  information resources.  The RFCs defining URNs and services based on
  them were published 1997-2001.  Since then, the URN system has gained
  popularity.  Among the more traditional parties with deep interest in
  persistent identifiers and making heavy use of URNs are national
  libraries; solely within this area, tens of millions of resources
  have been assigned URNs; this enables efficient searching of and
  persistent linking to these documents.

  This working group is chartered to revise the key RFCs describing the
  URN system, including RFC 2141 (URN Syntax) and RFC 4306 (Namespace
  Definition Mechanisms), update important URN namespace specifications,
  and to screen and update RFCs describing URN resolution principles
  and practices.

  For RFC 2141, this revision will include in particular: an update of
  the formal syntax specification in the light of the URI Standard
  (STD 66, RFC 3986) using the ABNF from STD 68 (RFC 5234), a revision
  of URN examples from imaginary ones into existing URNs in current
  namespaces, providing a formal IANA registration for the 'urn' URI
  scheme using the template from BCP 35 (RFC 4395), and an update of
  the section describing how URNs are resolved in the Internet.
  RFC 4306 (BCP 66) needs a less pervasive update, mostly to align it
  with the current IANA procedures and terminology as defined in BCP 26
  (RFC 5226).

  Regarding URN Namespace specifications, the WG will focus on updates
  for the definitions of URNs based on bibliographic identifier systems,
  in particular RFC 3187 (URN Namespace for International Standard Book
  Numbers) and RFC 3188 (URN Namespace for National Bibliography
  Numbers).  In both cases, the respective identifier system and/or the
  institutions and roles involved in their assignment and resolution
  have evolved significantly since these RFCs have been published.
  In particular, the URN:ISBN namespace needs to be extended according
  to the revision of the international ISBN standard, and the usage of
  the URN:NBNs has grown rapidly and there is a need to align the
  namespace registration with experience and current practice.
  In a second stage, RFC 3044 (URN Namespace for International Series
  Standard Number) will be checked for the necessity of an update.

  Thus, in support of the current international efforts to establish a
  distributed, linked system of URN resolution systems for bibliographic
  identifiers, the primary aim of the WG is an updated set of standards
  documents, which is needed to assure uniformity and interoperability
  of the URN resolution services.

  Alongside the modernization of these core RFCs for URNs and specific
  URN namespaces, the working group will also consider a revision of
  earlier RFCs related to the principles of URNs and URN resolution,
  such as RFC 2483 (URI Resolution services necessary for URN
  resolution), RFC 2276 (Architectural principles of Uniform Resource
  Name Resolution), RFC 1737 (Functional requirements for Uniform
  Resource Names) and RFC 2169 (A trivial convention for using HTTP in
  URN resolution).  All these must be checked; if the document is still
  deemed relevant, it will be modernized.

  The working group will also consider the possibility of publishing
  Best Current Practices on how to resolve the URNs utilizing the
  existing Internet protocols such as HTTP.  This BCP will be based on
  the European URN resolution infrastructure under construction in the
  project PersID.

  Since the revised specifications will be based on existing production
  systems and provide important guidelines for future implementers,
  the WG aims at publishing the RFCs on the Standards Track and will try
  to advance the core document at least to Draft Standard status as fast
  as possible.

  The WG can take on work to update other well-established URN namespace
  definitions upon a case-by-case decision.

Input documents:

  RFC 2141
  RFC 3406

  RFC 3187
  RFC 3188

  RFC 2483
  RFC 2276
  RFC 1737
  RFC 2169

Goals and Milestones (preliminary):

  Feb 2010   Initial WG formation as 'URN-R' (outside the IETF)
  Mar 2010   WG work plan completed, brought to IETF APP Area
  May 2010   first Internet-Drafts for most important core document
             revisions
  Jul 2010   Presentation of the group & early results at IETF 78 (BoF)
  Aug 2010   Formal establishment of the IETF WG
  Dec 2010   WG Last Call on WG core document set
  Feb 2011   core document set forwarded to IESG
      2011   work on supporting documents (guidelines, URN resolution)
      2012   implementation report for promoting 2141bis to Draft Std.

Internet-Drafts:

  draft-ah-rfc2141bis-urn          (-00: March 2010)
  draft-hakala-rfc3187bis-isbn-urn (-00: March 2010)
  draft-hakala-rfc3188bis-nbn-urn  (-00 due for week 18/2010)

Request For Comments:

  none so far

_______________________________________________
urn mailing list
urn <at> ietf.org
https://www.ietf.org/mailman/listinfo/urn