Re: new iafa draft

Jon Knight <J.P.Knight@lut.ac.uk> Thu, 11 January 1996 15:04 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa09732; 11 Jan 96 10:04 EST
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa09728; 11 Jan 96 10:04 EST
Received: from services.Bunyip.COM by CNRI.Reston.VA.US id aa07402; 11 Jan 96 10:04 EST
Received: (from daemon@localhost) by services.bunyip.com (8.6.10/8.6.9) id KAA01964 for iafa-out; Thu, 11 Jan 1996 10:02:25 -0500
Received: from mocha.bunyip.com (mocha.Bunyip.Com [192.197.208.1]) by services.bunyip.com (8.6.10/8.6.9) with SMTP id KAA01956 for <iafa@services.bunyip.com>; Thu, 11 Jan 1996 10:02:18 -0500
Received: from bgate.lut.ac.uk by mocha.bunyip.com with SMTP (5.65a/IDA-1.4.2b/CC-Guru-2b) id AA05355 (mail destined for iafa@services.bunyip.com); Thu, 11 Jan 96 10:01:50 -0500
Received: (jon@localhost) by weeble.lut.ac.uk (8.7.3/8.6.9) id PAA25359; Thu, 11 Jan 1996 15:01:07 GMT
Date: Thu, 11 Jan 1996 15:01:06 +0000 (GMT)
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Jon Knight <J.P.Knight@lut.ac.uk>
To: Thomas Krichel <T.Krichel@surrey.ac.uk>
Cc: Chris Weider <clw@bunyip.com>, iafa@bunyip.com
Subject: Re: new iafa draft
In-Reply-To: <9601102102.AA16368@central.surrey.ac.uk>
Message-Id: <Pine.SUN.3.91.960111145424.24234U-100000@weeble.lut.ac.uk>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Orig-Sender: owner-iafa@bunyip.com
Precedence: bulk

On Wed, 10 Jan 1996, Thomas Krichel wrote:
>   One approach to resolve the problems with the current draft
>   is to dump the concept of version to replace it by a part
>   concept. A resource could be thought of as a collection of
>   files that are related in some way. How they related to each
>   other is difficult to express in  a template form. Thererfore
>   one should list the parts, the format of each part and 
>   a description of its functionality.

I think if we're going to get rid of variants (I assume that's what you 
mean by version) then we might as well go the whole hog and have proper 
heirarchical templates rather than a single flat file.  And once you've 
done that, its but a short step to SGML style markup...

>   Abstract: This resource is about the sex life of snowpeople
>   Part: Slides with main results in English
>   Format: application/slideprocessor
>   URL: snow.slide
>   Part: Slides with main results in French
>   Format: application/slideprocessor
>   URL: neige.slide
>   Format: application/video
>   Part: Video of Snowpeople having sex, in French
>   URL: sexedeneige.video
>   Format: text/fortram
>   Part: programme to compute increase in room temperature through
>         sexual activity of snowpeople
>   URL:  snowsextemper.for

How do you associate the URL and Format (and I guess other "variant" 
style information) to the part name?  They don't seem to be in any 
particular order and there's now no variant number holding the bits 
together even if they're spread throughout the template.

Jon

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Jon "Jim'll" Knight, Researcher, Sysop and General Dogsbody, Dept. Computer
Studies, Loughborough University of Technology, Leics., ENGLAND.  LE11 3TU.
* I've found I now dream in Perl.  More worryingly, I enjoy those dreams. *