W3C home > Mailing lists > Public > xmlp-comments@w3.org > February 2002

Re: Resolution of Content Based Routing issue

From: Tex Texin <texin@progress.com>
Date: Tue, 12 Feb 2002 23:33:52 -0500
Message-ID: <3C69ECB0.F703115F@progress.com>
To: David Fallside <fallside@us.ibm.com>
CC: xmlp-comments@w3.org, W3c I18n Group <w3c-i18n-ig@w3.org>
David,

Thanks for your response.

The suggestion below seems to contradict the principle of early
normalization specified in the Character Model. However, as the
examination of content is outside the scope of SOAP 1.2, and therefore
the normalization of the content is irrelevant to SOAP 1.2, we can agree
the issue is resolved.

However, at the time the XML Protocol Working Group is ready to consider
operations that require examination of content, the I18N working group
would like to discuss normalization with you and consider ideas for
solutions that also meet the goals of early normalization.

Regards,

Tex Texin

David Fallside wrote:
> 
> The XML Protocol Working Group has resolved to close its issue #98 [1] with
> the text quoted below. You are the originator of this issue, and so we are
> informing you of our decision. If you think this resolution does not
> address the issue, please let me know.
> 
> Routing is not within the scope of SOAP 1.2, but can
> specified using the extension mechanisms provided by SOAP 1.2.  If
> normalization is required for content-based routing extensions to work
> properly, then the specifications for content-based routing extensions must
> 
> ensure normalization.  This appears to be feasible by defining a SOAP
> header block (with mustUnderstand="true") whose semantics would imply that
> the SOAP envelope (and its descendants) be normalized before applying a
> content-based routing function.  In addition, a related extension feature
> could use a SOAP header block to indicate explicitly that a SOAP envelope
> has not yet been normalized; such a header block can be removed after the
> envelope has been normalized.  To reiterate, extensions for routing and
> normalization are not within the scope of the SOAP 1.2 specifications.
> 
> [1] http://www.w3.org/2000/xp/Group/xmlp-issues.html#x98
> 
> ............................................
> David C. Fallside, IBM
> Ext Ph: 530.477.7169
> Int  Ph: 544.9665
> fallside@us.ibm.com

-- 
-------------------------------------------------------------
Tex Texin                    Director, International Business
mailto:Texin@Progress.com    Tel: +1-781-280-4271
the Progress Company         Fax: +1-781-280-4655
-------------------------------------------------------------
Find out about Globalization Empowerment for Progress users
mailto:global-empowerment@progress.com
For a compelling demonstration for Unicode:
http://www.geocities.com/i18nguy/unicode-example.html
Received on Tuesday, 12 February 2002 23:33:56 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 27 October 2009 08:42:27 GMT