@martindholmes and I have found that the Stylesheets do not always output the values of a valList when included by specList/specDesc. To us, it seems like semi valLists, when included by specDesc, do produce a list of suggested values in the documeentation; closed valLists do not.
For instance, this part of CO.xml embeds documentation for att.placement:
The <gi>rt</gi> element is a member of <ident type="class">att.placement</ident>, and thus the
<att>place</att> attribute may be used to indicate where the
ruby gloss is with respect to the base text:
<specList>
<specDesc key="att.placement" atts="place"/>
</specList>
Which produces something like (note the "Suggest values include" sentence)
The rt element is a member of att.placement, and thus the place attribute may be used to indicate where the ruby gloss is with respect to the base text:
att.placement provides attributes for describing where on the source page or object a textual element appears.
place specifies where this item is placed. Suggested values include: 1] top; 2] bottom; 3] margin; 4] opposite; 5] overleaf; 6] above; 7] right; 8] below; 9] left; 10] end; 11] inline; 12] inspace
However, this specList:
<p>To overcome these problems, the following additional attributes are
defined for all elements in the <ident type="class">att.divLike</ident> class:
<specList><specDesc key="att.divLike" atts="org sample"/>
<specDesc key="att.fragmentable" atts="part"/>
</specList>
</p>
produces this (which does not include the phrase "Legal values include", which, according to common_tagdocs.xsl should):
To overcome these problems, the following additional attributes are defined for all elements in the att.divLike class:
att.divLike provides attributes common to all elements which behave in the same way as divisions.
org (organization) specifies how the content of the division is organized.
sample indicates whether this division is a sample of the original source and if so, from which part.
att.fragmentable provides attributes for representing fragmentation of a structural element, typically as a consequence of some overlapping hierarchy.
part specifies whether or not its parent element is fragmented in some way, typically by some other overlapping structure: for example a speech which is divided between two or more verse stanzas, a paragraph which is split across a page division, a verse line which is divided between two speakers.
@martindholmes and I have found that the Stylesheets do not always output the values of a valList when included by specList/specDesc. To us, it seems like semi valLists, when included by specDesc, do produce a list of suggested values in the documeentation; closed valLists do not.
For instance, this part of CO.xml embeds documentation for att.placement:
Which produces something like (note the "Suggest values include" sentence)
However, this specList:
produces this (which does not include the phrase "Legal values include", which, according to
common_tagdocs.xslshould):