W3C home > Mailing lists > Public > xproc-dev@w3.org > September 2010

Re: Newbie: config file import, and http-request

From: docs <docs@davidpriest.ca>
Date: Tue, 21 Sep 2010 07:37:57 -0700
Message-Id: <D2EDD08C-0523-42F9-9D9D-DD74AEEB1230@davidpriest.ca>
Cc: David Priest <david@davidpriest.ca>, "xproc-dev@w3.org" <xproc-dev@w3.org>
To: Florent Georges <fgeorges@fgeorges.org>
Aha!  Now I'm beginning to see how to compose a complex step!  Very helpful. 

The biggest gap in XProc at the moment are patterns and prototypes from which to learn. The W3 spec is great for detail, but thin on putting the parts into play. 

-- 
davidpriest.ca
XML/XSLT Workflows
& Documentation

On 2010-09-21, at 3:30 AM, Florent Georges <fgeorges@fgeorges.org> wrote:

> On 20 September 2010 23:05, David Priest wrote:
> 
>  Hi,
> 
>> I'm beginning to experiment with replacing Ant with XProc.  One
>> of my key items involves accessing an HTTPS server.  Of course,
>> I don't want my credential details getting into the repository,
>> so I would like to have a config file that provides username
>> and password.
> 
>  You can use p:add-attribute:
> 
> <p:declare-step xmlns:c="http://www.w3.org/ns/xproc-step"
>                xmlns:p="http://www.w3.org/ns/xproc"
>                name="mir.fetch"
>                version="1.0">
> 
>   <p:input port="source">
>      <p:inline>
>         <c:request method="get" detailed="true" auth-method="basic"/>
>      </p:inline>
>   </p:input>
>   <p:output port="result"/>
> 
>   <p:parameters name="params">
>      <p:input port="parameters">
>         <p:document href="dpriest.xml"/>
>      </p:input>
>   </p:parameters>
> 
>   <p:add-attribute match="/c:request" attribute-name="username">
>      <p:input port="source">
>         <p:pipe port="source" step="mir.fetch"/>
>      </p:input>
>      <p:with-option name="attribute-value" select="
>          /c:param-set/c:param[@name eq 'username']/@value">
>         <p:pipe port="result" step="params"/>
>      </p:with-option>
>   </p:add-attribute>
> 
>   <p:add-attribute match="/c:request" attribute-name="password">
>      <p:with-option name="attribute-value" select="
>          /c:param-set/c:param[@name eq 'password']/@value">
>         <p:pipe port="result" step="params"/>
>      </p:with-option>
>   </p:add-attribute>
> 
>   <p:add-attribute match="/c:request" attribute-name="href">
>      <p:with-option name="attribute-value" select="
>          concat(/c:param-set/c:param[@name eq 'uri']/@value, 'version.xml')">
>         <p:pipe port="result" step="params"/>
>      </p:with-option>
>   </p:add-attribute>
> 
>   <!-- commented out to see the c:request element instead -->
>   <!--p:http-request/-->
> 
> </p:declare-step>
> 
>  I used to use options for that exact same purpose[1], but using
> a file can be interesting in some cases.
> 
>  Regards,
> 
> -- 
> Florent Georges
> http://fgeorges.org/
> 
> [1]http://code.google.com/p/expath/source/browse/trunk/website/tools/upload.xproc
> 
Received on Tuesday, 21 September 2010 21:19:01 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 21 September 2010 21:19:01 GMT