You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@xerces.apache.org by ne...@apache.org on 2001/12/17 20:38:15 UTC
cvs commit: xml-xerces/java/docs faq-general.xml faq-pcfp.xml
neilg 01/12/17 11:38:15
Modified: java/docs faq-general.xml faq-pcfp.xml
Log:
a few corrections + a number of wordsmithing fixes for the documentation.
Revision Changes Path
1.19 +18 -9 xml-xerces/java/docs/faq-general.xml
Index: faq-general.xml
===================================================================
RCS file: /home/cvs/xml-xerces/java/docs/faq-general.xml,v
retrieving revision 1.18
retrieving revision 1.19
diff -u -r1.18 -r1.19
--- faq-general.xml 2001/12/17 18:23:41 1.18
+++ faq-general.xml 2001/12/17 19:38:14 1.19
@@ -6,8 +6,8 @@
<a>
<p>
You can turn validation on and off via methods available
- on the SAX2 <code>XMLFilter</code> interface. While only the
- <code>SAXParser</code> implements the <code>XMLFilter</code>
+ on the SAX2 <code>XMLReader</code> interface. While only the
+ <code>SAXParser</code> implements the <code>XMLReader</code>
interface, the methods required for turning on validation
are available to both parser classes, DOM and SAX.
<br/>
@@ -21,18 +21,26 @@
</a>
</faq>
<faq title='IDs and XML Schemas'>
- <q>Why getElementById() does not always work for documents validated against XML Schemas?</q>
+ <q>Why does getElementById() not always work for documents validated against XML Schemas?</q>
<a>
- <p>According to XML Schema specification, an instance document might have
-more than one <jump href="http://www.w3.org/TR/xmlschema-1/#key-vr">validation root</jump> and <jump href="http://www.w3.org/TR/xmlschema-1/#cvc-id">ID/IDREFS</jump> must be unique only within validation root, meaning that a document may have identical ids. In this case, the output of getElementById() is unspecified. On the other hand, if document root is a validation root of the document, getElementById() should work as expected.
+ <p>According to the XML Schema specification, an instance document might have
+more than one <jump href="http://www.w3.org/TR/xmlschema-1/#key-vr">validation root</jump> and
+<jump href="http://www.w3.org/TR/xmlschema-1/#cvc-id">ID/IDREFS</jump> must be
+unique only within the context of a particular validation root, meaning that a
+document may potentially contain multiple identical ids. In this case, the output
+of getElementById() is unspecified. On the other hand, if the document root is
+a validation root of the document, getElementById() should work as expected.
</p>
</a>
</faq>
<faq title='PSVI'>
- <q>How do I get access to PSVI?</q>
+ <q>How do I get access to the PSVI?</q>
<a>
- <p>Xerces provides a sample component PSVIWriter that intercepts document handler events and collects PSVI information. For more information read <link idref="samples-xni">samples documentation</link> on how to use xni.parser.PSVIParser and xni.parser.PSVIConfiguration.
+ <p>Xerces provides a sample component PSVIWriter that intercepts document
+handler events and collects PSVI information. For more information read <link
+idref="samples-xni">samples documentation</link> on how to use xni.parser.PSVIParser
+and xni.parser.PSVIConfiguration.
</p>
<note>Xerces only produces light-weight PSVI.</note>
</a>
@@ -64,11 +72,11 @@
<li>Chinese (big5)</li>
<li>Chinese for PRC (mixed 1/2 byte) (gb2312)</li>
<li>Japanese ISO-2022-JP (iso-2022-jp)</li>
- <li>Cyrllic (koi8-r)</li>
+ <li>Cyrillic (koi8-r)</li>
<li>Extended Unix Code, packed for Korean (euc-kr)</li>
<li>Russian Unix, Cyrillic (koi8-r)</li>
<li>Windows Thai (cp874)</li>
- <li>Latin 1 Windows (cp1252)</li>
+ <li>Latin 1 Windows (cp1252) (and all other cp125? encodings recognized by IANA)</li>
<li>cp858</li>
<li>EBCDIC encodings:</li>
<ul>
@@ -92,6 +100,7 @@
<li>Latin 0 EBCDIC</li>
<li>EBCDIC Arabic (ebcdic-cp-ar1)</li>
</ul>
+ <note>UCS-4 is not yet supported, but it is hoped that support will be available soon.</note>
</ul>
</a>
</faq>
1.4 +18 -7 xml-xerces/java/docs/faq-pcfp.xml
Index: faq-pcfp.xml
===================================================================
RCS file: /home/cvs/xml-xerces/java/docs/faq-pcfp.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- faq-pcfp.xml 2001/12/14 21:18:35 1.3
+++ faq-pcfp.xml 2001/12/17 19:38:14 1.4
@@ -16,9 +16,15 @@
<q>What validation behavior do I expect from the default parser configuration?</q>
<a>
<p>
- The default configuration (StandardParserConfiguration) includes DTD validator and Namespace binder. Thus, the <link idref='features' anchor="validation">validation feature</link> will enable validation against DTD only.
-To allow validation against XML Schemas you must turn on the <link idref='features' anchor="validation">validation feature</link> and the <link idref='features' anchor="validation.schema">schema feature</link>, and XML Schema Validator will be inserted in the pipeline.
-If you've created your own configuration which does not extend StandardParserConfiguration, you must make sure that your configuration inserts all needed validators in the pipeline.
+ The default configuration (StandardParserConfiguration) includes the DTD validator
+ and the Namespace binder. Thus, the <link idref='features' anchor="validation">
+ validation feature</link> will enable validation against a DTD only.
+To allow validation against XML Schemas you must turn on the <link
+idref='features' anchor="validation">validation feature</link> and the
+<link idref='features' anchor="validation.schema">schema feature</link>, and
+XML Schema Validator will be inserted in the pipeline.
+If you've created your own configuration which does not extend StandardParserConfiguration,
+you must make sure that your configuration inserts all needed validators in the pipeline.
</p>
</a>
</faq>
@@ -43,16 +49,21 @@
</li>
</ul>
<p>
- An application may choose to create the configuration that does not have DTD validator but has XML Schema validator. This will turn Xerces into non-compliant processor according to XML 1.0 and XML Schema specifications, thus the validation/augmentation outcome is undefined.
+ An application may choose to create a configuration that does not have ia DTD
+ validator but has an XML Schema validator. This will turn Xerces into a
+ non-compliant processor according to XML 1.0 and XML Schema specifications,
+ thus the validation/augmentation outcome is undefined.
</p>
</a>
</faq>
-<faq title='Validation against specific schema language'>
- <q>How can I tell the parser to validate against XML Schema and do not report DTD validation errors?</q>
+<faq title='Validation against a specific schema language'>
+ <q>How can I tell the parser to validate against XML Schema and not to report DTD validation errors?</q>
<a>
<p>
- Currently it is impossible. We hope that JAXP 1.2 will provide this capability via the schema language property. Otherwise, we might introduce Xerces language property that will allow specifying the language against which validation will occur.
+ Currently this is impossible. We hope that JAXP 1.2 will provide this capability
+ via iits schema language property. Otherwise, we might introduce a Xerces
+ language property that will allow specifying the language against which validation will dbimust occur.
</p>
</a>
</faq>
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-cvs-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-cvs-help@xml.apache.org