norman.walsh.name: Comments on /2009/03/26/xprocWithXProc http://norman.walsh.name/2009/03/26/xprocWithXProc/comments.atom 2009-03-27T11:48:54Z Comment 1 on /2009/03/26/xprocWithXProc http://norman.walsh.name/2009/03/26/xprocWithXProc#comment0001 2009-03-27T07:36:38Z 2009-03-27T07:36:38Z Vojtech Toman 1b7c6d2b6749e0e1d8431e48fd28019f44dde89f http://vtoman.wordpress.com
Thanks for putting your XML Prague presentation in one blog entry. (Is this the longest entry on your blog so far? :) I have one question about your use of p:pipeinfo in the pipeline, and especially the use of xml:id: 
<p:pipeinfo xml:id="steps-depends">
  <cx:depends>
    <cx:target>steps.rnc</cx:target>
    <cx:source>../typed-pipeline-library.xml</cx:source>
    <cx:source>../../style/library-to-rnc.xsl</cx:source>
  </cx:depends>
</p:pipeinfo>
You refer to the p:pipeinfo elements *of the pipeline itself* like this: 
<cx:out-of-date>
  <p:input port="source" select="id('steps-depends')/cx:depends">
    <p:document href="#"/>
  </p:input>
</cx:out-of-date>
Is this really possible? I mean, can an XProc pipeline access its source? I understand that href="#" resolves to the owner document, but this is the first time I see this in the XProc context.
 Comment 2 on /2009/03/26/xprocWithXProc http://norman.walsh.name/2009/03/26/xprocWithXProc#comment0002 2009-03-27T11:48:55Z 2009-03-27T11:48:55Z Norman Walsh 9f5c771a25733700b2f96af4f8e6f35c9b0ad327 http://norman.walsh.name/

Yeah, it is sort of absurdly long. Alternatively, I could have tried to cut the pipelines into snippets and highlight only the changed parts and lots of other things. In that alternate world, I fear the post wouldn't have been made for days, so I decided this was better. :-)

With regard to <p:document href=""> (the # is irrelevant I think), yes I think that should work. It's known to work in XSLT stylesheets, for example.

I was a little surprised, to be honest, when I tried it and it just worked. I think you might find the same thing is true in your implementation. If the href is relative, it has to be resolved against the base URI of the document element. In a pipeline, that's the base URI of the pipeline document, unless someone has used xml:base. If you resolve "" against the current base URI to get an absolute URI, the right thing just happens.

I believe it should work even if xml:base has been used, that is, same document references are immutable with respect to the base URI, but I bet that doesn't (yet) work in my implementation. I haven't tried though.