You are viewing a plain text version of this content. The canonical link for it is here.
Posted to j-dev@xerces.apache.org by bu...@apache.org on 2001/02/27 22:28:20 UTC
[Bug 740] New - An error is not raised by the parser for the constraint violation minInclusive <= maxInclusive
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=740
*** shadow/740 Tue Feb 27 13:28:20 2001
--- shadow/740.tmp.4276 Tue Feb 27 13:28:20 2001
***************
*** 0 ****
--- 1,39 ----
+ +============================================================================+
+ | An error is not raised by the parser for the constraint violation minInclu |
+ +----------------------------------------------------------------------------+
+ | Bug #: 740 Product: Xerces-J |
+ | Status: NEW Version: 1.3.0 |
+ | Resolution: Platform: PC |
+ | Severity: Normal OS/Version: |
+ | Priority: Component: Schema-Datatypes |
+ +----------------------------------------------------------------------------+
+ | Assigned To: xerces-j-dev@xml.apache.org |
+ | Reported By: nddelima@ca.ibm.com |
+ | CC list: Cc: |
+ +----------------------------------------------------------------------------+
+ | URL: |
+ +============================================================================+
+ | DESCRIPTION |
+ Description:
+ The parser does not raise an error for a simpleType derived by restriction from
+ the Primitive datatype float, with facets minInclusive <= maxInclusive.
+
+
+ Reference:
+ Constraint on Schemas: minInclusive <= maxInclusive
+ "It is an error for the value specified for minInclusive to be greater than the
+ value specified for maxInclusive for the same datatype"
+
+ Section 4.2.7 of
+ XML Schema Part 2: Datatypes
+ W3C Candidate Recommendation 24 October 2000
+
+
+ Example:
+ The section of code that should have raised an error but did not is as below.
+ <simpleType name="myFloat">
+ <restriction base="float">
+ <minExclusive value="9.99"/>
+ <maxExclusive value="99.99"/>
+ </restriction>
+ </simpleType>