Closed TEITechnicalCouncil closed 9 years ago
This issue was originally assigned to SF user: louburnard Current user is: lb42
I am biased as Markus and I are working on the same project, but there is a strong use case for typing <figure> as there are various ways (even in traditional publishing) that taxonomies of figures are used.
Original comment by: @DavidSewell
This seems eminently sensible. Added figure to att.typed. The text in #FTGRA should be updated to include some of your nice examples.
Original comment by: @lb42
Original comment by: @lb42
It would be good to have a way of typing <figure>s.
Examples:
<figure type="map"> <head>Back Bay West</head> <graphic url="boston-bbw.png"/> </figure>
<figure type="photograph"> <head>The Country Club, Brookline, 1882</head> <p>America's earliest country recreational and social club. The core of the clubhouse was built in 1802 […]</p> </figure>
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 imageNote: if <figure> were to be a member of att.typed, there would be obvious uses of
@subtype
as well. Consider:<figure type="map" subtype="political"/> <figure type="map" subtype="orthophoto"/> <figure type="map" subtype="road"/>
These may have to be rendered using different applications and/or data sources depending on
@subtype
.Possibly related: FR 1274137
Original comment by: @mflatscher