[jats-list] BITS suggestion: make nav-pointer/@rid implied

[Alexander Schwarzman <aschwarzman@xxxxxxxxx>]

It appears that BITS model for 'nav-pointer' attributes is overly
restrictive: it requires a @rid. In case when an existing
back-of-the-book index is being digitized, it seems unreasonable to
require the tagger to find the indexing term in the text and place an
@id on it to serve as the target of the @rid.

Thus, it seems to me that in tagging the existing indexes

<index-entry>
<term>Benefit relationship</term>
<nav-pointer rid="idx14" nav-pointer-type="point">233</nav-pointer>
</index-entry>

could do without @rid, i.e.,

<index-entry>
<term>Benefit relationship</term>
<nav-pointer nav-pointer-type="point">233</nav-pointer>
</index-entry>

If this is so, then:

<!--                    NAVIGATION POINTER ATTRIBUTES              -->
<!--                    Attributes for the <nav-pointer> element.  -->
<!ENTITY % nav-pointer-atts
            "id         ID                                #IMPLIED
             rid        IDREF                             #REQUIRED
             nav-pointer-type
                        (end-of-range | point |
                         start-of-range)                  #IMPLIED
             xml:lang   NMTOKEN                           #IMPLIED
             content-type
                        CDATA                             #IMPLIED
             specific-use
                        CDATA                             #IMPLIED"  >

from BITS-toc-index-nav0.ent would become:

<!--                    NAVIGATION POINTER ATTRIBUTES              -->
<!--                    Attributes for the <nav-pointer> element.  -->
<!ENTITY % nav-pointer-atts
            "id         ID                                #IMPLIED
             rid        IDREF                             #IMPLIED
             nav-pointer-type
                        (end-of-range | point |
                         start-of-range)                  #IMPLIED
             xml:lang   NMTOKEN                           #IMPLIED
             content-type
                        CDATA                             #IMPLIED
             specific-use
                        CDATA                             #IMPLIED"  >


Also, Example 2 for <see-entry> in the BITS Tag Library is identical
to Example 1. Example 2 is supposed to contain page numbers but it
does not.

Finally, it might be helpful if the Tag Library contained examples of
using @id on 'index-entry and @rid on 'see-entry' and 'see-also-entry'
in case one wants to effect a link to a preferred or a related term.

Thank you,

Alexander ('Sasha') Schwarzman
Content Technology Architect
OSA - The Optical Society
2010 Massachusetts Ave., NW
Washington, DC 20036  USA
Direct: +1.202.416.1979
Email: aschwarzman@xxxxxxx
http://www.osa.org