Thanks Rich,
I have included an extract from the 0.3 ATOM draft below. You are right
Rich, they deal with this issue.
Excerpt from Section 3 "Common Atom Constructs" begins here ...
3.1.2 "mode" Attribute
Content constructs MAY have a "mode" attribute, whose value indicates the
method used to encode the content. When present, this attribute's value MUST
be listed below. If not present, its value MUST be considered to be "xml".
"xml":
A mode attribute with the value "xml" indicates that the element's
content is inline xml (for example, namespace-qualified XHTML).
"escaped":
A mode attribute with the value "escaped" indicates that the element's
content is an escaped string. Processors MUST unescape the element's content
before considering it as content of the indicated media type.
"base64":
A mode attribute with the value "base64" indicates that the element's
content is base64-encoded [RFC2045]. Processors MUST decode the element's
content before considering it as content of the the indicated media type.
... Excerpt ends here
This is very close to my earlier suggestion. There are further
restrictions/guidelines when using mode="xml" and they are also constrained
to xml 1.0
Comments ?
Ed
-----Original Message-----
From: Rich Salz [mailto:]
Sent: April 12, 2005 10:46 AM
To: Juan Carlos Cruellas
Cc: ; 'Konrad Lanz'; 'OASIS DSS TC'
Subject: Re: [dss] XMLData problem in Core "Opaqueness
> 1. We may add the "encoding" attribute to <dss:XMLData> for dealing
> with encoded XML... the escaped one is the obvious, can you think in
> others?
Someone could take a look at what the IETF "ATOM" working group does. They
had to handle this.
/r$
--
Rich Salz Chief Security Architect
DataPower Technology http://www.datapower.com
XS40 XML Security Gateway http://www.datapower.com/products/xs40.html
