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

Re: V.next: resource manager

From: Henry S. Thompson <ht@inf.ed.ac.uk>
Date: Thu, 05 Jan 2012 16:10:25 +0000
To: <vojtech.toman@emc.com>
Cc: <public-xml-processing-model-wg@w3.org>
Message-ID: <f5bmxa2ku4u.fsf@calexico.inf.ed.ac.uk>
So something such as this would be the kind of thing Alex and I were
proposing:

<p:delete match="a">
  <p:input port="source">
    <p:document href="http://example.com/doc.xml"/>
  </p:input>
</p:delete>
 
<p:stash name="{base-uri()}">

<p:uri-scope>
 <p:map-uri from="{base-uri()}" to="stash:{base-uri()}"/>

 <p:xinclude>
   <p:input port="source">
     <p:inline>
       <book>
         <!-- loads the document from the resource manager -->
         <xi:include href="http://example.com/doc.xml"/>
       </book>
     </p:inline>
   </p:input>
 </p:xinclude>

</p:uri-scope>

p:stash has a signature similar to p:store, but puts documents into
the local stash under the given name.  stash:... can be used within
pipelines to access documents stashed under the name ... .

This means that stash URIs look like e.g. stash:http://example.com/foo
or stash:file:///home/ht/tmp.html, which is a) bogus but b) simplifies
manipulation.

In other words, stash: URIs treat everything after the : as an opaque
string.

p:uri-scope is a new compound step, with content model something like

 ((map-uri|map-public|map-...)* subpipeline)

In haste,

ht
-- 
       Henry S. Thompson, School of Informatics, University of Edinburgh
      10 Crichton Street, Edinburgh EH8 9AB, SCOTLAND -- (44) 131 650-4440
                Fax: (44) 131 650-4587, e-mail: ht@inf.ed.ac.uk
                       URL: http://www.ltg.ed.ac.uk/~ht/
 [mail from me _always_ has a .sig like this -- mail without it is forged spam]
Received on Thursday, 5 January 2012 16:10:50 GMT

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