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

Isn't maxExclusive too... exclusive ?

From: Eric van der Vlist <vdv@dyomedea.com>
Date: Mon, 08 Oct 2001 09:44:37 +0200
Message-ID: <3BC15965.6090603@dyomedea.com>
To: xmlschema-dev@w3.org
"[Definition:]   maxExclusive is the ·exclusive upper bound· of the 
·value space· for a datatype with the ·ordered· property. The value of 
maxExclusive  ·must· be in the ·value space· of the ·base type·."

If I write:

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

Then

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

should be an error since "5" isn't in the value space of base datatype 
"foo", but the comment about "fixed":

"If {fixed} is true, then types for which the current type is the {base 
type definition} cannot specify a value for maxExclusive other than 
{value}."

makes me think that this should be allowed at least when fixed="true"...

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:44:20 GMT

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