Re: IAFA: PLEASE ... or we will probably use

Markus Stumpf <stumpf@informatik.tu-muenchen.de> Tue, 22 March 1994 21:37 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa18412; 22 Mar 94 16:37 EST
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa18402; 22 Mar 94 16:37 EST
Received: from mocha.bunyip.com by CNRI.Reston.VA.US id aa16044; 22 Mar 94 16:36 EST
Received: by mocha.bunyip.com (5.65a/IDA-1.4.2b/CC-Guru-2b) id AA06953 on Tue, 22 Mar 94 14:31:47 -0500
Received: from tuminfo2.informatik.tu-muenchen.de by mocha.bunyip.com with SMTP (5.65a/IDA-1.4.2b/CC-Guru-2b) id AA06947 (mail destined for /usr/lib/sendmail -odq -oi -fiafa-request iafa-out) on Tue, 22 Mar 94 14:29:58 -0500
Received: from hprbg5.informatik.tu-muenchen.de ([131.159.0.200]) by tuminfo2.informatik.tu-muenchen.de with SMTP id <326490>; Tue, 22 Mar 1994 20:29:31 +0100
Received: by hprbg5.informatik.tu-muenchen.de id <311468>; Tue, 22 Mar 1994 20:29:06 +0100
Subject: Re: IAFA: PLEASE ... or we will probably use
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Markus Stumpf <stumpf@informatik.tu-muenchen.de>
To: iafa@bunyip.com
Date: Tue, 22 Mar 1994 20:28:59 +0100
X-Mailer: ELM [version 2.4 PL6]
Content-Type: text
Content-Length: 2399
Message-Id: <94Mar22.202906mesz.311468@hprbg5.informatik.tu-muenchen.de>

|>Subject: Re: IAFA: PLEASE ... or we will probably use
                                                    ^^^
It was late in the night ... this should read loose ;)

|>What issues are outstanding against the current draft?  My archive vaporized
|>recently and I nee to suck up new ones anyhow.

I (and others) sent in corrections and additions. I'd sent a proposal
for a  AFA-MIRROR  type (which was never discussed in any way).
It is in the archive and there were problems with our local redist ...
Did anybody receive it?

(A working example can be found:
  http://www.informatik.tu-muenchen.de/isar/mirror/de-mirror.engl.html)

I'd also sent some comments about collapsing some of the tags using URLs
like e.g.:

Access-Protocol-v*
Access-Host-Name-v*
Access-Host-Port-v*
Pathname-v*

This could be all put in one tag using a URL:
  protocol://hostname:port/pathname

Same for the User/Organization: All this information could be
in a single file and would easily be addressed using a URL.
And this would also make it rather simple to maintain the information
as in most cases one can still support the location (i.e. the URL) and
would only have to maintain ONE file instead of 10, 20 or 100 in case of
a change in e.g. a telephone or fax number.

I also asked for some clarification or practicable examples
concerning the use of *-Handle:
The documentation and the example is rather vague.

There are some efforts in using IAFA stuff:
See:
o  http://web.nexor.co.uk/aliweb/doc/aliweb.html
     or more specifically
   http://web.nexor.co.uk/aliweb/doc/iafa/iafa.html
     (on this page Martijn has also notes on some problems he's having).

o http://www.informatik.tu-muenchen.de/cgi-bin/archive_access/pub/comp/X11/contrib/clients/00-index.html
    or
  http://www.informatik.tu-muenchen.de/cgi-bin/archive_access/pub/comp/platforms/pc/00-index.html
      This are two examples, where we use the (old style) AFA templates spead
      all over our archive to create a more comfortable access to our archive
    or
  gopher://gopher.informatik.tu-muenchen.de/77/.wais-db/ftp-index
      for a WAIS database of all the AFA files in our archive.


	\Maex
-- 
______________________________________________________________________________
 Markus Stumpf                        Markus.Stumpf@Informatik.TU-Muenchen.DE 
                                http://www.informatik.tu-muenchen.de/~stumpf/