Re: revised "generic syntax" internet draft

Karen R. Sollins (sollins@lcs.mit.edu)
Thu, 24 Apr 1997 11:35:13 -0400


Date: Thu, 24 Apr 1997 11:35:13 -0400
Message-Id: <199704241535.LAA10690@lysithea.lcs.mit.edu>
From: "Karen R. Sollins" <sollins@lcs.mit.edu>
To: cherlin@newbie.net
Cc: uri@bunyip.com
In-Reply-To: <v0300780baf8466ef2424@[206.245.192.47]> (message from Edward
Subject: Re: revised "generic syntax" internet draft

   X-Sender: cherlin@snowcrest.net
   References: <Pine.SUN.3.96.970421120702.245F-100000@enoshima>
   Mime-Version: 1.0
   Content-Type: text/plain; charset="us-ascii"
   Date: Thu, 24 Apr 1997 00:09:11 -0700
   From: Edward Cherlin <cherlin@newbie.net>
   Sender: owner-uri@bunyip.com
   Precedence: bulk

...

   I have said at least ten times in this discussion, with no acknowledgement
   from anyone, that we are to assume that people will not publish Unicode
   URLs without knowing that their servers support them.

   If I am going to create an ftp: site, and I don't check what version of
   what ftp server I'm using, I'm a fool, and likewise for gopher: and telnet:
   and the others. If I put out an https: URL and I don't have a secure server
   to receive it, I'm a fool. If I intend to accept encoded UTF-8, I need to
   find out how my server can deal with it. If I don't intend to accept it, I
   can regard encoded UTF-8 in URLs as plain ASCII, without breaking any
   process that is not already broken.

...

   --
   Edward Cherlin     cherlin@newbie.net     Everything should be made
   Vice President     Ask. Someone knows.       as simple as possible,
   NewbieNet, Inc.                                 __but no simpler__.
   http://www.newbie.net/                Attributed to Albert Einstein


Edward and everyone,

I have tried VERY hard to stay out of this discussion, but I know have
to ask a question as suggested by the extraction above.  Must one
conclude from a position of supporting encoding of character sets in
UTF-8 that the server at the site of the resource MUST be of a certain
flavor supporting that character set, and furthermore that perhaps the
general practice will be that each server will only support one or a
small number?  With no general solution implemented globally, those
with less popular character sets (this often goes hand in hand with
less technology and less economic strength) are much more likely to be
left out in the cold.  So much for general internationalization,
unless this means only internationalization for the larger, richer
communities.

			Karen Sollins

___________________________________________________________________
Karen R. Sollins				sollins@lcs.mit.edu
Research Scientist				Phone: 617/253-6006
M.I.T. Laboratory for Computer Science		Fax:   617/253-2673
545 Technology Square
Cambridge, MA 02139