dita — archive

More feedback about adding a figure legend

From: Kristen Eberlein <[email protected]>
To: [email protected]
Date: Tue, 24 May 2022 22:58:00 -0000

Passing this along so that I can add a link to this to GitHub issue. Kris From: kris eberleinconsulting.com Sent: Tuesday, May 24, 2022 6:56 PM To: 'david davidartman.com' <[email protected]> Subject: RE: [dita-comment] RE: Please implement a figure legend to the next DITA release Thanks for sending this to me. I will pass it on to the TC, so it can be considered when we start talking about DITA 2.1. My sense is that what you outline is too elaborate for base DITA and more appropriate for a specialization, but your focus on parts catalog will give us quite a few things to consider. (No one mentioned parts catalogs when we talked over Stefan s e-mail at today s TC call. Best, Kris From: david davidartman.com < [email protected] > Sent: Tuesday, May 24, 2022 5:46 PM To: kris eberleinconsulting.com < [email protected] > Subject: RE: [dita-comment] RE: Please implement a figure legend to the next DITA release I didn't want to overstep and turn the comment mailing list into a discussion, so I'm emailing you, ok? I think the idea of a 'callouts' child element of fig could be useful, especially for efficient reuse. I'd like to suggest a few ideas for children of callouts (container) / callout (element) : label - required, @type=alpha num [for localization or style standard shifts], @headerstring (which defines that column's table header) description - required, same as p, possibly multiple blocks allowed, @headerstring quantity - optional, numeric, @headerstring ident - optional, alphanumeric+some symbols, @headerstring [part number] pc - optional, alphanumeric+some symbols, @headerstring [internal / universal product code] img - optional, href, @headerstring [image of just the item itself] bc - optional, href, @headerstring [QR or other scannable bar code] material - optional, alphanumeric+some symbols, @headerstring [materials(s)] __ I could possibly think of a few others, given time to peruse specialty parts catalogs; but these seem a strong set of starting children that could be extended with specialization. Might even be use cases for hazard statement children of a callouts/callout element...? I hope this helps and isn't too presumptuous! David Artman DCA:d.a.d.