I lean towards the servient approach, myself.
> To talk tech rather than generalities, maybe we can extend the auxillary
> header of FAQ's. For example, to use the UUCP internals FAQ again (sorry
> for picking on you Ian if you're watching :-) ):
>
> Archive-name: uucp-internals
> Version: $Revision: 1.26 $
> Last-modified: $Date: 1994/10/26 02:39:07 $
> Longer-Version-At: <URL:http://airs.com/uucp-internals-long.html>
> Longer-Version-At: <URL:ftp://airs.com/pub/uucp-internals-long.txt>
>
> The normal FAQ posting would be a shorter summary, probably including a
> natural language description of "where to get the full thing" for those
> without smart newsreaders. Smart newsreaders could detect the
> "Longer-Version-At" field and fire off some kind of request for the rest
> if the user wants it. Maybe even through a ftpmail or httpmail gateway for
> those without IP links.
Clever. Good hack. Not hard to do. <Applause>
> The name "Longer-Version-At" is negotiable. It was the first thing that
> popped into my head. The "<URL:...>" notation is for some of the newer
> newsreaders that will probably have support for that semi-standard but
> won't know about "Longer-Version-At".
I was originally going to suggest making it "WWW-Version-At:" until I realized
I was looking at the wrong abstraction. Instead of thinking of the field as
a WWW pointer, think of it as a kind of reference that can point either at
another news article or at an URL or URN. Maybe it should be called
"Pointer-To:" or "Advertisement-For": :-)
-- Eric S. Raymond <esr@locke.ccil.org> WWW: //www.thyrsus.com/~esr/home.html
[
Usenet Hypertext FAQ Archive |
Search Mail Archive |
Authors |
Usenet
]
[
1993 |
1994 |
1995 |
1996 |
1997
]
© Copyright The Landfield Group, 1997
All rights reserved