Re: IAFA templates: a user's comment

Martijn Koster <m.koster@nexor.co.uk> Mon, 03 April 1995 08:42 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa00819; 3 Apr 95 4:42 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa00815; 3 Apr 95 4:42 EDT
Received: from services.Bunyip.COM by CNRI.Reston.VA.US id aa01526; 3 Apr 95 4:42 EDT
Received: (from daemon@localhost) by services.bunyip.com (8.6.10/8.6.9) id EAA28419 for iafa-out; Mon, 3 Apr 1995 04:42:58 -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 EAA28414 for <iafa@services.bunyip.com>; Mon, 3 Apr 1995 04:42:50 -0400
Received: from lancaster.nexor.co.uk by mocha.bunyip.com with SMTP (5.65a/IDA-1.4.2b/CC-Guru-2b) id AA16812 (mail destined for iafa@services.bunyip.com) on Mon, 3 Apr 95 04:42:40 -0400
Message-Id: <9504030842.AA16812@mocha.bunyip.com>
Received: from nexor.co.uk (actually host victor.nexor.co.uk) by lancaster.nexor.co.uk with SMTP (PP); Mon, 3 Apr 1995 09:41:37 +0100
To: Jill Foster <Jill.Foster@newcastle.ac.uk>
Cc: iafa@bunyip.com, mrp@itd.adelaide.edu.au
Subject: Re: IAFA templates: a user's comment
In-Reply-To: Your message of "Mon, 03 Apr 1995 02:50:09 BST." <v02110108aba3a6a00860@[128.240.3.154]>
Date: Mon, 03 Apr 1995 09:41:02 +0100
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Martijn Koster <m.koster@nexor.co.uk>
X-Orig-Sender: owner-iafa@bunyip.com
Precedence: bulk

In message <v02110108aba3a6a00860@[128.240.3.154]>;, Jill Foster writes:

> 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.)

So lets see: Jill Foster think's it's ugly, I think they're gross,
Alan doesn't care for them, and the IESG doens't like them either. I
have said in the past we should probably keep them because of the
legacy, but after all this *is* a draft. Sounds to me like they need
to go, or at the very least marked as deprecated.

>We're trying to base the TRAINMAT templates on the IAFA moving targets -

:-) If it's easier/better I'd prefer to freeze a trimmed-down version
NOW and then argue about additions later...

>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.)

Yes, and that's v. bad.

> 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).

So would you say it's more important to have the one description
pointing to "somewhere" where all these files are, than explicit
mapping between variants and locations?

-- Martijn
__________
Internet: m.koster@nexor.co.uk
X-400: C=GB; A= ; P=Nexor; O=Nexor; S=koster; I=M
WWW: http://web.nexor.co.uk/mak/mak.html