Re: [urn] URN namespace for NBNs

[[e-mail] (Dale R. Worley)]

The draft looks fine to me.  There are various nits, which I've listed
below.

Dale

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

Various terminology like "hand-held", "immaterial", and "digital" is
used.  Do you have a clear terminology in mind?

2.  Conventions used in this document

   "NBN" refers to any National Bibliography Number identifier system
   used by the national libraries and other institutions, which use
   these identifiers with the national library's support and permission.

s/library's/libraries'/ since it is "support of libraries".  (Check
with the Editor!)

3.1.  The URN:NBN Namespace

   For instance, even if a digitized book has an ISBN, JPEG
   image files of its pages get NBNs.

You probably want to say "may get".

3.2.  Community Considerations for NBNs

   Note that the f-component is not a part of the NSS and therefore the ...

   Resources identified by NBNs are not always available in the ...

   If an NBN identifies an immaterial work, descriptive metadata about ...

These three paragraphs seem to be more about the resolution process
than community considerations.  Perhaps they can be separated in some
way?

4.1.  Overview

   uniqueness of the URN:NBNs at the global scale [Iso3166MA"/>.

This reference is corrupted.

4.2.  Encoding Considerations and Lexical Equivalence

   When an NBN is used as a URN, the namespace-specific string (NSS)
   MUST consist of three parts:

   o  a prefix, structured as a primary prefix, which is a two-letter
      ISO 3166-1 country code, ...

This doesn't specify *what* the country code must be.  Instead,

   When an NBN within a national library's identifier system is used
   as a URN, the namespace-specific string (NSS) MUST consist of three
   parts:

   o  a prefix, structured as a primary prefix, which is the two-letter
      ISO 3166-1 country code of the library's country, ...

5.  URN Namespace ID (NID) Registration for the National Bibliography
    Number (NBN)

   Declaration of syntactic structure of NSS part:

           nbn_string  = <specific per prefix>
                                         ; MUST adhere to RFC 3986 <path-rootless> syntax;
                                         ; parsers must regard nbn_strings as case-sensitive

There is trouble with <...> here.

      Colon MAY be used as a delimiting character only within the
      prefix, between ISO 3166-1 country code and sub-namespace code(s),
      which split the national namespace into smaller parts.

Comparing with the text in 4.2, I don't think this is phrased
correctly, as it may imply that colon may not appear in the
nbn_string.

      Reading it as:  Colon MAY be used (as a delimiting character
      only within the prefix) ...

Instead:

      Colon MAY be used within the prefix only as a delimiting
      character between the ISO 3166-1 country code and the
      sub-namespace code(s), which split the national namespace into
      smaller parts.

--

      See Section 4.2 of RFC XXXX for examples.

There should be a note telling the RFC Editor to insert the RFC number here.

   Process for identifier resolution:
      See Section 4.3 of RFC XXXX.

Ditto.

   Rules for lexical equivalence of NSS part:
      ...
      Formally, two URN:NBNs are lexically equivalent if they are octet-
      by-octet equal after the following (conceptional) preprocessing:

      1.  normalize the case of the leading "urn:" token;

This should be 'the leading "urn:nbn:" token', as otherwise the "nbn"
is not mentioned!

8.  Acknowledgements

   Revision of RFC 3188 started during the project PersID [PERSID] Later

Insert a full-stop after the reference.

9.  Contributors

   Alfred Hoenes was the editor and co-author of two of the documents
   from which this one is, in part, derived.

Is it possible to provide a description or reference to these
documents?  (One appears to be in the references already.)

Appendix A.  Significant Changes from RFC 3188

   Updated URN:NBN Namespace Registration template for IANA; whole
   document adapted to new URN Syntax document, RFC 2141bis, and new URN
   Namespace Registration document, RFC 3406bis (now retired and merged
   into 2141bis.

This paragraph is hard to read, and it has unbalanced parentheses.

   Use of query directives and fragment parts with this Namespace is now
   specified, in accordance with the aforementioned RFCs.

The terminology in RFC 8141 is "query components" and "fragment components".

[END]