W3C home > Mailing lists > Public > www-xml-schema-comments@w3.org > July to September 2005

[Bug 1893] New: R-203: Inconsistency with constraints on min/maxExclusive

From: <bugzilla@wiggum.w3.org>
Date: Fri, 26 Aug 2005 13:54:21 +0000
To: www-xml-schema-comments@w3.org
Cc:
Message-Id: <E1E8eez-0007Ea-6d@wiggum.w3.org>

http://www.w3.org/Bugs/Public/show_bug.cgi?id=1893

           Summary: R-203: Inconsistency with constraints on
                    min/maxExclusive
           Product: XML Schema
           Version: 1.0
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: XSD Part 2: Datatypes
        AssignedTo: cmsmcq@w3.org
        ReportedBy: sandygao@ca.ibm.com
         QAContact: www-xml-schema-comments@w3.org


"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
Received on Friday, 26 August 2005 13:54:23 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Sunday, 6 December 2009 18:13:09 GMT