[rfc-i] [IAB] draft-iab-xml2rfc-03, "B.2 Anchors and IDs"

[jhildebr at cisco.com (Joe Hildebrand (jhildebr))]

On 5/9/16, 5:06 AM, "IAB on behalf of Julian Reschke" <iab-bounces at iab.org on behalf of julian.reschke at gmx.de> wrote:



><https://greenbytes.de/tech/webdav/draft-iab-xml2rfc-03.html#rfc.section.B.2>
>
>"Authors can leave anchors in a document that can later be used for 
>references with the "anchor" attribute. Anchors can be included in the 
>following elements: <artwork>, <aside>, <blockquote>, <cref>, <figure>, 
><li>, <reference>, <referencegroup>, <section>, <sourcecode>, <t>, and 
><table>. The author can then refer to that anchor in the "target" 
>attribute of the <xref> element."
>
>This is inaccurate, as the grammar allows anchor attributes on more 
>elements, such as the child elements of <table>.
>
>In general, I'm +1 on allowing anchors for everything that creates a 
>well-defined anchor point in the document -- even when it might be 
>impossible to auto-create prose when xref'ing that point.

Agree.  I'm fine with the preptool throwing an error if it can't figure out text to generate.

>That said, there are many other elements that IMHO would need to allow 
>anchors as well: note, boilerplate, xref, relref, tt, strong, em, sub, 
>sup, spanx, and bcp14.

Can we add those in the bis version?

-- 
Joe Hildebrand