Fwd: Re: Please VOTE ON ebxml Messaging Services spec v 0.2 forrelease to ebXML-Wide Group Review

[Jim Hughes <jfh@fs.fujitsu.com>]

Dick,

Do you agree with this position, that the first charset in 2.2.1.4 should 
be removed? Did we miss this point in the discussion last week?

>----
>In the specification, there are two charset attributes: in ebXML Message
>Envelop's Content-Type and ebXML Header Container's Content-Type. In
>addition, both charset attribute identify character set of same whole "the
>message" as following:
>
>     2.2 ebXML Message Envelope
>     ...
>     2.2.1.4 charset Attribute
>     The charset attribute is used to identify the character set used to
>     create the message. The list of valid values can be found at
>     http://www.iana.org/. The default charset value is "iso-8859-1". For
>     example:
>         charset="iso-8859-1"
>     ...
>     2.3 ebXML Header Container
>     ...
>     2.3.3.2 charset Attribute
>     The charset attribute identifies the character set used to create
>     the message. The list of valid values can be found at
>     http://www.iana.org/. The charset attribute SHALL be equivalent to
>     the encoding attribute of the ebXML Header Document (see section 3).
>     For maximum interoperability it is RECOMMENDED that [UTF-8] be used.
>     Note: this is not the default for MIME. For example:
>         charset="UTF-8"
>
>I believe that first charset attribute (section 2.2.1.4) should be
>deleted, because:
>     - It is an attribute for Content-Type "multipart/related". But in
>       the Content-Type, charset is not defined as an acceptable
>       attribute (by RFC 2387 "The MIME Multipart/Related Content-type").
>     - In multipart format of MIME, usually each part has charset
>       attribute individually. Top header has not charset attribute.
>     - It causes confusion when different character sets are identified by
>       the two charset attribute

Thanks,

Jim