Re: http charset labelling

Keld J|rn Simonsen <keld@dkuug.dk> Thu, 01 February 1996 21:47 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa21069; 1 Feb 96 16:47 EST
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa21065; 1 Feb 96 16:47 EST
Received: from services.Bunyip.COM by CNRI.Reston.VA.US id aa13883; 1 Feb 96 16:47 EST
Received: (from daemon@localhost) by services.bunyip.com (8.6.10/8.6.9) id OAA22525 for uri-out; Thu, 1 Feb 1996 14:26:17 -0500
Received: from mocha.bunyip.com (mocha.Bunyip.Com [192.197.208.1]) by services.bunyip.com (8.6.10/8.6.9) with SMTP id OAA22520 for <uri@services.bunyip.com>; Thu, 1 Feb 1996 14:26:13 -0500
Received: from dkuug.dk by mocha.bunyip.com with SMTP (5.65a/IDA-1.4.2b/CC-Guru-2b) id AA29092 (mail destined for uri@services.bunyip.com); Thu, 1 Feb 96 14:26:07 -0500
Received: (from keld@localhost) by dkuug.dk (8.6.12/8.6.12) id UAA26497; Thu, 1 Feb 1996 20:24:13 +0100
Message-Id: <199602011924.UAA26497@dkuug.dk>
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Keld J|rn Simonsen <keld@dkuug.dk>
Date: Thu, 01 Feb 1996 20:24:11 +0100
In-Reply-To: Larry Masinter <masinter@parc.xerox.com> "Re: http charset labelling" (Feb 1, 19:07)
X-Charset: ISO-8859-1
X-Char-Esc: 29
Mime-Version: 1.0
Content-Type: Text/Plain; Charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
Mnemonic-Intro: 29
X-Mailer: Mail User's Shell (7.2.2 4/12/91)
To: Larry Masinter <masinter@parc.xerox.com>
Subject: Re: http charset labelling
Cc: uri@bunyip.com
X-Orig-Sender: owner-uri@bunyip.com
Precedence: bulk

Larry Masinter writes:

> > The notation should not be on business cards etc, I think we
> > all agree on this. It should not either be in URLs in html docs,
> > I also think we all agree on that.
> 
> No, I completely disagree. If people are going to be so foolish as to
> put their URLs on their business cards, they should put them there in
> a form that is useful. And certainly HTML documents absolutely need to
> know how the URL is represented.

I am not sure what you are saying here: do you mean that the user
should know what charset the URL is encoded in at the server?
I think you previously said that URLs are independent of encoding,
also Franc,ois said that it is not possible to see on a business
card what charset the c-cedille in his name is coded in.
This is also a general paradigme in IT standardization: you
operate on an abstract character level.

Or do you say that a URL should clearly identify where a 
resource is located? I do not disagree to that one.

Keld