mrglavas 2003/11/14 11:45:19
Modified: java/docs faq-pcfp.xml
Log:
Fix reference to the default configuration and
improve FAQ on the validation behaviour of
the default configuration.
Revision Changes Path
1.7 +14 -10 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.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- faq-pcfp.xml 24 Mar 2003 22:44:32 -0000 1.6
+++ faq-pcfp.xml 14 Nov 2003 19:45:19 -0000 1.7
@@ -7,7 +7,10 @@
<p>
If a validator is included in the pipeline, the assessment is
done, whether the validation feature is set to true or false.
- The validation feature only enables the validation constraint error reporting
and it does not control the infoset augmentation: if a validator is included in the
pipeline the parser will augment the infoset according to the grammar specified for
the instance document.
+ The validation feature only enables the validation constraint error
+ reporting and it does not control the infoset augmentation: if a
+ validator is included in the pipeline the parser will augment the
+ infoset according to the grammar specified for the instance document.
</p>
</a>
</faq>
@@ -16,15 +19,16 @@
<q>What validation behavior do I expect from the default parser configuration?</q>
<a>
<p>
- 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.
+ The default configuration (&DefaultConfigLong;) includes the DTD validator
+ and the document scanner (which are both capable of namespace binding). 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 &DefaultConfig; (or another
+ suitable configuration included with the parser), you must make sure that your
+ configuration inserts all needed validators in the pipeline.
</p>
</a>
</faq>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
