W3C home > Mailing lists > Public > xml-encryption@w3.org > August 2000

Encrypted Node URI and NodeType

From: Joseph M. Reagle Jr. <reagle@w3.org>
Date: Wed, 30 Aug 2000 13:25:59 -0400
Message-Id: <>
To: Ed Simon <ed.simon@entrust.com>
Cc: "Public XML Encryption List" <xml-encryption@w3.org>, swick@w3.org, Dan Connolly <connolly@w3.org>

As stated after the Crypto BoF, in your proposal [1] I recommend you break
up your NodeType into a location (location of the EncryptedNode's encrypted
serialization -- if not present in the element content) and NodeType (the
URIs of the Information Set item provided by [2]). Instead of

<EncryptedNode xmlns="http://www.w3.org/2001/03/Encryption"
    NodeType="."  <!-- "." indicates the <EncryptedNode> element is right
                         where the original unencrypted element was -->
    (Base64 of encrypted Element node)


<EncryptedNode xmlns="http://www.w3.org/2001/03/Encryption"
    (Base64 of encrypted Element node)

Futhermore, if Location is intended to be a URI the "." hack/syntax for the
present node will probably be problematic. I'm presently scratching my head
about the best structure/relation of these things to each other (describing
Information Set Items/Nodes in the context of a serialized Information Set
Items/Nodes where both instances have a relationship to each other...)
Hopefully I'll post more within the week.

[2] http://www.w3.org/TR/2000/WD-xml-infoset-20000726

Joseph Reagle Jr.   
W3C Policy Analyst                mailto:reagle@w3.org
IETF/W3C XML-Signature Co-Chair   http://www.w3.org/People/Reagle/
Received on Wednesday, 30 August 2000 13:26:05 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 23:12:58 UTC