X-VM-v5-Data: ([nil nil nil nil nil nil nil nil nil]
	["1737" "Wed" "11" "June" "1997" "13:52:36" "+0100" "Sebastian Rahtz" "s.rahtz@ELSEVIER.CO.UK" nil "41" "Re: automatic numbering" "^Date:" nil nil "6" 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.5/8.8.4) with ESMTP
	  id KAA20960; Thu, 12 Jun 1997 10:19:14 +0200 (MET DST)
Received: from lsv1.listserv.gmd.de by listserv.gmd.de (LSMTP for OpenVMS v1.1a) with SMTP id <3.88BFB40D@listserv.gmd.de>; Thu, 12 Jun 1997 9:50:33 +0200
Received: from RELAY.URZ.UNI-HEIDELBERG.DE by RELAY.URZ.UNI-HEIDELBERG.DE
          (LISTSERV-TCP/IP release 1.8b) with spool id 151444 for
          LATEX-L@RELAY.URZ.UNI-HEIDELBERG.DE; Wed, 11 Jun 1997 14:53:07 +0200
Received: from pillar.elsevier.co.uk (root@pillar.elsevier.co.uk
          [193.131.222.35]) by relay.urz.uni-heidelberg.de (8.7.6/8.7.4) with
          ESMTP id OAA21885 for <LATEX-L@RELAY.URZ.UNI-HEIDELBERG.DE>; Wed, 11
          Jun 1997 14:53:05 +0200 (MET DST)
Received: from snowdon.elsevier.co.uk (snowdon.elsevier.co.uk
          [193.131.197.164]) by pillar.elsevier.co.uk (8.8.5/8.8.5) with ESMTP
          id NAA19162 for <LATEX-L@RELAY.URZ.UNI-HEIDELBERG.DE>; Wed, 11 Jun
          1997 13:49:23 +0100 (BST)
Received: from cadair.elsevier.co.uk by snowdon.elsevier.co.uk with SMTP (PP);
          Wed, 11 Jun 1997 13:52:48 +0100
Received: from lochnagarn.elsevier.co.uk (lochnagarn.elsevier.co.uk
          [193.131.216.1]) by cadair.elsevier.co.uk (8.8.5/8.8.5) with ESMTP id
          NAA12824 for <LATEX-L@RELAY.URZ.UNI-HEIDELBERG.DE>; Wed, 11 Jun 1997
          13:52:40 +0100 (BST)
Received: (from srahtz@localhost) by lochnagarn.elsevier.co.uk (8.8.5/8.8.5) id
          NAA29103; Wed, 11 Jun 1997 13:52:36 +0100 (BST)
References: <pc910inkm2.fsf@epsilon.ams.org>
            <199706110929.KAA19914@lochnagarn.elsevier.co.uk>
            <pcafkxs4yp.fsf@epsilon.ams.org>
Message-ID:  <199706111252.NAA29103@lochnagarn.elsevier.co.uk>
Reply-To: Mailing list for the LaTeX3 project
              <LATEX-L@RELAY.URZ.UNI-HEIDELBERG.DE>
In-Reply-To:  <pcafkxs4yp.fsf@epsilon.ams.org>
Date:         Wed, 11 Jun 1997 13:52:36 +0100
From: Sebastian Rahtz <s.rahtz@ELSEVIER.CO.UK>
Sender: Mailing list for the LaTeX3 project
              <LATEX-L@RELAY.URZ.UNI-HEIDELBERG.DE>
To: Multiple recipients of list LATEX-L
              <LATEX-L@RELAY.URZ.UNI-HEIDELBERG.DE>
Subject:      Re: automatic numbering
Status: R
X-Status: 
X-Keywords:                  
X-UID: 2023

Michael John Downes writes:
 > Only if you believe that element numbers are not data. It is not SGML
 > that dictates the numbers cannot be data, it is your DTD. There seems to
well, true

 > true in many cases, but the kind of material in which it is true least
 > often is mathematical material, which happens to be the stuff that my
 > employer specializes in---hence my colored view of the situation.

fair point. but i would argue you are an unusual situation, and the
SGML world seems to be against you

 > In any case if explicit numbers were added to LaTeX 3 documents I don't
 > see that it would impair your current approach any. Just have your
if you have a clear notation, yes, its true we can all win.

 <section3><suggested-rendition>1.2.5</suggested-rendition>
  <st>The results<st>
 ..
 </section3>

 > Actually a full number spec should include both value and formatting,
 > separated, for maximum flexibility. I have some prototypes lying around
i should have guessed

 > ---A mathematician who chooses to number list items with Greek
 > letters will find a change to standard numbering by the publisher
 > unpalatable; it destroys the nuances of the original.
in the fascist world I live in, the author would not _have_ this
freedom, they get lists or no lists....

 > ---In a mathematical document where \bullet or \square is used as a math
 > symbol the author will naturally tend to shun the use of the same symbol
 > for itemized lists. Putting the document through a publishing process
 > that ignores this constraint might be a significant disservice to

i'd call that journal style. a mathematical publication might well
implement <itemize> with symbols unlikely to get confused with typical
content

Sebastian