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

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


cmsmcq@w3.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |RESOLVED
           Keywords|needsAgreement              |resolved
         Resolution|                            |FIXED
            Version|1.0/1.1 both                |1.1 only




------- Comment #3 from cmsmcq@w3.org  2006-03-21 00:14 -------
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.

Received on Tuesday, 21 March 2006 00:14:45 UTC