Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Re: Whitespace normalization for union types

From: Xan Gregg <xan.gregg@---.--->
To: Kasimier Buchcik <kbuchcik@---------.-->
Date: 6/2/2005 5:34:00 AM
On Jun 1, 2005, at 6:00 PM, Kasimier Buchcik wrote:
> Hmm, I repeat [1]:
> "For all datatypes =B7derived=B7 by =B7union=B7  whiteSpace does not =
apply
> directly; however, the normalization behavior of =B7union=B7 types is
> controlled by the value of whiteSpace on that one of the =B7memberTypes=B7=

> against which the =B7union=B7 is successfully validated."

I don't understand the last use of the word "union" in the quoted text. =

You seem to be reading the word to mean something like "intial value" 
or "pre-normalized string", which sounds reasonable. While I can't make =

sense of it literally, I was reading it to imply that for the member 
type to control the whiteSpace normalization, the value had to also be =

valid against the entire rest of the union type (including facets).

Now that I think about the ramifications, I like your interpretation 
better, mainly because it keeps the base type validation separate.

> I really need some definitive clarification on this.

I think the application of facets to unions is underspecified. 
Afterall, there are statements like:

     The value space and lexical space of a union datatype are the
     union of the value spaces and lexical spaces of its memberTypes.

which ignores the possibility of facets. I don't see any real 
improvement in the 1.1 working draft, either.

xan=


From xan.gregg@j... Thu Jun 02 13:50:09 2005
Received: from 


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