W3C home > Mailing lists > Public > public-xml-processing-model-wg@w3.org > August 2008

Re: add p:encrypt and p:decrypt optional step

From: Norman Walsh <ndw@nwalsh.com>
Date: Fri, 22 Aug 2008 09:35:11 -0400
To: public-xml-processing-model-wg@w3.org
Message-ID: <m27ia9tbow.fsf@nwalsh.com>
"Innovimax SARL" <innovimax@gmail.com> writes:

> We could say that we have
>
> <p:declare-step type="p:encrypt">
>    <p:input port="source" primary="true"/>
>    <p:output port="result"/>
>    <p:input port="parameters" kind="parameter"/>
>    <p:option name="match" required="true"/> <!-- XSLTMatchPattern -->
>   <p:option name="granularity" required="true"/><!-- 'content' or 'element'
> -->
> </p:declare-step>
>
> match option would say which elements you want to encrypt and granularity
> option would say if you encrypt the matched element or its content

Is that all you need to do encryption? Everytime I've tried to
understand XMLDSig kits there's been all sorts of stuff about tokens
and certificates that I've never been able to get my head around.

> <p:declare-step type="p:decrypt">
>    <p:input port="source" primary="true"/>
>    <p:output port="result"/>
>    <p:input port="parameters" kind="parameter"/>
>    <p:option name="match" required="true"/> <!-- XSLTMatchPattern -->
> </p:declare-step>
>
> match would match perticular node
> {http://www.w3.org/2001/04/xmlenc#}EncryptedData (if we stick to XML
> Encryption spec, but we don't need to) and would decrypt them

Again, is there enough information here to do the job?

                                        Be seeing you,
                                          norm

-- 
Norman Walsh <ndw@nwalsh.com> | First time surrealists are often
http://nwalsh.com/            | confused by the similarities between
                              | fish and telephones.

Received on Friday, 22 August 2008 13:36:00 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 22 August 2008 13:36:02 GMT