Re: About spaces in URL's and such.

---------

Al Gilman (asgilman@access.digex.net)
Fri, 1 Dec 1995 17:09:11 -0500 (EST)


From: "Lennart Regebro" <lennart@bump.traffic.is>
On 1 Dec 95 at 10:17, Martin Leese - OMG wrote:

>>> In this case, there is a definite RFC822-type of syntax, so that
>>> pretty much wraps it up, doesn't it?
>
>Yes. I would say that where a standard exists we have an obligation
>to use it, unless there is a VERY good reason not to.

Couldn't agree more. Then I know where my vote will go when it comes
to the syntax of the line.

>>> Url: <URL:http://www.domain.foo/pub/faq/my.faq> "Descriptive Text"
>
>Yes. This is ugly but headers, even auxiliary ones, are not meant to
>be pretty. It is nice when they are, but that is a bonus and should
>not be a requirement.

On encoding within headers:
The note from Olle Jarnefors (I believe) demonstrates that the
syntax suggested in RFC 1808 has internationalization problems.

The header doesn't need to be called 'Url:'. 'Reference:' might
actually be a better name.

On the field-name:
There is a "References:" header already in RFC 822; It takes a list
of entries, identified either by <message-unique@host.domain.path>
forms or "phrase" entries, typically the subject header
of the referenced topic.

[ When I suggested introducing a new uri-cite alternative in [the
list in] this header in some syntax which would be a legal value
of the pre-existing "phrase" syntax, Harald Alvestrand was
guardedly postitive. I want to make URLs work in the
"References:" header but it's a little more complicated thay you
would indicate.]

The existing standard header which really means what you
want is the "Location:" header used in HTTP. MIME would want you
to spell it "Content-location:" (see the brawl Bill Wohler
referred to).

I am afraid that the clean way to do this is not to use two
header atoms here, but to define an URL-parameter such as
"cite-as= " The combined effect of these transforms would be to
change the example

from
Reference: <URL:http://www.domain.foo/pub/faq/my.faq> "Descriptive Text"

to
Location: <URL:http://www.domain.foo/pub/faq/my.faq;
cite-as="Descriptive Text">

or
References: <URL:ftp://rtfm.mit.edu/pub/usenet/my-native-group/my-faq.txt;
cite-as="Latest official My FAQ">
<URL:ftp://ftp.domain.foo/pub/faq/my.faq;
cite-as="Current draft revision of My FAQ">
<URL:http://www.domain.foo/pub/faq/my.faq;
cite-as="Clickable but not always current translation of My FAQ">
Next-header:

<I do not claim to have worked all the encoding requirements of these
examples...>

Harald referred to a Birds Of a Feather (BOF) session to be held
at Dallas to discuss citations. This is the standard method of
testing the water to see if there is probable cause to start a
Working Group on a topic. As I have been telling them, FAQs are
a critical application for anything that they might come up with
in this area. I suspect that the functional equivalent of my
hypothetical "cite-as" parameter seems to me to be something that
would be needed very generally.

Al Gilman



[ Usenet Hypertext FAQ Archive | Search Mail Archive | Authors | Usenet ]
[ 1993 | 1994 | 1995 | 1996 | 1997 ]

---------

faq-admin@landfield.com

© Copyright The Landfield Group, 1997
All rights reserved