Re: Possible new XProc 1.1 step: p:template

"Henry S. Thompson" <ht@inf.ed.ac.uk> writes:
>  <p:transform match="/*">
>   <p:input port="template">
>    <p:inline>
>     <c:request method="GET" href="{@uri}">
>      <c:header name="Accept" value="application/rdf+xml"/>
>     </c:request>
>    </p:inline>
>   </p:input>
>  <p:transform>
>
> That would do for expermentation purposes.

Except that the spec says of p:inline:

   Inline documents are considered “quoted”. The pipeline processor
   passes them literally to the port, even if they contain elements
   from the XProc namespace or other namespaces that would have other
   semantics outside of the p:inline.

Hence my suggestion with the ugly name p:interpolated-inline.

> I should have made clear that I assume that the context node for
> evaluation of XPath expressions within curly braces is the node
> matched by the 'match' option.
>
> A further step at the level of the whole language would be to
> interpret
>
>   <[step name] . . .>
>    <[some elt] . . .>
>     . . .
>    </[some elt]>
>   </[step name]>
>
> as shorthand for
>
>   <[step name] . . .>
>    <p:input port="[primary port name]">
>     <p:inline>
>      <[some elt] . . .>
>       . . .
>      </[some elt]>
>     </p:inline>
>    </p:input>
>   </[step name]>

We could, though that seems to invite all sorts of confusion.

                                        Be seeing you,
                                          norm

-- 
Norman Walsh <ndw@nwalsh.com> | It is not failure of others to
http://nwalsh.com/            | appreciate your abilities that should
                              | trouble you, but rather your failure to
                              | appreciate theirs.-- Confucius