- From: Takeshi Imamura <IMAMU@jp.ibm.com>
- Date: Thu, 18 Jul 2002 16:09:38 +0900
- To: reagle@w3.org
- Cc: merlin <merlin@baltimore.ie>, xml-encryption@w3.org
>> This text is good to me, too. As for serialization, I don't think that >> we have to specify any serialization algorithm. This means that whatever >> algorithm an implementation assumes, it should be compliant with this >> section. > >Ok, [1] now includes the text. I'd still like to include some simple >rationale as to why this is done/necessary: "(e.g., serialization and >reparsing ensures all nodes correspond to the same document)". I'm not sure >if that's your rationale so I welcome suggestions. While how to replace a part of a node-set from a document with a node-set from another document is unclear from the definition of the node-set, how to replace a part of an octet stream with another octet stream is very clear. So the processing should be specified over octet streams, and then the processing "include Y in place of e and its descendants in X" is regarded as a shortcut of the original processing. This is my rationale. Thanks, Takeshi IMAMURA Tokyo Research Laboratory IBM Research imamu@jp.ibm.com
Received on Thursday, 18 July 2002 03:10:04 UTC