RE: Messaging Service spec v0-2 - charsets

["Brunner, Eric" <EBrunner@Engage.com>]

I must have missed something. I'd like to see the rational for declining to
label the encoding.

Two parties using SJIS (or Big5 or GB or ...) MAY convay this encoding to
each other how?

Two parties using SJIS (or ...) MUST convert their data to utf8 (or
iso8859-*) because why?

Cheers,
Eric

-----Original Message-----
From: Christopher Ferris [mailto:chris.ferris@east.sun.com]
Sent: Tuesday, September 19, 2000 10:06 AM
To: tmcgrath@tedis.com.au
Cc: duane; ebXML-Transport@lists.ebxml.org; Jon Bosak;
joebaran@extol.com; ebxml-coord@lists.ebxml.org
Subject: Re: Messaging Service spec v0-2 - charsets


The spec wording of the charset has been revised in version
0.21 which is what we plan to publish. That version contains
some edits which were omitted (due to time and other constraints)
from version 0.2 which you reviewed. 

UTF-8 is RECOMMENDED, but not mandated. I don't believe that 
we can mandate its use. Fujitsu might have some comment on
this based upon their experience. Bottom line, the charset
used should be pre-agreed (and hence, in the TPA or equivalent)
by both parties.

Cheers,

Chris

Tim McGrath wrote:
> 
> as we have concluded our report and suggested the spec now go to public
> review, this thread should now be addressed directly to the TRP team.
> 
> i shall forward it to their list.
> 
> duane wrote:
> 
> > Jon:
> >
> > Yes - you are right.  UTF-8 has been mandated by the Technical
> > Architecture group as minimal.
> >
> > ISO 8859-1 does not represent Kanji characters correctly as far as I
> > know.
> >
> > Duane Nickull
> >
> > Jon Bosak wrote:
> > >
> > > [tmcgrath@tedis.com.au:]
> > >
> > > | * lines 211-215 and then 261-268  (charsets)
> > > |
> > > | Both claim to be "The charset attribute is used to identify the
> > > | character set used to create the message" and yet propose
> > > | different values.  i think it means the outer and inner encoding
> > > | methods but if so it should not use the same first sentence.
> > >
> > > The encoding method could use the iso-8859-1 default value of lines
> > > 213-215 or UTF-8 as recommended in 264-266.  It seems to me that
> > > we should mandate the latter.  Surely UTF-8 is the minimum level
> > > of internationalization for anything calling itself an XML tool.
> > >
> > > Jon
> 
> --
> regards
> tim mcgrath
> TEDIS   fremantle  western australia 6160
> phone: +618 93352228  fax: +618 93352142

-- 
    _/_/_/_/ _/    _/ _/    _/ 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