Thanks for the feedback, Sebastian.
I submitted an FR (3062922).
As to use cases (copied from FR):
Example use cases (from a processing application perspective):
. generate separate lists of maps, illustrations, etc.
. collect all //figure[@type='photograph'] and display in a gallery
. print-to-web conversion project: for each figure[@type='map'] as
encountered in the print edition, render a dynamic map (e.g. via Google
Maps API) instead of the printed map image
Is the last one of the above cases one of those that should go with an
@rend solution in your opinion?
Sebastian Rahtz wrote:
> On 9 Sep 2010, at 16:42, Markus Flatscher wrote:
>> Assuming I had an urge to distinguish between different kinds of
>> figures, e.g. between maps and illustrations, what would be the proper
>> way of encoding such a distinction, given that @type is not currently
>> allowed on <figure>? (Should it be?)
> Does seem like there is no way. My initial reaction that this is an oversight,
> and that it should be a member of att.declaring and/or att.typed. Maybe you'd
> like to enter a feature request, with some examples?
> though I confess I don't immediately see the use case. If the original
> presentation is different, you have @rend, of course.
> Sebastian Rahtz
> Information Manager, Oxford University Computing Services
> 13 Banbury Road, Oxford OX2 6NN. Phone +44 1865 283431
> Sólo le pido a Dios
> que el futuro no me sea indiferente
Markus Flatscher, Project Editor
ROTUNDA, The University of Virginia Press
PO Box 400314, Charlottesville VA 22904, USA
Courier: 211 Emmet Street South, Charlottesville VA 22903, USA
Email: [log in to unmask]