draft-seantek-xmlns-rdf-urns-01.txt, review/URN assignment

Sean Leonard <dev+ietf@seantek.com> Fri, 25 September 2015 13:04 UTC

Return-Path: <dev+ietf@seantek.com>
X-Original-To: urn-nid@ietfa.amsl.com
Delivered-To: urn-nid@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 73B261A01A5 for <urn-nid@ietfa.amsl.com>; Fri, 25 Sep 2015 06:04:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level:
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7J-s8imDmeAF for <urn-nid@ietfa.amsl.com>; Fri, 25 Sep 2015 06:04:16 -0700 (PDT)
Received: from mxout-08.mxes.net (mxout-08.mxes.net [216.86.168.183]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3A1AB1A0108 for <urn-nid@ietf.org>; Fri, 25 Sep 2015 06:04:16 -0700 (PDT)
Received: from [192.168.123.7] (unknown [75.83.2.34]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id E859C509BD for <urn-nid@ietf.org>; Fri, 25 Sep 2015 09:04:14 -0400 (EDT)
Subject: draft-seantek-xmlns-rdf-urns-01.txt, review/URN assignment
References: <20150925125313.18560.84898.idtracker@ietfa.amsl.com>
To: "urn-nid@ietf.org" <urn-nid@ietf.org>
From: Sean Leonard <dev+ietf@seantek.com>
X-Forwarded-Message-Id: <20150925125313.18560.84898.idtracker@ietfa.amsl.com>
Message-ID: <56054638.8080506@seantek.com>
Date: Fri, 25 Sep 2015 06:03:52 -0700
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0
MIME-Version: 1.0
In-Reply-To: <20150925125313.18560.84898.idtracker@ietfa.amsl.com>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-256; boundary="------------ms040102070604000000060901"
Archived-At: <http://mailarchive.ietf.org/arch/msg/urn-nid/EJ8nz1OwlJr3ZqSgmpFaMy0fzog>
X-BeenThere: urn-nid@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: discussion of new namespace identifiers for URNs <urn-nid.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/urn-nid>, <mailto:urn-nid-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/urn-nid/>
List-Post: <mailto:urn-nid@ietf.org>
List-Help: <mailto:urn-nid-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/urn-nid>, <mailto:urn-nid-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Sep 2015 13:04:19 -0000

Hello URN-NID review list:

draft-seantek-xmlns-rdf-urns-01 has been posted. URN NID assignments for 
"xmlns" and "rdf" are requested. Please review.

Since the last draft, I have gotten interest and feedback indicating 
that there is pent-up demand for these namespaces. As it has been nine 
months since the last discussion, and URNBIS has failed to deliver 
results, we cannot delay further. Let's move forward; thank you.

Comments up through the last revision (specifically the comments by Dale 
R. Worley, but also others) have been incorporated or addressed.

Regards,

Sean

***********
TEMPLATE

  Namespace ID:
     xmlns

  Registration Information:
     Version: 1
     Date: 2015-09-24

  Declared registrant of the namespace:
     IETF

  Declaration of syntactic structures:
     An xmlns name is any
     valid XML name corresponding to "Name" in Section 2.3
     of [XML1.0] (production 5), with the following restrictions:
        1. The name MUST be at least four characters.
        2. Colons MAY be used as intra-name dividers.
        3. Colons MUST NOT appear at the beginning or end of the name.
        4. Consecutive colons MUST NOT appear.
     and the following relaxation:
        5. The first part of the name preceding the first colon MAY
           be comprised of DIGITs (which are intended to correspond
           to registered IANA Private Enterprise Numbers);
           further discussion is in
           "Process of identifier assignment".

       The ABNF of a name is:

        urn-xmlns-name = [DIGIT+ ":"] NoColonNameStartChar
                         *([":"] NoColonNameChar)

     Where the productions NoColonNameStartChar and NoColonNameChar
     are respectively taken from NameStartChar (production 4)
     and NameChar (production 4a) in [XML1.0], with ":" omitted.
     Although ABNF is formally US-ASCII only, the domain of
     this production includes the whole Unicode range.

     The name is used as the basis of the
     Namespace Specific String (NSS) as follows.
     When the NSS is encoded in a URN in a URI protocol slot,
     Unicode code points beyond U+007F
     are encoded as percent-encoded UTF-8. Conveniently,
     all XML name characters in the US-ASCII range are in the
     [RFC3986] unreserved set.
     When the NSS is encoded in a URN in a IRI protocol slot,
     Unicode code points beyond U+007F in the unreserved set
     are encoded as-is; they MUST NOT be percent-encoded.

  Relevant ancillary documentation:
     [XML1.0], [XML1.1].

  Identifier uniqueness considerations:
     The meaning of an identifier is registered in the registry,
     and thus is unique.

  Identifier persistence considerations:
     Once an identifier is registered, its meaning cannot be changed.

  Process of identifier assignment:
     Identifiers are registered with IANA on a First-Come, First-Served
     basis. One-character initial prefixes are reserved for further
     use. Two- and three-character initial prefixes are intended to
     correlate with language tags and regional codes; however, they
     have no such semantic content when used in an xmlns name. Whole
     number initial prefixes are intended to represent IANA
     Private Enterprise Numbers.
     Registrants are free to register names with reserved two-character
     and three-character initial prefixes, such as "au:flag" or
     "en:us:ca:lax". Registrants are also free to register names with
     whole number prefixes, such as "20:10-250": these names have a
     particular registration process since they implicitly relate
     relate to IANA Private Enterprise Numbers.
     The IANA Considerations section fully defines the
     registration processes.

  Process for identifier resolution:
     The registration for a particular identifier MAY include
     any number of URIs that a URN resolver MAY use to resolve
     the URN to return specific resources. The registered
     URIs are not equivalent to the registered URN, so an XML document
     that refers to that particular namespace MUST use the registered
     URN as the XML namespace URI. IANA will maintain the resolution
     database--see Section 4.
     A URN resolver SHALL pass any [RFC3986] fragment component in the
     urn: URI or IRI through to the resolved URI if the registered URI
     does not have a fragment component. See [URNBIS].
     If the registered URI has a fragment component, a URN resolver
     SHALL NOT pass any [RFC3986] fragment component in the urn: URI
     or IRI; the fragment component SHALL be ignored.

  Rules for Lexical Equivalence:
     The NSS is compared case sensitively.
     If a URI and a IRI are compared against each other, the
     UTF-8 percent-encoded octets in the URI representing code points
     in the unreserved set beyond U+007F SHALL be treated
     as the Unicode code points
     in the IRI. An IRI that contains UTF-8 percent-encoded octets
     in the unreserved set beyond U+007F is not supposed to exist;
     it is a protocol error.
     Fragments (delimited by the # character) are not considered
     part of the name, the NSS, or the URN, so a fragment would not
     affect lexical equivalence. Nevertheless, a urn: URI or IRI
     might be produced with a fragment component.

  Conformance with URN Syntax:
     The URN of this namespace conforms to new URN Syntax
     [URNBIS], old URN syntax [RFC2141], and Uniform Resource Identifier
     (URI): Generic Syntax [RFC3986].

  Validation mechanism:
     An XMLNS URN may be validated by looking it up in the IANA Registry.

  Scope:
     Global.

***********

-------- Forwarded Message --------
Subject: 	New Version Notification for draft-seantek-xmlns-rdf-urns-01.txt
Date: 	Fri, 25 Sep 2015 05:53:13 -0700
From: 	internet-drafts@ietf.org



A new version of I-D, draft-seantek-xmlns-rdf-urns-01.txt
has been successfully submitted by Sean Leonard and posted to the
IETF repository.

Name:		draft-seantek-xmlns-rdf-urns
Revision:	01
Title:		URN Namespaces for XML Namespaces and RDF IRIs
Document date:	2015-09-24
Group:		Individual Submission
Pages:		9
URL:            https://www.ietf.org/internet-drafts/draft-seantek-xmlns-rdf-urns-01.txt
Status:         https://datatracker.ietf.org/doc/draft-seantek-xmlns-rdf-urns/
Htmlized:       https://tools.ietf.org/html/draft-seantek-xmlns-rdf-urns-01
Diff:           https://www.ietf.org/rfcdiff?url2=draft-seantek-xmlns-rdf-urns-01

Abstract:
    XML segregates elements into namespaces, which can be used to mix
    tags with different semantics in a composite XML document.  XML
    namespaces are identified by URIs (XML 1.0) or IRIs (XML 1.1).
    Similarly, RDF contains "nodes" that are identified by "URI
    references" (RDF 1.0) or "IRIs" (RDF 1.1).  This document defines
    URNs specifically for XML namespaces and RDF nodes.