OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

dss message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: RE: [dss] base64


At 04:57 PM 10/7/2003 -0400, Rich Salz wrote:

> > Rich, your schema mentions transferring XML both in the clear and
> > base64-encoded, and says something about "encoding" - are there character
> > encoding issues that would necessitate base64'd XML, where the
> > InputDocument might be in a different encoding than the protocol message?
>
>Exactly.  An application might be using a codeset optimized for its
>locale, but the DSS might be in all UTF-8, for example.
>         /r$

So we need at least the option of base64'ing an XML input document.

Which of these choices do you (or anyone else) prefer, for a <Document>'s 
contents:

1) XML can be plain or base64; everything else is base64 -
     <XMLData>
     <Base64XMLData>
     <Base64BinaryData> (with a MimeType attribute)

2) The way Rich's schema initially had it - like above, but also with the 
option for for un-encoded non-XML text:
     <XMLData>
     <Base64XMLData>
     <Base64BinaryData> (with a MimeType attribute)
     <TextData> (" " ")

3) The way it currently is: everything is base64'd
     <Data> (with a MimeType attribute)


Trevor 



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]