URL character set

Larry Masinter (masinter@parc.xerox.com)
Tue, 3 Mar 1998 12:44:02 PST


Message-ID: <023f01bd46e5$19a46060$e3d3000d@bronze-208.parc.xerox.com>
From: "Larry Masinter" <masinter@parc.xerox.com>
To: "Al Gilman" <asgilman@access.digex.net>
Cc: <uri@Bunyip.Com>
Date: Tue, 3 Mar 1998 12:44:02 PST
Subject: URL character set

Al Gilman
# The restriction to the current RFC-822-header-safe subset of
# ASCII is temporary under the plans as I hear them.  But it does
# not make sense to open this up to a schemewise free-for-all or the
# clients will choke on the necessary library.  Saying that some
# clients will support some schemes defeats the purpose.  The point
# of URIs is so that more clients can support more schemes.

# I think that

# "Character Set" Considered Harmful
# http://www.w3.org/MarkUp/html-spec/charset-harmful.html

# may be relevant here.

Check out ftp://ds.internic.net/draft-masinter-url-i18n-00.txt 

I think  we might want to remove the idea of a 'new kind of URL', though,
and call it an EURI. If I get comments this week, I'll try to incorporate 
them in a revised version.