The attribute @rend is not controlled in any way, and is globally available as in standard TEI. We agreed to remove it, since the rendition of an element is not our focus. However, rendition in the original may be useful in some cases when transforming generic highlighted passages in a level 0 text to use a more semantically precise tag such as emph or foreign, if the original is consistent in using (say) bold for the former and italic for the latter. My experience however suggests that Gutenberg texts (at least) are very inconsistent in their use of @rend values, sometimes even within the same text.
Should we simply disallow @rend? Or retain it only on <hi> and <milestone> ? I assume that trying to define any closed set of values for the attribute would be a non starter.
I have a (slight) preference for allowing @rend only on <hi> and milestone.
The attribute @rend is not controlled in any way, and is globally available as in standard TEI. We agreed to remove it, since the rendition of an element is not our focus. However, rendition in the original may be useful in some cases when transforming generic highlighted passages in a level 0 text to use a more semantically precise tag such as emph or foreign, if the original is consistent in using (say) bold for the former and italic for the latter. My experience however suggests that Gutenberg texts (at least) are very inconsistent in their use of @rend values, sometimes even within the same text.
Should we simply disallow @rend? Or retain it only on
<hi>
and<milestone>
? I assume that trying to define any closed set of values for the attribute would be a non starter.I have a (slight) preference for allowing @rend only on
<hi>
and milestone.