Checking Enumerative QNames for the TAML-defined simple values

["Dennis E. Hamilton" <dennis.hamilton@acm.org>]

I'm not much of a schema head, but I think you can do what you want in a
modestly-awkward way.

1. For the QNames, the only permitted form for open-ended extensions have a
":" in them somewhere.   Other than those, the only permitted ones should be
the (unprefixed) ones we define as part of the TAML specification.  

2. You might have to do a Union to make it work.  That is have a QName where
a ":" is required.  Then union with an NCName restricted to the literal
values that are defined in the TAML specification.

3. This is only awkward because each restricted enumerated-attribute value
that is extensible with PrefixedNames has its plain values restricted
independently, so we can't use a new derived type to handle this.

Does this work for you?

 - Dennis

PS: I don't talk about typos because there is no way to distinguish between
a typo, a non-conformant document, and an up-level document being attempted
by a processor using a down-level schema.  They all look like documents that
don't satisfy the schema.  Processors might be creative about helping users
find errors and recognize their causes.  I would be amazed if anyone went
very far with this for TAML.  

-----Original Message-----
From: stephengreenubl@gmail.com [mailto:stephengreenubl@gmail.com] On Behalf
Of Stephen Green
http://lists.oasis-open.org/archives/tag/200911/msg00059.html
Sent: Sunday, November 15, 2009 00:53
To: dennis.hamilton@acm.org
Cc: TAG TC List
Subject: Re: [tag] Re: Considerations for TAML Authoring and
normalizedString

[ ... ]

There is still an issue that typos in the existing built-in codes
won't be picked up by the schema - they will still be acceptable
as QNames without a prefix.

[ ... ]