W3C home > Mailing lists > Public > xmlschema-dev@w3.org > October 2001

Why can minExclusive be equal to maxExclusive?

From: Eric van der Vlist <vdv@dyomedea.com>
Date: Mon, 08 Oct 2001 09:54:02 +0200
Message-ID: <3BC15B9A.4080703@dyomedea.com>
To: xmlschema-dev@w3.org
"Schema Component Constraint: minExclusive <= maxExclusive
It is an ·error· for the value specified for ·minExclusive· to be 
greater than the value specified for ·maxExclusive· for the same datatype."

What's the point of allowing:

<xs:simpleType name="foo">
  <xs:restriction base="xs:float">
   <xs:maxExclusive value="5"/>
   <xs:minExclusive value="5"/>
  </xs:restriction>
</xs:simpleType>

since the value space of this datatype is empty?

Eric
-- 
Rendez-vous à Paris pour une visite guidee de la nebuleuse XML.
                                           http://dyomedea.com/formation/
------------------------------------------------------------------------
Eric van der Vlist       http://xmlfr.org            http://dyomedea.com
http://xsltunit.org      http://4xt.org           http://examplotron.org
------------------------------------------------------------------------
Received on Monday, 8 October 2001 03:53:42 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 11 January 2011 00:14:24 GMT