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

V.next: resource manager

From: Norman Walsh <ndw@nwalsh.com>
Date: Thu, 05 Jan 2012 09:15:58 -0500
To: public-xml-processing-model-wg@w3.org
Message-ID: <m2pqeyutep.fsf@nwalsh.com>
Here's a big one to chew on.

Suppose http://example.com/doc.xml contains:

  <doc>
    <a/>
    <b/>
    <c/>
  </doc>

And consider this pipeline fragment:

  <p:delete match="a">
    <p:input port="source">
      <p:document href="http://example.com/doc.xml"/>
    </p:input>
  </p:delete>

  <p:sink/>

  <p:xinclude>
    <p:input port="source">
      <p:inline>
        <book>
          <xi:include href="http://example.com/doc.xml"/>
        </book>
      </p:inline>
    </p:input>
  </p:xinclude>

Assume for the moment that the p:delete step runs to completion before
the p:xinclude step starts.

Which document does the p:xinclude step produce?

  <book>
  <doc>
    <a/>
    <b/>
    <c/>
  </doc>
  </book>

or

  <book>
  <doc>
    <b/>
    <c/>
  </doc>
  </book>

I think the latter is the more useful, if perhaps more surprising, result.

Discuss. :-)

                                        Be seeing you,
                                          norm

-- 
Norman Walsh
Lead Engineer
MarkLogic Corporation
Phone: +1 413 624 6676
www.marklogic.com

Received on Thursday, 5 January 2012 14:16:38 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 5 January 2012 14:16:38 GMT