>> Summary: >> -------- >> The new schema language property should define the value of "ANY" to >> allow validation based on the grammar found in document instance. >> Otherwise, the property may be set to the namespace of a schema against >> which validation must occur (reporting validation errors, and infoset >> augmentation if any). For both cases the validation must be set to true >> (otherwise no errors will be reported). > >Sounds good to me. > >The schemaLanguage property will be disabled if setValidating(false) is >called. Right?
If setValidating maps onto the SAX validation feature, then the two are orthogonal. A conformant validating XML processor must report validity constraint failures against a DTD grammar, at user option. The validation feature is that option. There is no reason that a conformant validating XML processor, told not to report validity constraint failures, could not be used as the XML processor that produces the document infoset that an XML Schema processor then operates upon. In fact, I would still argue that a validating XML processor that does not report validity constraint failures against a DTD grammar when validation is true is non-conformant. - http://xml.org/sax/features/validation If true, validation is performed following the rules defined in Section 5.1 of the XML 1.0 spec for DTD validation. ALWAYS !! - http://apache.org/xml/features/validation/schema If true, validation is performed following the rules defined in the XML Schema specification. These two features are independent and I do not understand how they can be both set to true and claim that the behavior conforms to both specifications. Regards, Glenn --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
