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 1893 - R-203: Inconsistency with constraints on min/maxExclusive
Summary: R-203: Inconsistency with constraints on min/maxExclusive
Status: CLOSED FIXED
Alias: None
Product: XML Schema
Classification: Unclassified
Component: Datatypes: XSD Part 2 (show other bugs)
Version: 1.1 only
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: XML Schema WG
QA Contact: XML Schema comments list
URL:
Whiteboard:
Keywords: resolved
Depends on:
Blocks:
 
Reported: 2005-08-26 13:54 UTC by Sandy Gao
Modified: 2009-04-21 19:21 UTC (History)
0 users

See Also:


Attachments

Description Sandy Gao 2005-08-26 13:54:21 UTC
"Schema Component Constraint: minExclusive valid restriction

It is an error if any of the following conditions is true: 
2 maxInclusive is among the members of {facets} of {base type definition} and 
{value} is greater the {value} of the parent maxInclusive" 
So it's an error for minEx > base.maxIn, which implies minEx <= base.maxIn (if 
minEx == maxIn, it results in an empty value space)

"Schema Component Constraint: maxExclusive valid restriction

It is an error if any of the following conditions is true: 
3 minInclusive is among the members of {facets} of {base type definition} and 
{value} is less than or equal to the {value} of the parent minInclusive" 
So it's an error for maxEx <= base.minIn, which implies maxEx > base.minIn

Isn't this inconsistent? Shouldn't this be either: 

minEx < base.maxIn && maxEx > base.minIn 
or 
minEx <= base.maxIn && maxEx >= base.minIn 

See
http://lists.w3.org/Archives/Public/www-xml-schema-comments/2003JanMar/0037.html
Comment 1 Sandy Gao 2005-10-04 20:45:45 UTC
Discussed at 2005-09-23 telecon.

Resolved: Classify 1893 as error with corrigendum against 1.0, but ask 
implementors which way they resolved the inconsistency before deciding how to 
resolve this.
Comment 2 C. M. Sperberg-McQueen 2005-11-09 12:27:37 UTC
This appears to apply both to 1.0 and to 1.1; since there is not
now a separate issue for 1.1, I'm reassigning this to version
1.0/1.1 both.  This assignment is based on a hasty reading of the
description and may be wrong.
Comment 3 C. M. Sperberg-McQueen 2006-03-21 00:14:40 UTC
The Working Group discussed this issue in the face to face meeting of
January 2006 in St Petersburg, Florida, and adopted a proposal to
change (in 1.1) the relevant part of section 4.3.9.4 to read:

   Schema Component Constraint: minExclusive valid restriction
   It is an ·error· if any of the following conditions is true:
     1 minExclusive is among the members of {facets} of {base type
       definition} and {value} is less than the {value} of that
       minExclusive.
     2 minInclusive is among the members of {facets} of {base type
       definition} and {value} is less than the {value} of that
       minInclusive.
     3 maxInclusive is among the members of {facets} of {base type
       definition} and {value} is greater than or equal to the
       {value} of that maxInclusive.
     4 maxExclusive is among the members of {facets} of {base type
       definition} and {value} is greater than or equal to the
       {value} of that maxExclusive.

The changed wording appears in the Last Call draft of February 2006.