X-VM-v5-Data: ([nil nil nil nil nil nil nil nil nil] ["2283" "Mon" "9" "November" "1998" "16:14:26" "+0000" "Robin Fairbairns" "Robin.Fairbairns@CL.CAM.AC.UK" nil "54" "Re: ISO LaTeX" "^Date:" nil nil "11" nil nil nil nil nil] nil) Received: from listserv.gmd.de (listserv.gmd.de [192.88.97.1]) by mail.Uni-Mainz.DE (8.8.8/8.8.8) with ESMTP id RAA28893; Mon, 9 Nov 1998 17:14:37 +0100 (MET) Received: from lsv1.listserv.gmd.de (192.88.97.2) by listserv.gmd.de (LSMTP for OpenVMS v1.1a) with SMTP id <15.E3D5AB0A@listserv.gmd.de>; Mon, 9 Nov 1998 17:14:36 +0100 Received: from RELAY.URZ.UNI-HEIDELBERG.DE by RELAY.URZ.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8b) with spool id 408279 for LATEX-L@RELAY.URZ.UNI-HEIDELBERG.DE; Mon, 9 Nov 1998 17:14:32 +0100 Received: from heaton.cl.cam.ac.uk (exim@heaton.cl.cam.ac.uk [128.232.32.11]) by relay.urz.uni-heidelberg.de (8.8.8/8.8.8) with SMTP id RAA18086 for ; Mon, 9 Nov 1998 17:14:30 +0100 (MET) Received: from dorceus.cl.cam.ac.uk (cl.cam.ac.uk) [128.232.1.34] (rf) by heaton.cl.cam.ac.uk with esmtp (Exim 1.82 #1) id 0zctxV-00000Z-00; Mon, 9 Nov 1998 16:14:29 +0000 Message-ID: Reply-To: Mailing list for the LaTeX3 project In-Reply-To: Your message of "Mon, 09 Nov 1998 15:42:18 GMT." <13895.3418.375000.233026@SRAHTZ> Date: Mon, 9 Nov 1998 16:14:26 +0000 From: Robin Fairbairns Sender: Mailing list for the LaTeX3 project To: Multiple recipients of list LATEX-L Subject: Re: ISO LaTeX Status: R X-Status: X-Keywords: X-UID: 2796 sebastian writes: > Hans Aberg writes: > > The idea of an ISO LaTeX is in fact not very good because the standard must > > be charged to pay for the salaries of the ISO bureaucrats. It means that the _real_ work that iso cs does (and for which you pay) is the diplomacy and the maintenance of standards in drafting. one regularly gets comments from keith brannon in ittf on standards whose technical content he knows absolutely nothing about -- what he's highlighting is sloppy drafting that has left ambiguities in the standard. however, the difficulty finding a credible and useful committee to standardise latex would kill the enterprise stone dead before it even started. i would recommend not even thinking about standardising latex. > this is true, but not universal (see DSSSL). still, ISO standards are > a good thing, because they have *some* credibility for independence, > editing, and longevity. I'd rather have an ISO standard than a W3C > one, since > > + the membership of W3C entirely depends on companies buying their > way in i sit on bsi committees because people pay for uk academics to do that. you have to buy your way in to earn the right to `give' them your expertise... > + the membership is largely US-based ime, the americans shout loudest in iso, so their theoretical numerical minority is not so significant. (also, their national procedures make them really difficult to negotiate with...) > + their standards of writing and editing are lax > + they change the things as it suits them these two are the real problem with non-traditional `standards'. > + would _you_ trust people with hair that long :-} there are plenty of long-haired people on iso working groups (the things that write standards). there are even some very long-haired people in suits at the political levels. the real problem with iso standardisation process is the tendency to reject things for irrational reasons. hence the new jtc1/sc3? to redo all the work the w3c has already done on xml/xsl. we (jtc1/sc24) have already knocked the w3c's png standard into shape, but for some reason the x*l work isn't thought `good enough'; by the time sc3? has done anything, the world will have moved on way beyond the point where they could have any influence. r