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 3024 - R-258: inclusive and exclusive bounds (1.0)
Summary: R-258: inclusive and exclusive bounds (1.0)
Status: NEW
Alias: None
Product: XML Schema
Classification: Unclassified
Component: Datatypes: XSD Part 2 (show other bugs)
Version: 1.0 only
Hardware: PC Windows 3.1
: P2 normal
Target Milestone: ---
Assignee: David Ezell
QA Contact: XML Schema comments list
URL:
Whiteboard:
Keywords: needsDrafting
Depends on:
Blocks:
 
Reported: 2006-03-21 00:27 UTC by C. M. Sperberg-McQueen
Modified: 2012-12-04 00:54 UTC (History)
0 users

See Also:

Attachments

Description C. M. Sperberg-McQueen 2006-03-21 00:27:52 UTC 
This item was first raised by Sandy Gao in May 2004 
(http://lists.w3.org/Archives/Member/w3c-xml-schema-ig/2004May/0047.html).
This issue is for XML Schema 1.0; the analogous issue for 1.1 is
bug 2250.

The first constraint in 4.3.8.4 of the datatype spec says 

    It is an error for both maxInclusive and maxExclusive to be
    specified in the same derivation step of a datatype
    definition.

And the first constraint [2] in 4.3.9.4 says 

    It is an error for both minInclusive and minExclusive to be
    specified for the same datatype.

Clearly they don't match with each other. IMO, the one in 4.3.9.4
is incorrect, and should be changed to something similar to that
in 4.3.8.4.

At the face to face meeting of January 2006 in St. Petersburg,
Florida, the WG adopted the proposal given above for XML Schema
1.1.