[
Lists Home |
Date Index |
Thread Index
]
- To: Alessandro Triglia <sandro@oss.com>
- Subject: Re: [xml-dev] Re: Binary Encoding using Base64
- From: Rich Salz <rsalz@datapower.com>
- Date: Mon, 27 Jan 2003 15:48:42 -0500
- Cc: 'Bill de hÓra' <bill@dehora.net>, xml-dev@lists.xml.org
- In-reply-to: <002701c2c643$6b29b880$7d01a8c0@Aldebaran>
- References: <002701c2c643$6b29b880$7d01a8c0@Aldebaran>
- User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20021130
Alessandro Triglia wrote:
I misled Bill; my quote is from page 26 not page 23. Section 6.8 of RFC
2045 says
>>> The encoded output stream must be represented in lines of no more
>>> than 76 characters each. All line breaks or other characters not
>>> found in Table 1 must be ignored by decoding software.
> By the way, am I right that there is no canonical representation defined
> for base64binary in XML Schema?
No. If you look at http://www.w3.org/TR/xmlschema-2/#base64Binary you
will see that it says:
For base64Binary data the entire binary stream is encoded using
the Base64 Content-Transfer-Encoding defined in Section 6.8 of
[RFC 2045].
The relevant part is triply-quoted above. :)
/r$
PS: Apologies to Simon; my "please turn the page" was snide, rather
than funny (which was the intention), compounded by being wrong as I
described above.
|
