W3C home > Mailing lists > Public > xml-encryption@w3.org > June 2002

Re: XML decryption transform number 13

From: merlin <merlin@baltimore.ie>
Date: Wed, 12 Jun 2002 18:28:17 +0100
To: "Takeshi Imamura" <IMAMU@jp.ibm.com>
Cc: reagle@w3.org, xml-encryption@w3.org
Message-Id: <20020612172817.E824F44315@yog-sothoth.ie.baltimore.com>

r/IMAMU@jp.ibm.com/2002.06.13/00:24:05
>
>
>>         2. Copy Y in place of e in Z.
>
>According to XPath's data model, this is not possible because Y and Z are
>yielded from different documents.  Merlin's technique, i.e., serializing Y
>and Z and parsing the resultant octet stream, would be needed.

Hi Takeshi,

I respectfully disagree with you here, although if you can
refer me to where the XPath document states that this is not
possible, I'll willingly relent.

Joseph's text implies that you take the document structure and
a node set over it and copy these nodes into another document,
duplicating the structure where possible. I don't see anything
that precludes this; how it is done is left, as it should be,
to the implementor.

Are you suggesting that decrypt-and-replace is not possible? If
so, why are you not asking that the entire concept be removed
from the specification?

By explicitly leaving this non-normative text vague, as Joseph
does, any given implementation can do what it needs to do. If
it cannot perform this operation, then it does not support
the decrypt-and-replace mode.

What you suggest; i.e., serialize and parse; does not
correspond to decrypt-and-replace, it corresponds to the
creation of a new document. That's not what we are trying to
specify; we're trying to specify, as abstractly as possible,
how to replace nodes in the original document with a decrypted
node set, without actually mandating any given implementation.

Merlin
Received on Wednesday, 12 June 2002 13:29:00 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:32:03 UTC