Re: Header referring to external source equivalent to MIME body part

• Messages sorted by: [ date ][ thread ][ subject ][ author ]
• Next message: pshuang@MIT.EDU: "Copyright notice added to rtfm.mit.edu archives"
• Previous message: Larry W. Virden, x2487: "Re: Web part of the "FAQ Book" project"

To follow up on what Harald.T.Alvestrand@uninett.no said ...

So, I would stick with Location, to minimize the divergence.
If the rest of the community (hi, folks!) doesn't agree with me, let's
do Content-Location.

Harald A

I don't think that we can simply adopt the HTTP usage, because (I
believe you said) they have imposed the additional rule that only
one such reference shall appear. At least in the faq-maintainers
community, there is a desire to mark up a copy of a document with
headers which identify more than one "Where to get this FAQ"
items.

In HTML usage, this information is going to be inline in a
"How to get this FAQ" paragraph within the document.

In the existing News.Answers practice, there is an email submission
to a two-step process of automatic scrub and manual review where
the correct use of headers is part of the process.

In looking to future extensions, the faq-maintainers mailing list
are trying to come up with an optimal encoding for the URL to
the master (and perhaps alternate) location [or retrieval method]
for documents which are widely mirrored.

This seems to me to be exactly the same function that MIME needs
here -- a header or metadata attribute that I might spell:

Hi-I-am: <URL or external-message-body-compatible-script> <Heuristic text>.

Al Gilman

• Next message: pshuang@MIT.EDU: "Copyright notice added to rtfm.mit.edu archives"
• Previous message: Larry W. Virden, x2487: "Re: Web part of the "FAQ Book" project"

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