W3C home > Mailing lists > Public > xmlschema-dev@w3.org > February 2007

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

From: Michael Kay <mike@saxonica.com>
Date: Thu, 15 Feb 2007 16:35:21 -0000
To: "'Costello, Roger L.'" <costello@mitre.org>, <xmlschema-dev@w3.org>
Message-ID: <014a01c7511f$497a5b20$6401a8c0@turtle>

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@w3.org 
> [mailto:xmlschema-dev-request@w3.org] On Behalf Of Costello, Roger L.
> Sent: 15 February 2007 15:48
> To: xmlschema-dev@w3.org
> 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?
> 
>     XML Spy says they are invalid.
> 
>     Oxygen XML says they are valid.
> 
> Which is correct?
> 
> /Roger
> 
Received on Thursday, 15 February 2007 16:35:47 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 14:56:11 UTC