Re: IAFA templates: a user's comment

Jill Foster <Jill.Foster@newcastle.ac.uk> Mon, 03 April 1995 01:52 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa08934; 2 Apr 95 21:52 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa08930; 2 Apr 95 21:52 EDT
Received: from services.Bunyip.COM by CNRI.Reston.VA.US id aa14530; 2 Apr 95 21:52 EDT
Received: (from daemon@localhost) by services.bunyip.com (8.6.10/8.6.9) id VAA17674 for iafa-out; Sun, 2 Apr 1995 21:51:12 -0400
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 VAA17661 for <iafa@services.bunyip.com>; Sun, 2 Apr 1995 21:50:58 -0400
Received: from cheviot.ncl.ac.uk by mocha.bunyip.com with SMTP (5.65a/IDA-1.4.2b/CC-Guru-2b) id AA15351 (mail destined for iafa@services.bunyip.com) on Sun, 2 Apr 95 21:50:29 -0400
Received: from burnmoor.ncl.ac.uk by cheviot.ncl.ac.uk id <CAA14829@cheviot.ncl.ac.uk> (8.6.10/ for ncl.ac.uk) with SMTP; Mon, 3 Apr 1995 02:50:14 +0100
Received: from tuda.ncl.ac.uk (tuda.ncl.ac.uk [128.240.2.1]) by burnmoor.ncl.ac.uk (8.6.11/8.6.10-cf revision 2 for Solaris 2.x) with ESMTP id CAA00390; Mon, 3 Apr 1995 02:50:13 +0100
Received: from [199.92.189.240] (ietf-240.ietf.org [199.92.189.240]) by tuda.ncl.ac.uk (8.6.10/8.6.10-cf revision 1 for SunOS 4.1.x) with SMTP id CAA08028; Mon, 3 Apr 1995 02:50:09 +0100
Date: Mon, 3 Apr 1995 02:50:09 +0100
X-Sender: njf@burnmoor.ncl.ac.uk (Unverified)
Message-Id: <v02110108aba3a6a00860@[128.240.3.154]>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
To: iafa@bunyip.com
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Jill Foster <Jill.Foster@newcastle.ac.uk>
Subject: Re: IAFA templates: a user's comment
Cc: mrp@itd.adelaide.edu.au
X-Orig-Sender: owner-iafa@bunyip.com
Precedence: bulk

At 9:45 am 24/3/95, Martijn Koster wrote:
>Thomas Krichel wrote:
>
>>   Martijn Koster writes:
>>
>> ...
>>
>> > The variant part of the IAFA templates are a quick fix for a small
>> > domain of problems surrounding manifestations of a
>> > document. Personally I'd like to see it removed altogether, but it'll
>> > have to stay in for backward compatibility.

I've never liked the way variants are handled. It's ugly and not template
user (filler in) friendly. (I did say this right in the early stages years
ago.)

>
>Sure, ALIWEB also filters out bogus templates. But someone somewhere
>is writing the template, probably by hand, and probably without having
>read all $$ pages of the iafa draft. So it _has_ to be simple.

We're trying to base the TRAINMAT templates on the IAFA moving targets -
but have not really used the variants format. We want to - but have hedged
round it a little for practical reasons. (Difficult to provide a general
purpose template that could be filled in by a non-iafa guru without a user
manual.) Different versions/formats of a piece of network training material
should have only one template in order that people can find them as a group
and decide which suits them best and so that template maintainers don't
have to complete 50 templates for one resource (they just won't do it).

Mark Prior (Univ. Adelaide) has the catalogue on line and the template as a
form for people to complete. See below. This is a real life example using
resources that cover both electronic formats, paper published formats and
video. (It broke the original TopNode model.)

To access the document online you may use the World Wide Web at the
University of Adelaide (Australia)

  http://coolabah.itd.adelaide.edu.au/TrainMat/catalogue.html
  http://coolabah.itd.adelaide.edu.au/TrainMat/template.html

Comments welcome.

-- Jill