[rfc-i] [IAB] draft-iab-xml2rfc-latest, "2.46.2 "numbered" Attribute"

julian.reschke at gmx.de (Julian Reschke) Tue, 28 June 2016 21:19 UTC

From: julian.reschke at gmx.de (Julian Reschke)
Date: Tue, 28 Jun 2016 23:19:43 +0200
Subject: [rfc-i] [IAB] draft-iab-xml2rfc-latest, "2.46.2 "numbered" Attribute"
In-Reply-To: <7FC576F7-4B0B-48FA-9465-5D585991E5EE@cisco.com>
References: <72846c2a-3be8-be66-3105-d384c8377489@gmx.de> <7FC576F7-4B0B-48FA-9465-5D585991E5EE@cisco.com>
Message-ID: <90847558-888b-7fff-2535-ece814ea3e38@gmx.de>

On 2016-06-28 22:32, Joe Hildebrand (jhildebr) wrote:
>> On Jun 28, 2016, at 8:53 AM, Julian Reschke <julian.reschke at gmx.de> wrote:
>>
>> <https://greenbytes.de/tech/webdav/draft-iab-xml2rfc-04.html#rfc.section.2.46.2>:
>>
>> "If set to "false", the formatter is requested to not display a section number. The prep tool will verify that such a section is not followed by a numbered section in a part, and will verify that the section is a top-level section."
>>
>> Define this in terms what is allows, not in terms of what the preptool does:
>>
>> "A value of 'false' is only allowed on top-level sections that are not followed by any other numbered section".
>
> Do <references> elements count as sections?  They get numbers.
>
> If so, this means that only the last <section> elements in <back> may be un-numbered.

Yes.

(This wasn't meant to change the definition, but apparently it has 
uncovered something we need to discuss).