NMTOKEN in framedefs etc was Re: LC model draft draft-ietf-forces-model-07.txt

In several places in s.4, name spaces are implied by such as
"Each ... (frame definition) MUST contain a unique name (NMTOKEN) "
and
"Uniqueness is defined to be over all ....defined in this library document and
in all directly or indirectly included library documents."

Sounds great in theory but a nightmare in practice; what happens when a new
library document is included which has a clash with an existing name; who
changes what?  More bacically, who enforces uniqueness?

It all seems unnecessarily complex; why not make it unique, period?  This is a
well trodden path for WGs, setting up an IANA registry with controlled (eg
Expert Review, Standardss Track RFC) or uncontrolled (FCFS) updates, perhaps
with a split in the namespace between IETF and vendor defined names.

Also, for framedefs, it looks as if this unique name is the
<name> in here </name>
element  in which case I think that worth spelling out.

And what is NMTOKEN? Reverse engineering the Schema, I see it is a type
(previously used by BEEP/SOAP, I find) which the W3C XML datatype pages explain
as

"[Definition:]   NMTOKEN represents the NMTOKEN attribute type from [XML 1.0
(Second Edition)]. The ·value space· of NMTOKEN is the set of tokens that
·match· the Nmtoken production in [XML 1.0 (Second Edition)]. The ·lexical
space· of NMTOKEN is the set of strings that ·match· the Nmtoken production in
[XML 1.0 (Second Edition)]. The ·base type· of NMTOKEN is token."

Well yes, I would like to see some more explanation for this new (to me) concept
rather than just the bracketed term.

Tom Petch

----- Original Message -----
From: "Patrick Droz" <[email protected]>
To: <[email protected]>
Sent: Friday, October 13, 2006 10:36 AM
Subject: LC model draft draft-ietf-forces-model-07.txt


> I would like to issue last call on the model draft. As this is
> a fairly large document the LC will last for 3 weeks and will
> therefore end just before the next IETF. It is draft:
> draft-ietf-forces-model-07.txt
> and can be found at:
> http://www.ietf.org/internet-drafts/draft-ietf-forces-model-07.txt
>
> A number of people have indicated that if the document is in
> LC they would thoroughly review the document. I hope people will
> stick to their promises.
>
> Regards,
> Patrick
>
>
>