RE: result-document() and XProc secondaries

Hi,

It depends where exactly you get err:XD0001, but if you stylesheet produces an empty primary result document, you may expect an eror in p:xslt. Normally this error should be err:XD0007 but perhaps this what goes wrong in your particular case. But I am just guessing here.

If the error is not in p:xslt, then I would just add <p:log port="secondary" href="...."/> to p:xslt to see what documents get created by the stylesheet. I believe that Calabash supports extension attributes/command-line options to allow for logging sequences of documents.

Regards,
Vojtech

________________________________________
Odesílatel: xproc-dev-request@w3.org [xproc-dev-request@w3.org] za uživatele David [david@davidpriest.ca]
Odesláno: 11. prosince 2010 2:00
Komu: xproc-dev@w3.org
Předmět: result-document() and XProc secondaries

Is there any reason to believe that the XProc below would error-out with
an XD0001 (non-XML resource)?  When the self-same XSLT transformation is
run through Saxon, it correctly produces the files through its
result-document() statements.

How can I discover exactly what is being received by the p:store
statement?  If I could only see the (presumably non-XML) data, I'd have
a much better clue as to what the problem is.

<?xml version="1.0"?>
<p:declare-step xmlns:p="http://www.w3.org/ns/xproc" version="1.0"
name="bootstrap">
<p:xslt name="extract_literate_programs" version="2.0">
<p:input port="source">
<p:document href="bootstrap_literate_xml.xml"/>
</p:input>
<p:input port="stylesheet">
<p:document href="bootstrap_tangle.xsl"/>
</p:input>
<p:input port="parameters">
<p:empty/>
</p:input>
</p:xslt>
<p:sink/>
<p:for-each>
<p:iteration-source>
<p:pipe step="extract_literate_programs" port="secondary"/>
</p:iteration-source>
<p:store>
<p:with-option name="href" select="concat('src-',p:iteration-position())"/>
</p:store>
<p:identity/>
</p:for-each>
</p:declare-step>

Received on Tuesday, 14 December 2010 09:34:49 UTC