[rfc-i] draft-iab-xml2rfc-03, "B.2.1 Overlapping Values"

jhildebr at cisco.com (Joe Hildebrand (jhildebr)) Wed, 16 March 2016 19:52 UTC

From: jhildebr at cisco.com (Joe Hildebrand (jhildebr))
Date: Wed, 16 Mar 2016 19:52:01 +0000
Subject: [rfc-i] draft-iab-xml2rfc-03, "B.2.1 Overlapping Values"
In-Reply-To: <B2B8DB2A-614D-4C87-A819-929ADEC53FEC@cisco.com>
References: <56E7314B.3060408@gmx.de> <56E82BB5.1020202@gmx.de> <B2B8DB2A-614D-4C87-A819-929ADEC53FEC@cisco.com>
Message-ID: <DF980D0F-F352-4566-8287-665B4295195F@cisco.com>

On 3/15/16, 4:00 PM, "rfc-interest on behalf of Joe Hildebrand (jhildebr)" <rfc-interest-bounces at rfc-editor.org on behalf of jhildebr at cisco.com> wrote:



>Here are the places I see pn's in the current RNC:
>
>"""
>abstract
>note
>boilerplate (remove)
>section
>t
>aside
>blockquote
>ol
>ul
>li
>dl
>dt (remove?)
>dd (remove? Not in preptool)
>figure
>table
>artwork
>sourcecode
>thead (remove? Not in preptool)
>tbody (remove? Not in preptool)
>tfoot (remove? Not in preptool)
>tr (remove? Not in preptool)
>th (remove? Not in preptool)
>references
>"""

While we're on this topic, I don't think <ol>, <ul>, and <dl> should get @pn's.  I agree with Julian that they use up a part number in the list in a visually non-intuitive way.  Each of the list items (<li>, <dt>) getting a @pn makes sense to me; they look more-or-less like <t>'s in the section's flow.

-- 
Joe Hildebrand