Under certain circumstances, a user may wish to validate a tree while ignoring
the content of certain elements, designated by name. This is not dissimilar
from the need to validate an arbitrarily-named element when a type is known for
it, though it's a different use case.
The original driving use case: XML-binary Optimized packaging replaces this:
<base64Element>KJJjasdfweLFDKJsvas==</base64Element>
with this:
<base64Element xmime:contentType="application/octet-stream"
xmlns:xmime="XMIME_NS">
<xop:Include xmlns:xop="XOP_NS" href="cid:id@id.issuer" />
<base64Element>
The goal is to be able to designate elements which will be accepted as valid,
but treated as processContents=skip (and wildcard attribute pc=skip, too).
This is considered reasonable; the goal of strict validation is subverted, but
that's because somebody went to the trouble of doing it.
Original issue reported on code.google.com by aale...@gmail.com on 21 Aug 2013 at 7:35
Original issue reported on code.google.com by
aale...@gmail.com
on 21 Aug 2013 at 7:35