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

Re: URIs for media-types

From: Joseph Reagle <reagle@w3.org>
Date: Wed, 30 Jan 2002 15:32:00 -0500
Message-Id: <200201302032.PAA25248@tux.w3.org>
To: "Takeshi Imamura" <IMAMU@jp.ibm.com>
Cc: xml-encryption@w3.org
On Thursday 24 January 2002 03:11, Takeshi Imamura wrote:
> >A. We can have a MimeType and Encoding attribute, just like xmldsig.
> >B. We can have a MimeType attribute only and any parameters (including
> >charset and others) are encoded within that string. For example,
> ><... MimeType="text/html;charset=ISO-8859-1&level=2">
> I think both are OK, but if forced to compare them, I prefer A.

Ok, this is now reflected in [1]. It's presently part of EncryptedType, any 
reason we should limit this to EncryptedData?


[1] http://www.w3.org/Encryption/2001/Drafts/xmlenc-core/
$Revision: 1.123 $ on $Date: 2002/01/30 20:30:05 $ GMT by $Author: reagle $

MimeType is an optional (advisory) attribute which describes the media type 
of the data which has been encrypted. The value of this attribute is a 
string with values defined by [MIME]. For example, if the data that is 
encrypted is a base64 encoded PNG, the Encoding may be specified as 
'base64' and the MimeType as 'image/png'. This attribute is purely 
advisory; no validation of the MimeType information is required by this 
specification. Note, this information may not be necessary if it is already 
bound to the identifier in the Type attribute. For example, the Element and 
Content types defined in this specification are always UTF-8 encoded 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 Wednesday, 30 January 2002 15:32:12 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 27 October 2009 08:42:20 GMT