W3C home > Mailing lists > Public > xml-dist-app@w3.org > April 2001

Internationalization issue.

From: David Clay <david.clay@oracle.com>
Date: Fri, 27 Apr 2001 13:34:53 -0700
Message-ID: <3AE9D7ED.5E4BA06C@oracle.com>
To: xml-dist-app@w3.org
I received this mail from a member of the internationalization group
reminding me of an issue that was raised during our f2f in Boston which
was not recorded in my subsequent mail.

I believe that this should be added to the issues list.  The issue
is that unnormalized payloads cannot predictably be routed based
upon their content.

We can, of course, decide that this is an issue which we need not
but I think we should capture it.

> Tex Texin wrote:
> David,
> With respect to XMLP, and the Character Model:
> In:
> http://lists.w3.org/Archives/Member/w3c-i18n-wg/2001Mar/0222.html
>"David Clay (by way of Martin Duerst )" wrote:
>    * XML protocol need not normalize application payloads or check to
> insure that they are normalized
> During the discussion, I raised a question about content-sensitive
> routing of such payloads.
> I remember we discussed this, but I don't recall the details of the
> answer or perhaps someone was going to go off and think about it.
> If the payload is not normalized, but the routing services look
> at the content of the payload to determine where the payload
> should be sent, then the routing is not predictable.
> For example, if it is needed to specify that any payload that
> includes the term FOO-BAR be sent to a particular location,
> and if the payloads can contain unnormalized variations of FOO-BAR,
> then some of the payloads may not be routed to the right
> places. (At least by some definitions.)
> Is this a concern?
> tex

> Tex Texin                      Director, Product Management
> mailto:Texin@Progress.com      +1-781-280-4271 Fax:+1-781-280-4655
> Progress Software Corp.        14 Oak Park, Bedford, MA 01730
Received on Friday, 27 April 2001 17:33:52 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 22:01:13 UTC