Re: On ACTION-118: Summarize issues relating to XSD canonicalization

XML Schema 1.1 changes the case for xsd:decimal canonicalization of 
integer values.

http://www.w3.org/TR/xmlschema11-2/#decimal

3.3.3 decimal
3.3.3.1 Lexical Mapping

[3]   decimalLexicalRep ::= decimalPtNumeral | noDecimalPtNumeral

...
The definition of the ·canonical representation· has the effect of 
prohibiting certain options from the Lexical Mapping (§3.3.3.1). 
Specifically, for integers, the decimal point and fractional part are 
prohibited.


Under XML Schema 1.0, the decimal point was required in the lexical form 
(canonical or not).

	Andy


On 18/01/12 16:26, Jeremy Carroll wrote:
>
> Built-in derived datatypes may have different canonicalization rules
> from the primtiives.
>
> Example issue:
> "1"^^xsd:short and "1.0"^^xsd:decimal are both in canonical form.
> They have the same value. It is 'natural' for certain RDF systems to
> canonicalize the former to the latter changing it's lexical form.
>
> Thus any dependence from RDF on XSD canonicalization needs significant
> care.
>
> Jeremy
>
>
> http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/#decimal
>
>
> [[
> 3.2.3.2 Canonical representation
>
> The canonical representation for decimal is defined by prohibiting
> certain options from the Lexical representation (§3.2.3.1).
> Specifically, the preceding optional "+" sign is prohibited. The decimal
> point is required. Leading and trailing zeroes are prohibited subject to
> the following: there must be at least one digit to the right and to the
> left of the decimal point which may be a zero.
>
> ]]
>
> http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/#short
> [[
> 3.3.18.2 Canonical representation
>
> The canonical representation for short is defined by prohibiting certain
> options from the Lexical representation (§3.3.18.1). Specifically, the
> the optional "+" sign is prohibited and leading zeroes are prohibited.
>
> ]]
>
>
>
>

Received on Wednesday, 18 January 2012 17:25:04 UTC