Re: filenaming proposal for IAFA description files
Matti Aarnio <mea@nic.funet.fi> Wed, 21 October 1992 11:10 UTC
Received: from ietf.nri.reston.va.us by IETF.NRI.Reston.VA.US id aa00918; 21 Oct 92 7:10 EDT
Received: from NRI.RESTON.VA.US by IETF.NRI.Reston.VA.US id aa00914; 21 Oct 92 7:10 EDT
Received: from kona.CC.McGill.CA by NRI.Reston.VA.US id aa04122; 21 Oct 92 7:11 EDT
Received: by kona.cc.mcgill.ca (5.65a/IDA-1.4.2b/CC-Guru-2b) id AA11199 on Wed, 21 Oct 92 02:06:57 -0400
Received: from nic.funet.fi by kona.cc.mcgill.ca with SMTP (5.65a/IDA-1.4.2b/CC-Guru-2b) id AA11195 (mail destined for /usr/lib/sendmail -odq -oi -fiafa-request iafa-out) on Wed, 21 Oct 92 02:06:51 -0400
Received: by nic.funet.fi id <91193>; Wed, 21 Oct 1992 08:03:18 +0200
Subject: Re: filenaming proposal for IAFA description files
Sender: ietf-archive-request@IETF.NRI.Reston.VA.US
From: Matti Aarnio <mea@nic.funet.fi>
To: Aydin Edguer <edguer@alpha.ces.cwru.edu>
Date: Wed, 21 Oct 1992 08:03:08 +0200
Cc: iafa@cc.mcgill.ca
In-Reply-To: <9210202338.AA12890@alpha.CES.CWRU.Edu>; from "Aydin Edguer" at Oct 21, 92 1:38 am
X-Mailer: ELM [version 2.3 PL11]
Message-Id: <92Oct21.080318eet.91193@nic.funet.fi>
> > Now, this filename will obviously have to be different for ... > > Well, after reading over the new iafa-doc2, I have yet another suggestion > to make. Rather than limiting the names of the IAFA- files to a particular > name/extension/case, I suggest you have a single file that meets all the > restrictions of known operating system names. This single file will give > the mapping from IAFA- document name to system dependent name. Software > that is doing mirroring could then grab the one known name file, parse > its contents and use that to obtain the other IAFA- documents. This may > [I hope] help in the automation of IAFA- data. > > Implementable? From practicality viewpoint: Yes, very much so! That first file should be named something which is implementable at all systems (6+3 ? 8+3 ?) and then all the rest is just a question of simple mapping. However those maps should contain BOTH directory info and real filenames - for beasts like IBM CMS with a bit odd "directory" structure... Model: IAFA-foobar: "string for CWD argument" "target.file" (And as it is all text anyway - ASCII or EBCDIC - that need not be defined ?) > Aydin Edguer /Matti Aarnio <mea@nic.funet.fi>
- filenaming proposal for IAFA description files Markus Stumpf
- Re: filenaming proposal for IAFA description files Alan Emtage
- Re: filenaming proposal for IAFA description files Aydin Edguer
- Re: filenaming proposal for IAFA description files Markus Stumpf
- Re: filenaming proposal for IAFA description files Mark Prior
- Re: filenaming proposal for IAFA description files Aydin Edguer
- Re: filenaming proposal for IAFA description files Matti Aarnio
- Re: filenaming proposal for IAFA description files Olle Jarnefors