You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@xerces.apache.org by sa...@apache.org on 2003/03/25 23:41:00 UTC
cvs commit: xml-xerces/java/docs xml-schema.xml
sandygao 2003/03/25 14:41:00
Modified: java/docs xml-schema.xml
Log:
Make the schema limitation page in the docs up-to-date.
Revision Changes Path
1.5 +10 -33 xml-xerces/java/docs/xml-schema.xml
Index: xml-schema.xml
===================================================================
RCS file: /home/cvs/xml-xerces/java/docs/xml-schema.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- xml-schema.xml 11 Nov 2002 19:03:24 -0000 1.4
+++ xml-schema.xml 25 Mar 2003 22:41:00 -0000 1.5
@@ -34,49 +34,26 @@
<li> Length, minLength, and maxLength facets are limited to the value
2147483647. Items larger than this limit will not be validated
correctly.</li>
- <li> Year and seconds values in date/time datatypes are limited to the
- value 2147483647. Items larger than this limit will not be validated
- correctly. </li>
+ <li> The values of minOccurs and maxOccurs attributes are limited to
+ the value 2147483647. Items larger than this limit will not be
+ validated correctly.</li>
+ <li> The values of minimum and maximum quantifiers in the pattern
+ regular expressions are limited to the value 2147483647.
+ Items larger than this limit will not be validated correctly.</li>
+ <li> The absolute values of the fraction portion of the second values
+ in date/time datatypes are limited to the value 2147483647.
+ Items larger than this limit will not be validated correctly.
+ i.e. 11.2147483648 is not supported as a second value. </li>
</ul>
</s2>
<s2 title='Problem Areas/Known Bugs'>
<ul>
- <li> Due to changes in the specification for Decimals in
- JDK1.3, not all decimals that should be invalid according
- to the Schema specs may be found by the parser;</li>
<li> For larger values of maxOccurs, a StackOverflowError may occur.
The workaround for this problem, if your application permits it,
is to change the maxOccurs value to unbounded.</li>
-
- </ul>
- </s2>
- <s2 title='Interpretation of Areas that are Unclear or
- Implementation-Dependent'>
- <ul>
- <li> QName: the specification does not define the unit of length. We
- chose to implement the length facet as being in units of XML characters
- in the value space ( # of chars in namespace URI + ":" +
- local part );</li>
- <li> We have interpreted the specs as requiring
- <keyref> Identity Constraints to refer to
- <key> or <unique> identity constraints within
- the scope of the elements to which the <keyref> is
- attached. This interpretation is at variance with the
- Schema Primer, which contains an example with a
- <keyref> declared on an element used inside the
- element of its corresponding <key>;</li>
</ul>
</s2>
<s2 title="Other Notes">
- <p> The parsers contained in this package are able to read and
- validate XML documents with the grammar specified in either
- DTD or XML Schema format.
- The schema is specified by the xsi:schemaLocation or
- xsi:noNamespaceSchemaLocation attribute on the root
- element of the document. The xsi prefix must be bound to the
- Schema document instance namespace, as specified by the
- Recommendation. See the sample provided in the
- Usage section.</p>
<p> As of version 2.2.1, it is hoped that Xerces-J will always
be able to parse the Schema for Schemas current at the time of the product's release. As of version
2.2.1, this implies inserting special logic to permit the presence of
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-cvs-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-cvs-help@xml.apache.org