This also looks good.
Thanks,
Spencer
----- Original Message -----
From: "Arnt Gulbrandsen" <[EMAIL PROTECTED]>
To: "Spencer Dawkins" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>; "General Area Review
Team" <[email protected]>; "Lisa Dusseault" <[EMAIL PROTECTED]>
Sent: Friday, August 18, 2006 12:53 PM
Subject: Re: [Gen-art] Gen-ART Review of draft-newman-i18n-comparator-13.txt
I noticed this one too late to mention in the other answer.
Spencer Dawkins writes:
5.2. Operations
...
Although the collation's substring function provides a list of
matches, a protocol need not provide all that to the client. It may
provide only the first matching substring, or even just the
information that the substring search matched.
Hmmm. I am trying to remember that you're not defining a protocol, only
describing what protocols do and don't do, but I'm trying to read this
from the application's perspective, and having a hard time understanding
how (for example) an application that is trying to display what is
matching responds when the protocol only provides an indication that
something matched. You may say this is what the protocol developers are
supposed to worry about ("if you think applications will want to display
what matches, you'd better define the protocol so that this information is
returned"), and that's OK. I'm just struggling a bit here.
Appended text: «In this way, collations can be used with protocols that
are defined such that "x is substring of y" returns true-false.»
Arnt
_______________________________________________
Gen-art mailing list
[email protected]
https://www1.ietf.org/mailman/listinfo/gen-art
