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

RE: Encrypted external non-XML data

From: Ed Simon <ed.simon@entrust.com>
Date: Thu, 31 Aug 2000 11:31:09 -0400
Message-ID: <3120721CA75DD411B8340090273D20B10C1B8C@sottmxs06.entrust.com>
To: "'merlin'" <merlin@baltimore.ie>
Cc: Public XML Encryption List <xml-encryption@w3.org>
Agreed.  The strawman proposal already covers encrypting
arbitrary objects.  After the Santa Barbara meeting, Joseph
and I discussed how to do what is suggested in your note.

Basically NodeType will be split into Type and Location and
EncryptedNode will be renamed EncryptedData so one would have
something like what you have in your message but with the
addition of a Type attribute and using the term "URI" rather
than "Location":

<EncryptedData xmlns="&xmlenc;"
  EncryptionInfo="#encryptionInfo23" />

Regards, Ed

-----Original Message-----
From: merlin [mailto:merlin@baltimore.ie]
Sent: Thursday, August 31, 2000 10:15 AM
To: Ed Simon
Cc: Public XML Encryption List
Subject: Encrypted external non-XML data


Something that I would be interested in is the ability to
provide encryption information about an external non-XML

<EncryptedData xmlns="&xmlenc;"
  EncryptionInfo="#encryptionInfo23" />

The rationale is that XML is being used in some situations
to encode control information describing accompanying non
XML data.

Support in this document would allow the control data to
express encryption information in a standard manner, and
the keying information could also be shared with encrypted
nodes within the control document.

Embedding external data within base 64 nodes is not always
practical or efficient.

Received on Thursday, 31 August 2000 11:36:24 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:31:58 UTC