Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


RE: Is a token element with a carriage return, or leading/trailing spaces, valid?

From: "Costello, Roger L." <costello@-----.--->
To: <xmlschema-dev@--.--->
Date: 2/15/2007 9:37:00 AM
 
Thanks Michael and Jerry.

I looked at the datatypes schema, and I see how the token datatype has
been defined with whitespace set to collapse.  I understand why my
examples should validate.

This spawns another question.

Consider these two declarations for element Title:

      <element name="Title" type="token"/>

      <element name="Title" type="string"/>

Consider an instance of Title:

      <Title>_______</Title>

Any value that I put in will yield the same validation results,
regardless of whether Title was declared to be of type token or string.
For example, this yields "valid"

      <Title>My Life and 
      Times</Title>

for both declarations.  And this yields "invalid"

      <Title>&#x0;</Title>

for both declarations.

Aren't the two declarations identical?  In fact, aren't they also
identical to this:

      <element name="Title" type="normalizedString"/>

Under what cases do they differ? (e.g., it yields "valid" when of type
string, but "invalid" when of type token)

/Roger


-----Original Message-----
From: Michael Kay [mailto:mike@s...] 
Sent: Thursday, February 15, 2007 11:35 AM
To: Costello, Roger L.; xmlschema-dev@w...
Subject: RE: Is a token element with a carriage return, or
leading/trailing spaces, valid?

These instances are valid.

People often misread this bit of the spec, because it's very badly
written.
What isn't immediately clear is that when it talks about the lexical
space
of the data type, that isn't the value as it appears in your source
document, it's the value after applying any processing implied by the
whitespace facet. In this case, applying the whitespace facet creates a
value that satisfies the rules for the lexical space.

The fact that xs:token is such a ridiculous misnomer for this data type
doesn't help...

Michael Kay
http://www.saxonica.com/

 

> -----Original Message-----
> From: xmlschema-dev-request@w... 
> [mailto:xmlschema-dev-request@w...] On Behalf Of Costello, Roger L.
> Sent: 15 February 2007 15:48
> To: xmlschema-dev@w...
> Subject: Is a token element with a carriage return, or 
> leading/trailing spaces, valid?
> 
> 
> Hi Folks,
>  
> Consider this element declaration:
>  
>       <element name="Title" type="token"/>
> 
> And consider these two instances of the element:
> 
>       <Title>My Life and 
>       Times</Title>
> 
>       <Title> My Life and Times </Title>
> 
> In the first instance, the data has a carriage return.
> 
> In the second instance, the data has leading and trailing spaces.
> 
> Are the instances valid or invalid?
> 
>     XMLSpy">XMLSpy says they are invalid.
> 
>     Oxygen XML says they are valid.
> 
> Which is correct?
> 
> /Roger
> 


From mike@s... Thu Feb 15 20:18:01 2007
Received: from lisa.w3.org ([128.30.52.41])
	by frink.w3.org with esmtp (Exim 4.50)
	id 1HHn3J-0003iu-0E
	fo


transparent
Print
Mail
Digg
delicious
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