This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 2064 - R-075: Potential problem with the rules for maxExclusive
Summary: R-075: Potential problem with the rules for maxExclusive
Status: CLOSED FIXED
Alias: None
Product: XML Schema
Classification: Unclassified
Component: Datatypes: XSD Part 2 (show other bugs)
Version: 1.0 only
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: C. M. Sperberg-McQueen
QA Contact: XML Schema comments list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-09-09 02:53 UTC by Sandy Gao
Modified: 2009-04-21 19:24 UTC (History)
0 users

See Also:


Attachments

Description Sandy Gao 2005-09-09 02:53:20 UTC
The following example is invalid according to the definition of maxExclusive, 
which states that "The value of maxExclusive must be in the value space of the 
base type":

 <xs:simpleType name="foo">
   <xs:restriction base="xs:float">>
    <xs:maxExclusive value="5"/>
   </xs:restriction>
 </xs:simpleType>
 
 
 <xs:simpleType name="bar">
   <xs:restriction base="foo">
    <xs:maxExclusive value="5"/>
   </xs:restriction>
 </xs:simpleType>
Should the example be valid if "fixed" is specified for maxExclusive in the 
base?

See:
http://lists.w3.org/Archives/Public/www-xml-schema-comments/2001OctDec/0041.html
Comment 1 Sandy Gao 2005-09-09 02:53:48 UTC
At the 12/20/2001 telecon, the WG decided to treat R-75 as an error and to 
instruct the editor to change the text to specify that the value of 
maxExclusive must be in the value space of the base type, or else the same 
value as the effective maxExclusive facet of the base type (if any). 

April 5: proposed erratum approved by WG.

Erratum E2-39 has been added to the errata doc.