[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: RE: Charset II - defn.
Ian, The encoding attribute of the XML prolog is "optional", are we going to REQUIRE this within the ebXML header document? If not then we should reword to: "SHALL be equivalent to the encoding attribute, when present, in the ebXML message Header XML Document" Dick Brooks Group 8760 110 12th Street North Birmingham, AL 35203 dick@8760.com 205-250-8053 Fax: 205-250-8057 http://www.8760.com/ InsideAgent - Empowering e-commerce solutions > -----Original Message----- > From: ian.c.jones@bt.com [mailto:ian.c.jones@bt.com] > Sent: Thursday, August 31, 2000 10:20 AM > To: ebxml-transport@lists.ebxml.org > Subject: Charset II - defn. > > > List-Unsubscribe: > <mailto:ebxml-transport-request@lists.ebxml.org?body=unsubscribe> > List-Archive: <http://lists.ebxml.org/archives/ebxml-transport> > List-Help: <http://lists.ebxml.org/doc/email-manage.html>, > <mailto:ebxml-transport-request@lists.ebxml.org?body=help> > > All, > > after discussion today lets try this: > > The charset attribute SHALL be equivalent to the encoding attribute of the > ebXML message Header XML Document (described in section 3). For maximum > interoperability it is RECOMMENDED that UTF-8 be used. Note: this is not > the default for MIME > > Ian Jones >
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC