Therefore XSLT processors do not rely on validating parsers.
XSLT uses a parser internally, but does not require a schema or DTD.
The interesting question here, is what happens to entities (those things defined with & or %) in a validating vs. But you can read the W3C recommendation if you are interested.
It's time to have a look at the validating parser and find out what happens when you use it to parse the sample presentation. The reference implementation supports any combination of configuration options.
(If a combination is not supported by any particular implementation, it is required to generate a factory configuration error.)Although a full treatment of XML Schema is beyond the scope of this tutorial, this section will show you the steps you need to take to validate an XML document using an existing schema written in the XML Schema language.
(You can also examine the sample programs that are part of the JAXP download.
A validating parser, validates XML against a schema or DTD.
An XML parser is anything that reads in XML, and provides your application with the nodes and attributes (OK, and PI's etc.) W3C has recommendations for validating and non-validating parsers and what they should return to the application.
On the other hand if either the XML or XSL document refers to an external entity, you had better hope that the XSLT processor dereferences it properly (something that a validating parser is required to do, but non-validating parsers may do but are not required to do, confusing isn't it?
) Most validating parsers can have their validations turned off programatically.
What is the difference between validation and parsing?
I know parsing check file structure (grammar), so may be checked as OK in parsing function, but may be WRONG in validation process because there is no attr value like "pink"? Parsing checks that the input conforms to the rules in the XML specification, for example that every start tag has a matching end tag.