Re: Pls check draft-mealling-iana-xmlns-registry-04.txt

[Andy Bierman <abierman@cisco.com>]

At 12:47 PM 4/26/2003, Wijnen, Bert (Bert) wrote:
>It is on IESG agenda to be approved as BCP.
>It probably has impact on how you name and register namespaces
>for the protocol being developed.

I think this draft focuses on how various XML related identifiers
are registered with IANA.

The two classes affecting this WG are:

   ns -- XML Namespaces [W3C.REC-xml-names] are named by a URI.  They
      have no real, machine-parseable representation.  Thus the
      registered document will be either the specification or a
      reference to it.  In the case where a URI is not provided by the
      registrant, the IANA will assign a URN of the form
      'urn:ietf:params:xml:ns:<id> which will be the XML Namespace's
      name.

   schema -- XML Schemas [W3C.REC-xmlschema-1] are also identified by a
      URI but their contents are machine parseable.  The IANA registered
      document will be the XML Schema file.  The URN the IANA assigns
      can be used as the URI for the schema and is of the form
      'urn:ietf:params:xml:schema:&ltid>'.
                                  ^^^
                                  note the bug in the src; should be &lt;

Some issues for this WG:

1) Namespace structure
   It will be useful to define a structure to this type of URI.
   Fields that are useful:
      - naming authority  
        e.g., ietf.org in http://ietf.org/xmlconf/1.0/base
      - category 
        e.g., xmlconf in http://ietf.org/xmlconf/1.0/base
      - sub-category
        e.g., base in http://ietf.org/xmlconf/1.0/base
      - version
        e.g., 1.0 in http://ietf.org/xmlconf/1.0/base

   Whether xmlconf got the field order right or has the complete list 
   of fields is open to discussion. 

2) Separate classes for namespaces and schemas
   AFAIK, the XML Schema specification does not define a separate
   URI for a schema and a namespace. The targetNamespace parameter
   refers to the namespace the schema is defined in, not the actual 
   schema document itself.

General issues with the document:

1) no examples
   It would be easier to understand this document if there were some
   examples of each type of identifier.  There are no examples at all
   in this document.

2) explanation of static fields
   Given the structure 'urn:ietf:params:xml:<class>:<id>'
   there is no mention of the static fields 'urn:ietf:params:xml'
   What is the 'params' field used for? It doesn't seem to be useful. 


>Thanks,
>Bert 

Andy


--
to unsubscribe send a message to xmlconf-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/xmlconf/>