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

[julian.reschke at gmx.de (Julian Reschke)]

On 2016-03-15 22:38, Joe Hildebrand (jhildebr) wrote:
> On 3/14/16, 3:46 PM, "IAB on behalf of Julian Reschke" <iab-bounces at iab.org on behalf of julian.reschke at gmx.de> wrote:
>
>
>
>> a) What is "pn" for a section that is unnumbered? I assume numbers are
>> still assigned, just not displayed?
>
> Yes.  Note that unnumbered sections can't have numbered sections that follow them.  Paragraphs in unnumbered sections still get pilcrows that are numbered as if the section had been numbered.
>
>> b) Don't we need "pn" on <references> (as they get numbered as regular
>> sections)?
>
> Yes.  I think Paul just added that.  This relates to our conversation last week.  I still think it might be nice to add a <referencesection> element to contain multiple <references>, which the preptool would add when needed.  <referencesection> would get the pn of the next top-level section (e.g s-4), and each <references> would be numbered as if it was a child section (e.g. s-4.1).  If there is only one <references>, it gets a top-level number.  I think this would be nice so that each output formatter doesn't have to make a separate decision about whether to gin up a top-level section or not.
>
> I think where we might have ended up last week was to just add the pn to <references>, and keep the output formatters more error-prone.  I can live with that, if that's what everyone else wants.

Right. FWIW, I have the following logic in my preptool-to-be:

>     <xsl:when test="self::references">
>       <xsl:text>s-</xsl:text>
>       <xsl:value-of select="1 + count(../../middle/section)"/>
>       <xsl:if test="count(../references)!=1">
>         <xsl:text>.</xsl:text>
>         <xsl:value-of select="1 + count(preceding-sibling::references)"/>
>       </xsl:if>
>     </xsl:when>

It's not that hard to get right.

>> c) Why is "pn" for <boilerplate> numbered when it can only occur once?
>
> Ah, you're right, that text in preptool is confusing.  The <boilerplate> itself shouldn't get a pn, but the sections therein should have pn's of s-boilerplate-1 and s-boilerplate-2, with all of their subsections and parts being numbered accordingly.

According to the vocabulary spec, there is a "pn" attribute on boilerplate:

<http://greenbytes.de/tech/webdav/draft-iab-xml2rfc-03.html#grammar.boilerplate>:

> boilerplate =
>   element boilerplate {
>     attribute xml:base { text }?,
>     attribute xml:lang { text }?,
>     attribute pn { text }?,
>     section+
>   }

(Yeah for anchors in artwork, btw :-)

Best regards, Julian