The QName URN Namespace

Glossary

The identifier is a name for the issue (and is unique within this document).

The type of issue is one of:

The status of the issue is one of:

The reference is an indication of where the issue was first raised.

The description is a succinct overview of the issue.

The resolution describes the specification change that resolves the issue.

Open Issues

Identifier Type / Status Reference and Description Proposed Resolution / Latest Change
any-­uri
change
open
julian.reschke@greenbytes.de, 2009-12-12: Need a grammar for "any valid URI". Do we follow stricly XMLNS, which would make it a "URI reference" as per RFC 3986, or do we tolerate junk and/or IRIs (no offense). Also, we need to state that this part of the URN will be empty for elements that are in no namespace (right?).

julian.reschke@greenbytes.de, 2010-03-07: In particular: how do we treat namespace names that use a fragment identifier? We can't allow the "#" character in the URN (by definition).
latest change in revision latest
curie
edit
open
julian.reschke@greenbytes.de, 2009-12-12: Maybe we should clarify the relation with CURIEs (which can be confused with QNames)? latest change in revision latest
edit
edit
open
julian.reschke@greenbytes.de, 2010-03-07: Umbrella issue for editorial changes. latest change in revision latest
examples
change
open
julian.reschke@greenbytes.de, 2009-12-11: Having just examples of QNames in element content might be confusing to people not familiar with that use case; we also should have at least one example for an XML element name, and for a QName in content. (potentially also move the examples out of the registration template?) latest change in revision latest
i18n
change
open
julian.reschke@greenbytes.de, 2009-12-11: Need to state how non-ASCII characters are mapped to the URN. latest change in revision latest
qname-­vs-­expname
edit
open
julian.reschke@greenbytes.de, 2009-12-12: There's a risk that we confuse people by claiming this is about QNames. What we map to URNs is the triple (namespace-name, local-name, prefix), where the prefix is optional. The tuple (namespace-name, local-name) is the *expanded name*, not the QName. Options: (1) just clarify the prose, (2) rename the URN scheme (is it in use already?) to something like "xmlname". latest change in revision latest
reg-­info
edit
open
julian.reschke@greenbytes.de, 2009-12-11: Update registration info. latest change in revision latest

Closed/Editor Issues

Identifier Type / Status Reference and Description Resolution / Latest Change
contacts
edit
closed
julian.reschke@greenbytes.de, 2009-12-11: Update author information. in revision 02:
Done in -01.
mailing-­list
edit
closed
julian.reschke@greenbytes.de, 2009-12-12: In the boilerplate, state where this Internet Draft should be discussed. Proposal: xml-dev. in revision 02:
Done in -01.
registrant
edit
closed
julian.reschke@greenbytes.de, 2009-12-11: Update registrant info. in revision 02:
Make the editor the registrant.
xml11
change
closed
julian.reschke@greenbytes.de, 2009-12-11: Consider removing any material related to XML 1.1. in revision 02:
Done.

Progress

Version Issues
latest |||||||||||
02 |||||||||||
01 ||||||||||
00

Last change: 2010-03-07