On 28-Oct-25 05:08, John Levine wrote:
It appears that Russ Housley <[email protected]> said:
Searches whose results might include RFCs should return accurate
results and support appropriate Unicode string matching behaviors.
Anyone who has recently used well known search tools, especially those
"enhanced" by AI, will have a good laugh at "searches ... should
return accurate results". I really don't see much point in the whole
sentence, since it appears to set requirements for all search engines.
If it's intended to apply to search tools provided by the RPC, it
should say so. If not, I suggest striking the whole sentence.
RFC 7997 does not have a similar discussion. Rather, RFC 7997 talks
about "searches against RFC indexes and database tables". I do not
recall any discussion about expanding the scope to include searches
within RFC documents. Maybe it is my memory, but I want to make
sure there is consensus around this topic.
That seems to me to open multiple cans of worms. If we want to include
old RFCs, some use obsolete encodings, some are only in Postscript, and
otherwise not easy to search reliably. For modern RFCs, I don't know what
"appropriate Unicode string matching" means and I don't want to try to
define it here. Character normalization? Language specific case folding?
LTR vs RTL strings?
I think it would be interesting at some point to think about how to
address this issue, but not in this document and not now.
Right. A conceivable policy is something like: "Any search tools
provided by the RPC should support searches for Unicode strings as
well as any other encodings used in the RFC series." But saying
nothing seems wiser.
Regards
Brian
--
rswg mailing list -- [email protected]
To unsubscribe send an email to [email protected]
