OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

dita message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: Stage One Proposal: Change the specialization base of imagemap


If the goal is to specialize the imagemap element from a different base element than fig,

<imagemap class="+ topic/fig ut-d/imagemap ">
   <image class="- topic/image " />
   <area class="+ topic/figgroup ut-d/area ">
    <shape class="+ topic/keyword ut-d/shape " />
    <coords class="+ topic/ph ut-d/coords " />
    <xref class="- topic/xref " />
   </area>
  </imagemap>

I think the difficulty is likely to be the area element child of imagemap.  The area element is specialized from figgroup; figgroup occurs only as a child of fig or figgroup.  (Or equation-figure, specialized from fig.)  It'd be difficult to specialize imagemap from another element without adding figgroup to that element's content model.

Because imagemap is specialized from fig, it could have its content model changed to include fig's optional title:

<imagemap class="+ topic/fig ut-d/imagemap ">
   <title class="- topic/title " />
   <image class="- topic/image " />
   <area class="+ topic/figgroup ut-d/area ">
    <shape class="+ topic/keyword ut-d/shape " />
    <coords class="+ topic/ph ut-d/coords " />
    <xref class="- topic/xref " />
   </area>
  </imagemap>

If you want specifically to allow:

<fig class="- topic/fig ">
  <title class="- topic/title " />
  <imagemap class="+ topic/fig ut-d/imagemap ">
   <image class="- topic/image " />
   <area class="+ topic/figgroup ut-d/area ">
    <shape class="+ topic/keyword ut-d/shape " />
    <coords class="+ topic/ph ut-d/coords " />
    <xref class="- topic/xref " />
   </area>
  </imagemap>
 </fig>

the simplest approach is to change the content model of the fig element to allow fig as a child, which would then logically permit imagemap and other specializations of fig as children of fig.

What the committee considers desirable I could not say.

Graydon Saunders | Publishing Solutions Developer | Precision Content 
Direct: +1
 (647)265-8500 x106Email: graydon@precisioncontent.com | www.precisioncontent.com

 


 

Unlock the Knowledge in Your Enterprise™


This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited. Please notify us by return email if you have received this email in error. ©2019, Precision Content Authoring Solutions Inc, Mississauga, Ontario, Canada


From: dita@lists.oasis-open.org <dita@lists.oasis-open.org> on behalf of Zoe Lawson <zoelawson17@hotmail.com>
Sent: 08 July 2019 20:30
To: DITA TC
Subject: [dita] Stage One Proposal: Change the specialization base of imagemap
 
Originally, <imagemap> was a specialization of <fig>. This means you cannot use an <imagemap> directly inside of a <fig>, which makes it complicated to add a title to your image.
You can work around this by using a <div> inside of the <fig>, but that seems like an extra layer of complexity.

If we change the specialization base of <imagemap> from <fig> to something slightly more generic such as <div>, that may simplify the adding of a title (or other content) around an <imagemap> in a <fig>.

I would like some technical assistance determining which element makes the most sense to specialize from.

Thanks,
Zoë Lawson


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]