[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: Re: Charset II - defn.
I prefer option 1 as well. No argument here;-) Chris ian.c.jones@bt.com wrote: > > All, > > I agree that the simplest way to "Fix" this is to mandate the XML > prologue for the message header document in section 3 of the specification. > > I have 2 possible views: > 1. In the prologue of the header the XML "encoding=" must be specified. > 2. In the prologue of the header the XML "encoding=" must be specified if > the encoding is NOT UTF-8. > > I prefer the 1st case but I know no matter what we say someone will > complain, from experience inserting the "encoding" even when not required by > the XML 1.0 spec. has stopped spurious errors when using some parsers. My > response is, "WE, are defining the ebXML header document and want maximum > interoperability with as little optionality as possible". So just like EDI > if we wanted to make an optional field mandatory for good business reason we > did! > > Comments? Arguments? Flames etc.?? > > Ian > > -----Original Message----- > From: Dick Brooks [mailto:dick@8760.com] > Sent: 31 August 2000 17:25 > To: Christopher Ferris > Cc: ian.c.jones; ebxml-transport > Subject: RE: Charset II - defn. > > Chris, > > I totally agree, if the encoding attribute is "REQUIRED" in the prolog of > the ebXML header document then Ian's text can remain unchanged! > > 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: Christopher Ferris [mailto:chris.ferris@east.sun.com] > > Sent: Thursday, August 31, 2000 11:16 AM > > To: Dick Brooks > > Cc: ian.c.jones@bt.com; ebxml-transport@lists.ebxml.org > > Subject: Re: Charset II - defn. > > > > > > Dick, > > > > The encoding attribute in the prolog is optional, but > > there is a default value as per your last email with the > > BOM, etc. > > > > Now, what we could do is have the encoding attribute > > required for ebXMLHeader document and that would end > > the discussion. > > > > Chris > > > > Dick Brooks wrote: > > > > > > 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 > > > > > > > > -- > > _/_/_/_/ _/ _/ _/ _/ Christopher Ferris - Enterprise Architect > > _/ _/ _/ _/_/ _/ Phone: 781-442-3063 or x23063 > > _/_/_/_/ _/ _/ _/ _/ _/ Email: chris.ferris@East.Sun.COM > > _/ _/ _/ _/ _/_/ Sun Microsystems, Mailstop: UBUR03-313 > > _/_/_/_/ _/_/_/ _/ _/ 1 Network Drive Burlington, MA 01803-0903 -- _/_/_/_/ _/ _/ _/ _/ Christopher Ferris - Enterprise Architect _/ _/ _/ _/_/ _/ Phone: 781-442-3063 or x23063 _/_/_/_/ _/ _/ _/ _/ _/ Email: chris.ferris@East.Sun.COM _/ _/ _/ _/ _/_/ Sun Microsystems, Mailstop: UBUR03-313 _/_/_/_/ _/_/_/ _/ _/ 1 Network Drive Burlington, MA 01803-0903
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC