Hi Gerrard,
The reason this isn't working for you is that in Xerces, schema validation
is performed on the result infoset produced by the XInclude processor.
(XInclude does not specify a processing order, so this was an
implementation decision.) When the XPointer is processed it isn't known
th
It's also not represented [1] in the infoset.
[1] http://www.w3.org/TR/2004/REC-xml-infoset-20040204/#omitted
Joseph Kesselman <[EMAIL PROTECTED]> wrote on 07/13/2005 11:05:08 AM:
> The DOM spec says the Document node can't contain text elements, so
there's
> really no way to record this whites
The DOM spec says the Document node can't contain text elements, so there's
really no way to record this whitespace in a standard DOM Document.
__
Joe Kesselman, IBM Next-Generation Web Technologies: XML, XSL and more.
"The world changed profoundly and unpredict
Hi,
I recently discovered that when parsing an XML document using DOM with
"include-ignorable-whitespace" feature on (which is default), all white
space located outside the root element is still lost! For example, a
trailing new line character at the end of the document will be lost, as
well as li
Hi,
I am getting an "XPointer resolution unsuccessful" error when I have an
XInclude include element that has an xpointer attribute using the
XPointer element() Scheme and that begins with an NCName (i.e. a
shorthand pointer).
The include element I am using looks like:
The error message w