- From: Alex Milowski <alex@milowski.org>
- Date: Wed, 16 May 2007 13:16:54 -0700
- To: public-xml-processing-model-wg@w3.org
On 5/16/07, Norman Walsh <ndw@nwalsh.com> wrote:
> Consider this pipeline:
>
> <p:pipeline name="pipeline"
> xmlns:p="http://www.w3.org/2007/03/xproc"
> xmlns:nw="http://nwalsh.com/xproc/pipelines">
> <p:input port="source">
> <p:document href="xproc.xml"/>
> </p:input>
>
> <p:import href="library.xml"/>
>
> <nw:do-some-stuff/>
>
> <p:store name="store">
> <p:option name="href" value="???"/>
> </p:store>
>
> </p:pipeline>
>
> Suppose I want to set the href value on the store option to the base URI
> of the pipeline's source input with .xml changed to .html.
In XSLT we resolved document references relative to the stylesheet unless
a context node was given. We could do something like:
* The 'value' string is relative to the base URI of the p:option element.
* The 'select' expression can use the context node to resolve
a relative value. The value is then resolved against the base URI
of the p:option element.
Since we're using XPath 1.0, we'd have to provide XPath 2.0's
'resolve-uri' and 'base-uri' functions for authors to be able to set
URI values relative to input documents.
--
--Alex Milowski
"The excellence of grammar as a guide is proportional to the paucity of the
inflexions, i.e. to the degree of analysis effected by the language
considered."
Bertrand Russell in a footnote of Principles of Mathematics
Received on Wednesday, 16 May 2007 20:16:59 UTC