I think it would be useful if the html:tr which contain an attribute on the Guidelines reference pages have an @id of the name of the attribute. If this would the case one could point to, say, the @rend attribute by saying:
Yes indeed. +1 from me. Except that we should be using id="tei_rend", I think, shouldn't we? And if we're going down this road, we should probably distinguish attributes from elements that might be id'ed in the same way, so I suggest:
I, of course, agree with my suggestion and also generally like Martin's addition. However.....
I worry if these are tei_att.rend that this might get confused with class names, etc.
What about tei_CLASS-OR-ELEMENT-NAME-attribute... so in the case of @rend it would be:
Some from library backgrounds do argue that IDs shouldn't be humanly dereferenceable but I think it makes sense in this case.
This was assigned to James and me in the aftermath of the Ann Arbor meeting, and I've just had a first shot at it in rev 10655. It builds OK locally and seems to have no bad side effects, but I'll leave the ticket open until the Jinkses have built everything successfully.
I've created ids along the lines of tei_att.rend and tei_att.xml-id, not including JC's suggestion of class or element name, because I don't see that we're going to get any collisions, and in any case it's not easy to determine the class or element name from the context in which the template runs, AFAICS. What happens with e.g. @xml:id or @xml:lang? So I've kept it simple for now.
Closing this ticket. JC might choose to re-open if he wants to have a go at adding the class and/or element information to the id.
Sign up for the SourceForge newsletter:
You seem to have CSS turned off.
Please don't fill out this field.