[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] Re: xml over http - RFC 3023
> > The problematic thing is that RFC3023 and RFC2616 specify defaults in > case it's missing, and these defaults are even conflicting. In my understanding, IESG approved the default in RFC 2616 only because 8859-1 was so common on the Web at that time. IESG instructed the authors of RFC 2376 (the predecessor of RFC 3023) to use US-ASCII as the default even when the MIME entity is transmitted via HTTP. Since XML was new, IESG did not want to use 8859-1. > For RFC2616bis, the plan is not to specify a default anymore (again: > <http://trac.tools.ietf.org/wg/httpbis/trac/ticket/20>). If this happens, we should revise RFC 3023 about charset defaulting in the case of text/xml over HTTP. Everything about encoding of text/xml is inherited from MIME and HTTP. Cheers, -- MURATA Makoto (FAMILY Given) <EB2M-MRT@a...>
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] |
PURCHASE STYLUS STUDIO ONLINE TODAY!Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced! Download The World's Best XML IDE!Accelerate XML development with our award-winning XML IDE - Download a free trial today! Subscribe in XML format
|