W3C home > Mailing lists > Public > public-xml-processing-model-wg@w3.org > January 2006

Re: Component interfaces

From: Jeni Tennison <jeni@jenitennison.com>
Date: Mon, 16 Jan 2006 17:03:15 +0000
Message-ID: <1796137002.20060116170315@jenitennison.com>
To: Erik Bruchez <ebruchez@orbeon.com>
CC: public-xml-processing-model-wg@w3.org

Hi Erik,

 >> (possibly document nodes containing only a text node child, though
 >> that might be bending it too much).
> Ouch. I don't think you will find that such a thing is allowed in any
> W3C spec.

I might be misunderstanding, but I think XDM allows precisely this.
See [1] which says:

  The children [of a document node] must consist exclusively of
  Element, Processing Instruction, Comment, and Text Nodes if it is
  not empty. Attribute, Namespace, and Document Nodes can never appear
  as children

XPath 2.0 allows this because XPath 1.0 allowed it. XPath 1.0 allowed
it to support the creation of parsed entities [2] (and, indeed,
non-XML text documents) using XSLT.

So to properly support XSLT and XQuery then it must be possible to
pass around document nodes that do not represent XML documents, such
as those that have a single text node as a child.


[1] http://www.w3.org/TR/xpath-datamodel/#DocumentNode
[2] http://www.w3.org/TR/xml11/#wf-entities

Jeni Tennison
Received on Monday, 16 January 2006 17:03:25 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:32:38 UTC