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

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

<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.

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.

Best regards, Julian