Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Re: Discrepancies in the W3C Schema docs?

From: "Pete Cordell" <petexmldev@--------------.--->
To: "Dan Maharry" <dan@---.---->, <xmlschema-dev@--.--->
Date: 6/11/2007 12:19:00 PM
----- Original Message From: "Dan Maharry" <dan@m...>

> Problem #4 : Single spaces or more?
> ...
> and [the] Names [production] reveals that it means each IDREF must be
> separated by a single \x20 character only else the string isn't a valid
> IDREFS type string.
>
> Names   ::=   Name (#x20 Name)*
>
>  So why can't the schema spec just say something like
>
> The *lexical space* of IDREFS is the set of lists of tokens each
> separated by a single \x20 character,....

I'm not even sure this is the whole story.  Section 3.3.3 Attribute-Value 
Normalization, of the XML 1.0 (Third Edition) says,

    Before the value of an attribute is passed to the application or checked 
for
    validity, the XML processor MUST normalize the attribute value...

So I think IDREFS only needs to match Names after normalization.

I've always assumed that the lexical space is pre-normalization, but I can't 
at the moment find anything that tells me this either way.

Pete.
--
=============================================
Pete Cordell
Codalogic Ltd
for XML Schema to C++ data binding visit
 http://www.codalogic.com/lmx/
=============================================



From dan@m... Mon Jun 11 14:09:22 2007
Received: from aji.w3.org ([133.27.2


transparent
Print
Mail
Like It
Disclaimer
.

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.

.
.

transparent

transparent