neilg 01/06/22 12:31:02
Modified: sources/xerces-j faq-general.xml properties.xml releases.xml
schema.xml
Log:
updates for Xerces-J 1.4.1
Revision Changes Path
1.4 +11 -0 xml-site/sources/xerces-j/faq-general.xml
Index: faq-general.xml
===================================================================
RCS file: /home/cvs/xml-site/sources/xerces-j/faq-general.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- faq-general.xml 2001/05/22 20:18:39 1.3
+++ faq-general.xml 2001/06/22 19:30:59 1.4
@@ -125,6 +125,13 @@
<faq title="International Encodings">
<q>What international encodings are supported by
&javaparsername;?</q>
<a>
+ <p> In general, the parser supports all IANA encodings and
+ aliases (see
+ <jump href="http://www.iana.org/assignments/character-sets";>
+ http://www.iana.org/assignments/character-sets</jump>) that
+ have clear mappings to Java encodings (see
+ <jump
href="http://java.sun.com/j2se/1.3.0/docs/guide/intl/encoding.doc.html";>here</jump>
+ for details). Some of the more common encodings are:</p>
<ul>
<li>UTF-8</li>
<li>UTF-16 Big Endian, UTF-16 Little Endian</li>
@@ -174,6 +181,10 @@
<li>EBCDIC Arabic (ebcdic-cp-ar1)</li>
</ul>
</ul>
+ <p> Please also look at the documentation for the feature
+ "http://apache.org/xml/features/allow-java-encodings"
+ which provides a mechanism for using the
+ encoding names recognized directly by Java.</p>
</a>
</faq>
1.4 +34 -0 xml-site/sources/xerces-j/properties.xml
Index: properties.xml
===================================================================
RCS file: /home/cvs/xml-site/sources/xerces-j/properties.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- properties.xml 2001/05/22 20:18:47 1.3
+++ properties.xml 2001/06/22 19:31:00 1.4
@@ -45,6 +45,40 @@
<tr><th>Note:</th> <td>This property is
currently not supported because the contents of the
XML string returned by this property is not well defined.</td></tr>
</table>
+
+ <anchor name="xml-string"/>
+
<p>http://apache.org/xml/properties/schema/external-schemaLocation</p>
+ <table>
+ <tr><th>Type:</th> <td>java.lang.String</td></tr>
+ <tr><th>Access:</th> <td>read-write</td></tr>
+ <tr><th>Desc:</th> <td>The XML Schema
Recommendation explicitly states that the inclusion of schemaLocation/
noNamespaceSchemaLocation attributes is only a hint; it does not mandate
+ that these attributes must be used to locate
schemas. This property
+ allows the user to specify a list of schemas to use.
+ If the targetNamespace of a schema (specified using
this property)
+ matches the targetNamespace of a schema occuring in
the instance document
+ in schemaLocation attribute, the schema specified by
the user using this
+ property will be used (i.e., the instance
document's schemaLocation attribute will be effectively ignored).
+ </td></tr>
+ <tr><th>Note:</th> <td>The syntax is the same as
for schemaLocation attributes in
+ instance documents: e.g, "http://www.example.com
file_name.xsd".
+ The user can specify more than one XML Schema in the
list.
+ </td></tr>
+ </table>
+
+ <anchor name="xml-string"/>
+
<p>http://apache.org/xml/properties/schema/external-noNamespaceSchemaLocation</p>
+ <table>
+ <tr><th>Type:</th> <td>java.lang.String</td></tr>
+ <tr><th>Access:</th> <td>read-write</td></tr>
+ <tr><th>Desc:</th> <td>This property allows the
user to specify an XML Schema with no namespace.
+ </td></tr>
+ <tr><th>Note:</th> <td>The syntax is a same as for
the noNamespaceSchemaLocation
+ attribute that may occur in an instance document:
+ e.g."file_name.xsd". The user may specify only one
XML Schema. For more information see the documentation for the
+
http://apache.org/xml/properties/schema/external-schemaLocation
+ property</td></tr>
+ </table>
+
</s2>
<s2 title="DOM Parser Properties">
1.4 +11 -0 xml-site/sources/xerces-j/releases.xml
Index: releases.xml
===================================================================
RCS file: /home/cvs/xml-site/sources/xerces-j/releases.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- releases.xml 2001/05/22 20:18:51 1.3
+++ releases.xml 2001/06/22 19:31:00 1.4
@@ -2,6 +2,17 @@
<!DOCTYPE s1 SYSTEM "./dtd/document.dtd">
<s1 title="Releases">
+ <s2 title='June 22, 2001 (version 1.4.1)'>
+ <ul>
+ <li>Added support for all IANA encoding aliases which have a clear
mapping to
+ encodings recognized by Java [Neil Graham]</li>
+ <li> Addressed degradations in DTD validation performance
+ caused by the schema implementation [Sandy Gao, Neil Graham]</li>
+ <li>Bug fixes [Sandy Gao, Neil Graham, Elena Litani, Lisa Martin,
Henry Zongaro, Edwin Goei] </li>
+ <li>Added support for setAttribute/getAttribute in JAXP [Edwin
Goei]</li>
+ <li>Added two new parser properties related to XML Schema [Elena
Litani]</li>
+ </ul>
+ </s2>
<s2 title='May 22, 2001 (version 1.4.0)'>
<ul>
<li>Completed implementation of schema Identity Constraints [Neil
Graham]</li>
1.4 +27 -14 xml-site/sources/xerces-j/schema.xml
Index: schema.xml
===================================================================
RCS file: /home/cvs/xml-site/sources/xerces-j/schema.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- schema.xml 2001/05/22 20:18:57 1.3
+++ schema.xml 2001/06/22 19:31:00 1.4
@@ -26,24 +26,29 @@
<li>No interface is provided for exposing the post-schema
validation infoset , beyond
that provided by DOM or SAX;</li>
+ <li> The parser permits situations in which there is
+ circular importing; that is, where there
+ is a series of schemas which contain <import>
+ information items whose effect is
+ recursive. However, the parser only permits forward
+ references--that is, references directed from the
+ direction of the schema cited in the instance
+ document to other schemas. For instance, if schema A
+ imports schema B which also imports schema A, and an
+ instance document validates against schema A, then
+ any reference in schema b to an information item from
+ schema A will produce an error. Circular
+ <include>s have similar limitations.</li>
<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>There is currently no checking for constraint
ct-cos-extends.1.5</li>
</ul>
</s2>
<s2 title='Problem Areas/Known Bugs'>
<ul>
- <li> Handling of <any> schema information items is
- not completely correct;</li>
- <li> 'id' attributes appearing on schema
- element information items are not treated
- correctly--uniqueness of their values is not
- mandated;</li>
- <li> relative URIs are not handled correctly;</li>
<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>
@@ -76,18 +81,26 @@
Schema document instance namespace, as specified by the
Recommendation. See the sample provided in the
Usage section.</p>
- <p>Finally, note that in <all> model groups fewer than 8
elements must
- be used.</p>
</s2>
<s2 title="Usage">
<p>In this release, schema validation has been integrated with
the
regular SAXParser and DOMParser classes. No special classes are
required to parse documents that use a schema.</p>
- <p>Documents that use XML Schema grammars specify the location
of the
- grammar using an xsi:schemaLocation attribute if they use
+ <p>Schema grammars can be associated with instance
+ documents in two ways. An application developer may use
+ the
+
<code>http://apache.org/xml/properties/schema/external-schemaLocation</code>
+ and the
+
<code>http://apache.org/xml/properties/schema/external-noNamespaceSchemaLocation</code>
+ properties to associate schemas with namespaces appearing in
+ instance documents; see the "properties"
+ section of this documentation for details. If this
+ property is not set, then each
+ document that uses XML Schema grammars must specify the
location of the
+ grammars it uses by using an xsi:schemaLocation attribute if they
use
namespaces, and an xsi:noNamespaceSchemaLocation attribute
- otherwise. These should be attached to the root / top-level
element
- in the document (for more details see XML Schema Part 1 section
4.3.2).
+ otherwise. These are usually placed on the root / top-level
element
+ in the document, though they may occur on any element; for more
details see XML Schema Part 1 section 4.3.2.
Here is an example with no target namespace: </p>
<source><document
xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance'
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
