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' <david@davidartman.com>
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 <david@davidartman.com>
Sent: Tuesday, May 24, 2022 5:46 PM
To: kris eberleinconsulting.com <kris@eberleinconsulting.com>
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.
-------- Original message --------
From: "kris eberleinconsulting.com" <kris@eberleinconsulting.com>
Date: 5/24/22 16:23 (GMT-05:00)
To: Stefan Eike <Stefan.Eike@dometic.com>,
dita-comment@lists.oasis-open.org
Subject: [dita-comment] RE: Please implement a figure legend to the next DITA release
Hi, Stefan.
The DITA TC met today and discussed your request. We decided to add it as a potential item for the DITA 2.1 release.
When we reach the point of working on DITA 2.1, weâll probably reach back out to you for greater clarity about the use cases.
Best,
Kris
From: Stefan Eike <Stefan.Eike@dometic.com>
Sent: Friday, May 20, 2022 4:35 AM
To: dita-comment@lists.oasis-open.org
Subject: [dita-comment] Please implement a figure legend to the next DITA release
Hello DITA Committee,
Iâd like to suggest adding a semantical structure for an illustration legend in DITA, see image below. This is quite generic but missing in DITA. IMHO this should be a child of
<fig> and/or a stand-alone block element with the possibility to link to a
<fig> element.
Thank you very much for working on the DITA standard.
👍
Stefan Eike
Head of Technical Documentation
Phone +49 (0)2572 879 279 Cell +49 (0) 172 8843770
Stefan.Eike@dometic.com
Dometic Germany Holding GmbH â BetriebsstÃtte Emsdetten, Hollefeldstr. 63, 48282 Emsdetten Germany
NOTICE: This email and any attachments are for the sole use of the intended recipient(s) and may contain confidential information. Any unauthorized review, use, disclosure or distribution
is prohibited. If you are not the intended recipient, please notify the sender by reply email and destroy the original message.