[rfc-i] draft-iab-html-rfc-02: references

jhildebr at cisco.com (Joe Hildebrand (jhildebr)) Tue, 01 March 2016 17:47 UTC

From: jhildebr at cisco.com (Joe Hildebrand (jhildebr))
Date: Tue, 1 Mar 2016 17:47:47 +0000
Subject: [rfc-i] draft-iab-html-rfc-02: references
In-Reply-To: <56D5D0B0.9040105@gmx.de>
References: <56D16672.4000708@gmx.de> <0EB37407-B7F1-4022-9822-6D5720D45B8C@vpnc.org> <56D1CFD8.2090909@gmx.de> <017E4EA1-75C5-4891-AC5C-D5ABD845A1D3@vpnc.org> <56D1D4C4.1090007@gmx.de> <64E8088C-4B3B-4445-B3DF-C673579EEE14@cisco.com> <0E1902D3-A929-40D3-BEF7-2064D9F5A6A5@cisco.com> <BF9113FB-DE8C-4EFC-8B74-571B8C22FACC@cisco.com> <56D52F2E.3000003@gmx.de> <29116D5B-9576-4CD2-B2F3-F272F6F032FE@cisco.com> <56D5D0B0.9040105@gmx.de>
Message-ID: <C7E9463C-0355-48FB-9DB0-8BA08975D803@cisco.com>

On 3/1/16, 10:26 AM, "Julian Reschke" <julian.reschke at gmx.de> wrote:



>If I understand your proposal correctly you propose that the old format 
>continues to be ok, 

Yes.

>but there'll be another way of doing things, that'll 
>be output by the preptool, 

Only if there is more than one <references> section.

>and that any formatter will have to 
>understand. That makes things worse (IMHO), because there are now *two* 
>ways to achieve the same thing -- you can't fix a complexity problem by 
>adding more complexity.

I'm open to a less-complex solution that has the property that ALL of the decisions on section numbering are made by the prep tool. Right now, the prep tool makes 90% of the decisions.

For example, I could imagine just putting a pn attribute on <references>, and telling the output formatters that if there is more than one <references>, they can compute the section number of the containing section by dropping the .1 from the first references/@pn.  That's at least a plain syntactic manipulation, which has been our standard to this point.

-- 
Joe Hildebrand