W3C home > Mailing lists > Public > xproc-dev@w3.org > July 2011

Attribute value templates on xproc elements

From: Geert Josten <geert.josten@daidalos.nl>
Date: Thu, 21 Jul 2011 13:48:13 +0200
To: "XProc Dev (xproc-dev@w3.org)" <xproc-dev@w3.org>
Message-ID: <B26C615F8546A84C81165A7BC8BE61A020F39D7F3C@EXMBXC01.ms-hosting.nl>
Hi all,

Has it been considered to allow attribute value templates within xproc elements? I noticed James Sulak has mentioned this a few times (http://markmail.org/message/izljaycmqd2vythh, and http://markmail.org/message/nswpbxjxk5cpw6zn), but couldn't find any answer. It can replace simple with-option and with-param elements, but it could give larger simplifications as well. Instead of doing:

    <p:declare-step type="ut:xslt" name="current">
		<p:input port="source" sequence="true" primary="true"/>
		<p:input port="parameters" kind="parameter"/>
		<p:output port="result" primary="true"/>
		<p:output port="secondary" sequence="true"/>
		<p:option name="href" required="true"/>
		<p:load name="load-file">
			<p:with-option name="href" select="$href"/>
			<p:input port="stylesheet">
				<p:pipe port="result" step="load-file"/>
			<p:input port="source">
				<p:pipe port="source" step="current"/>
			<p:input port="parameters">
				<p:pipe port="parameters" step="current"/>

Called with for instance:
			<p:with-option name="href" select="$href" />

Instead, ut:xslt would become unnecessary, and one would use:

			<p:input port="stylesheet">
				<p:document href="{$href}"/>

Kind regards,
Received on Thursday, 21 July 2011 11:48:38 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:03:08 UTC