OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

uddi-spec message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]


Subject: [uddi-spec] Second version: Proposed changes to UDDI Version 2specifications related to UTF-8 / UTF-16 issue


All,

After getting some feedback, I have drafted a second version of the specification changes that would be necessary to adopt the UTF-16 character encoding. Also, I misinterpreted the WS-I Basic Profile in that it does NOT mandate that a response message has to be encoded in the same character encoding
as the corresponding request message. In a conference call today, the WS-I Basic Profile Working Group also decided that this is not an issue, that is, response messages can also be encoded either in UTF-8 or UTF-16 and there is no need to match the character encoding of the request message.

Please see the revised proposal below.

First, the Programmers API Specification has to be changed as follows:

Section 3.1.7 "XML Encoding"
Replace
"Similarly, XML allows for a large number of character set encoding choices.  UDDI Operators are required to only support a single XML encoding - UTF-8, and will support all compatibility characters defined for UTF-8.  See appendix B for more information related to the use of byte order marks and
UTF-8 and the way the UDDI SOAP implementations convert all requests to Unicode prior to processing."
with
"Similarly, XML allows for a large number of character set encoding choices. UDDI Operators are required to support both UTF-8 and UTF-16, and will support all compatibility characters defined for these character encodings. See appendix B for more information related to the use of byte order marks
in Unicode and the way the UDDI SOAP implementations convert all requests to Unicode prior to processing."

Section 6.7 "Support for Unicode: SOAP listener behavior"
Remove
"The decision to use the UTF-8 encoding in all requests simplified the number of encoding variations that need to be handled within the XML interchanges used in this API specification."
Remove
"All such responses will be encoded in UTF-8."

Section 7.2 "XML Encoding requirements"
Replace
"All messages sent to and received from the Operator Site shall be encoded as UTF-8, and shall specify the HTTP Content-Type header with a charset parameter of "utf-8". All such messages shall also have the 'encoding="UTF-8"' markup in the XML-DECL that appears on the initial line.  Other encoding
name variants, such as UTF8, UTF_8, etc. shall not be used.  Therefore, to be explicit, the initial line shall be:
		     <?xml version="1.0" encoding="UTF-8" ?>
		and the Content-Type header shall be:
				Content-type: text/xml; charset="utf-8"
Operator sites MUST reject messages that do not conform to this requirement."
with
"All messages sent to the Operator Site shall be encoded either as UTF-8 or as UTF-16, and shall specify the HTTP Content-Type header with a corresponding charset parameter of "utf-8" or "utf-16". All such messages shall also have a corresponding 'encoding="UTF-8"' or 'encoding="UTF-16"' markup in
the XML-DECL that appears on the initial line.  Other encoding name variants, such as UTF8, UTF_8, UTF16 etc. shall not be used. Therefore, when using UTF-8, the initial line shall be:
		     <?xml version="1.0" encoding="UTF-8" ?>
		and the Content-Type header shall be:
				Content-type: text/xml; charset="utf-8"
When using UTF-16, the initial line shall be:
		     <?xml version="1.0" encoding="UTF-16" ?>
		and the Content-Type header shall be:
				Content-type: text/xml; charset="utf-16"
Operator sites MUST reject messages that do not conform to these requirements.
The character encoding of a response message that is received from an Operator Site conform to the same requirements. It is up to the Operator Site on which character encoding to use in response messages."

Second, the Operator's Specification has to changed as follows:

Section 4.4.2 "XML Encoding"
Replace
"All XML messages must be encoded in UTF-8."
with
"All XML messages must be encoded either in UTF-8 or UTF-16."

There is no need for a change of both the Data Structure Reference and the Replication Specification.

Best regards,
 Claus


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]


Powered by eList eXpress LLC