RE: Draft Minutes from 010611 Teleconf (changes)

Joseph,

The XPath expression in the example is a little strange.  If the "id"
attribute's value is of type ID, "3" cannot be specified.
And the filtering seems not to work as you expect, according to Section
6.6.3 of the XML Signature spec [1]:

"The transform output is also an XPath node-set. The XPath expression
appearing in the XPath parameter is evaluated once for each node in the
input node-set. The result is converted to a boolean. If the boolean is
true, then the node is included in the output node-set. If the boolean is
false, then the node is omitted from the output node-set."

[1] http://www.w3.org/TR/xmldsig-core/

Thanks,
Takeshi IMAMURA
Tokyo Research Laboratory
IBM Research
imamu@jp.ibm.com



From: "Joseph M. Reagle Jr." <reagle@w3.org>@w3.org on 2001/06/14 05:05 AM

Please respond to "Joseph M. Reagle Jr." <reagle@w3.org>

Sent by:  xml-encryption-request@w3.org


To:   "Blair Dillaway" <blaird@microsoft.com>
cc:   <edsimon@xmlsec.com>, <xml-encryption@w3.org>
Subject:  RE: Draft Minutes from 010611 Teleconf (changes)



At 14:43 6/13/2001, Blair Dillaway wrote:
>I assume you mean CipherValue.  If not, then my response may be off base.

Nope, you're on target, tweaked it back and improved the Xpath though I
haven't tested it yet.
                     //rep:CipherValue[@id='3']/text()

--
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/

Received on Friday, 15 June 2001 06:04:17 UTC