Message-Id: <33556428.93B@parc.xerox.com> Date: Wed, 16 Apr 1997 16:43:36 PDT From: Larry Masinter <email@example.com> To: firstname.lastname@example.org Subject: A workable alternative to "hex-encoded UTF-8 encoded URLs" If the problem of "users need to be able to see and write URLs in their preferred script" is important, there's a way to solve that problem actually: don't actually use URLs for this service. Instead, use a directory service that can accomodate - multiple case - multiple spellings for the same name - multiple scripts and script interpretation These multiple script references can be read on the radio, printed in magazines and on matchbook covers. The "Open Location" box in browsers would need to be changed so that it would look up the 'location' in the directory service. I call these "FRLs": Friendly Resource Locators. They're not Uniform, but they can be used to locate resources. It will require the development of a global infrastructure for a directory service, but that is actually easier to imagine than the global deployment of user agents that could handle hex-encoded UTF-8 encoded URLs. In the meanwhile, we should let the URL standard progress from Proposed to Draft without adding the baggage of a non-solution. Larry -- (These are not the droids you are looking for).