about use of AFA format

Rafal Maszkowski <rzm@oso.chalmers.se> Fri, 26 August 1994 21:39 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa06510; 26 Aug 94 17:39 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa06506; 26 Aug 94 17:39 EDT
Received: from mocha.Bunyip.Com by CNRI.Reston.VA.US id aa16996; 26 Aug 94 17:40 EDT
Received: by mocha.bunyip.com (5.65a/IDA-1.4.2b/CC-Guru-2b) id AA04752 on Fri, 26 Aug 94 17:11:22 -0400
Received: from oden.oso.chalmers.se by mocha.bunyip.com with SMTP (5.65a/IDA-1.4.2b/CC-Guru-2b) id AA04748 (mail destined for /usr/lib/sendmail -odq -oi -fiafa-request iafa-out) on Fri, 26 Aug 94 17:11:14 -0400
Received: by oden.oso.chalmers.se (5.64/0.0) id AA28078; Fri, 26 Aug 94 23:11:04 +0200
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Rafal Maszkowski <rzm@oso.chalmers.se>
Message-Id: <9408262111.AA28078@oden.oso.chalmers.se>
Subject: about use of AFA format
To: iafa@bunyip.com
Date: Fri, 26 Aug 1994 23:08:54 +0200 (MET)
X-Acknowledge-To: <rzm@oso.chalmers.se>
Latin-Date: Vineri XXVI August A.D. MCMXCIV
X-Mailer: ELM [version 2.4 PL23]
Content-Type: text
Content-Length: 2620
X-Orig-Sender: rzm@oso.chalmers.se

      2.1 
spelling: unqiue

      3.6.3 MISCELLANEOUS

      The following is a list of generic data element subcomponents used
      when referring to particular resources. These can be added to any
      of the templates described below.

Can they be added many times? I guess not..

It would be convenient to have multiple Description-v* and URI-v* (and
others) in SERVICE template. I'm maintaining a list of network
resources in Poland
(gopher://gopher.mat.uni.torun.pl/00/sieci-w-pl/Polskie_Zasoby_Sieciowe
http://www.ict.pwr.wroc.pl/pzs/pzs.html) in my own format and for me it
seems to be more natural to have possibility to specify various access
types to e.g. to X.500 gate through telnet, gopher and WWW in one
template.  They (access methods) are equivalent in the same way as
document.txt and document.ps are.

The same with mailing lists - the running list itself and its archive
isn't exatly the same but I would prefer to have information about
subscribing and ftp achives URIs, listserv archive URI and comment,
gopher archives URIs and News group URI in one template. Mailing list
and Usenet group where is it gatewayed to are obviously equivalent.

Another use of multiple URI-v*s etc. would be in LARCHIVE. It is always
possible to create a separate template for every possible
URI/package/area available in the archive and this is closer to the
idea of the format but example of LARCHIVE shows that Keywords fiels
has several topics included. Why not to have also URIs for all or some
of them in the same template?

      3.8.2 ORGANIZATION INFORMATION
...
      Notes on this file.

      <1> The Internet protocol used to communicate with this service.

I don't see any previous <1> in this section.

      3.8.4 DOCUMENTS, DATASETS, MAILING LIST ARCHIVES, USENET ARCHIVES,
            SOFTWARE PACKAGES, IMAGES AND OTHER OBJECTS
...
      Example 2
...
      URI-v0:           gopher://power.org/1/pub/Vfifth.tar.Z

I think it should be:
      URI-v0:           gopher://power.org/00/pub/Vfifth.tar.Z

Bibliography

IMHO it would be better to add UR[IL]s to all entries.

My General Remarks

The order of the fields is not specified (if I'm not wrong). It is
good because I'd like to have always Title field as the first one
to make  waisindex -t para  returning these lines in my gopher..
(like gopher://gopher.mat.uni.torun.pl/77/sieci-w-pl/.lists/index
does)

R.
PS. Excuse me if something of the above have been discussed before.
-- 
Rafal Maszkowski rzm@oso.chalmers.se      http://www.mat.uni.torun.pl/~rzm
Opinia publiczna powinna byc zaalarmowana swoim nieistnieniem - St. J. Lec