Re: revised "generic syntax" and "data:" internet drafts

Dan Oscarsson <Dan.Oscarsson@trab.se> Tue, 08 April 1997 14:35 UTC

Received: from cnri by ietf.org id aa21122; 8 Apr 97 10:35 EDT
Received: from services.Bunyip.Com by CNRI.Reston.VA.US id aa13544; 8 Apr 97 10:34 EDT
Received: (from daemon@localhost) by services.bunyip.com (8.8.5/8.8.5) id KAA19512 for uri-out; Tue, 8 Apr 1997 10:01:57 -0400 (EDT)
Received: from mocha.bunyip.com (mocha.Bunyip.Com [192.197.208.1]) by services.bunyip.com (8.8.5/8.8.5) with SMTP id KAA19502 for <uri@services.bunyip.com>; Tue, 8 Apr 1997 10:01:45 -0400 (EDT)
Received: from malmo.trab.se by mocha.bunyip.com with SMTP (5.65a/IDA-1.4.2b/CC-Guru-2b) id AA17793 (mail destined for uri@services.bunyip.com); Tue, 8 Apr 97 10:01:42 -0400
Received: from valinor.malmo.trab.se (valinor.malmo.trab.se [131.115.48.20]) by malmo.trab.se (8.7.5/TRAB-primary-2) with ESMTP id JAA15270; Tue, 8 Apr 1997 09:00:10 +0200 (MET DST)
Received: by valinor.malmo.trab.se (8.7.5/TRM-1-KLIENT); Tue, 8 Apr 1997 09:00:10 +0200 (MET DST) (MET)
Date: Tue, 08 Apr 1997 09:00:10 +0200
From: Dan Oscarsson <Dan.Oscarsson@trab.se>
Message-Id: <199704080700.JAA13330@valinor.malmo.trab.se>
To: mduerst@ifi.unizh.ch, masinter@parc.xerox.com
Subject: Re: revised "generic syntax" and "data:" internet drafts
Cc: cherlin@newbie.net, uri@bunyip.com
Mime-Version: 1.0
Content-Md5: C4h1HyQ52uE67/2CQC2Z2w==
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: owner-uri@bunyip.com
Precedence: bulk

> 
> I think that it would be reasonable to have a new "Proposed
> Standard" that covers 8-bit URLs in UTF-8 as well as
> the recommendation that 7-bit URLs be encoded with %NN.
> Since this proposal wouldn't be incompatible with
> draft-fielding-url-syntax-04.txt, it can progress
> independently. I think any proposed standard for UTF-8
> encoded URLs would have a different range of applicability
> than for ASCII URLs.

So we should have two standards of how the syntax of an URL should be?

Even if we define a new proposed standard: url-i18n-syntax that
references the ascii url-syntax, some people may stop at the ascii
standard and miss the i18n one and there may be a wording conflict.

One way could be to withdraw the current url standard and publish a new,
or we could do as you propose if the ascii url-syntax standard
clearly states that if a URL is used internationally the standard
defined by the url-i18n-syntax should be used. Martin, I and a few others
colud probably put together a url-i18n-syntax draft that could be published
simulataneously with the url-syntax draft.
What do you think Martin?

R   Dan