W3C home > Mailing lists > Public > w3c-ietf-xmldsig@w3.org > January to March 2002

Re: New XPath Filter Transform

From: merlin <merlin@baltimore.ie>
Date: Fri, 08 Mar 2002 18:26:43 +0000
To: reagle@w3.org
Cc: TAMURA Kent <kent@trl.ibm.co.jp>, w3c-ietf-xmldsig@w3.org, jboyer@pureedge.com
Message-Id: <20020308182643.519CF4422C@yog-sothoth.ie.baltimore.com>

The schema and DTD probably need a slight tweak:


  <complexType name="XPathType" content='textOnly'>

Something like that, anyway.


>I'll defer your question to John but apoligize that I didn't publish the 
>editorially tweaked version (with some renaming, schema, and namespace). 
>The latest version is at:
>  http://www.w3.org/Signature/Drafts/xmldsig-xpath/
>On Thursday 07 March 2002 00:29, TAMURA Kent wrote:
>> In message "New XPath Filter Transform"
>>     on 02/02/07, Joseph Reagle <reagle@w3.org> writes:
>> > Thoughts? (On these syntax issues, or implementation performance)
>> >
>> > [1] http://www.w3.org/Signature/Drafts/xmldsig-transform-xpath.html
>> Does this transform ignore the input nodeset except the root
>> node?  Does a resultant nodeset contain a node which is not
>> contained in the input nodeset but it is selected by
>> SignatureFilter XPath expression?
>Joseph Reagle Jr.                 http://www.w3.org/People/Reagle/
>W3C Policy Analyst                mailto:reagle@w3.org
>IETF/W3C XML-Signature Co-Chair   http://www.w3.org/Signature/
>W3C XML Encryption Chair          http://www.w3.org/Encryption/2001/

Baltimore Technologies plc will not be liable for direct,  special,  indirect 
or consequential  damages  arising  from  alteration of  the contents of this
message by a third party or as a result of any virus being passed on.

This footnote confirms that this email message has been swept by
Baltimore MIMEsweeper for Content Security threats, including
computer viruses.
Received on Friday, 8 March 2002 13:26:50 UTC

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