Re: [dita] Stage One Proposal: Change the specialization base of imagemap

[Chris Nitchie <chris.nitchie@oberontech.com>]

I don't have a strong opinion about <imagemap>; I just suggested moving it into core for the sake of flexibility, and having observed that <fig> isn't a great specialization base. If specializing from <div> instead makes the problems go away, I'm all for it.

I do think moving <sort-as> into core makes a lot of sense, but only if somebody else does the work :).

Chris

ïOn 7/9/19, 4:02 PM, "dita@lists.oasis-open.org on behalf of Kristen James Eberlein" <dita@lists.oasis-open.org on behalf of kris@eberleinconsulting.com> wrote:

    Agree about little used -- I think I've only included the utilities
    domain in document-type shells for a single client.

    Best,
    Kris

    Kristen James Eberlein
    Chair, OASIS DITA Technical Committee
    Principal consultant, Eberlein Consulting
    www.eberleinconsulting.com
    +1 919 622-1501; kriseberlein (skype)

    On 7/9/2019 3:55 PM, Eliot Kimber wrote:
    > My argument against putting imagemap in the base is that it is a little-used element and the actual design of it may not be ideal (one could think of other ways to associate linkable regions with images). Adding it to the base would add element types that few DITA users ever use a privilege a particular design where the current design is not privileged (because use of any domain is never mandatory).
    >
    > I also like the idea of simply allowing <title> within imagemap--that might be the simplest solution to meeting Zoe's original requirement.
    >
    > I think it's more appropriate as a standalone domain, even if it's a very simple one.
    >
    > I think it's easier to justify adding sort-as to the base since it's clearly a fundamental facility that some languages (Japanese, Traditional Chinese) must use for almost any lexical ordering situation and other languages often have need for.
    >
    > Cheers,
    >
    > E.
    > --
    > Eliot Kimber
    > http://contrext.com
    >
    >
    > On 7/9/19, 3:23 PM, "Kristen James Eberlein" <dita@lists.oasis-open.org on behalf of kris@eberleinconsulting.com> wrote:
    >
    >
    >
    >
    >
    >
    >          So we have two possibilities here:
    >
    >
    >      * Add <imagemap> and its child elements to base -- also
    >              <sort-as>
    >
    >
    >      * Change the specialization base for <imagemap> and area
    >              to <div>
    >
    >
    >          Which makes most sense?
    >
    >          Best,
    >            Kris
    >
    >            Kristen James Eberlein
    >            Chair, OASIS DITA Technical Committee
    >            Principal consultant, Eberlein Consulting
    >            www.eberleinconsulting.com <http://www.eberleinconsulting.com>
    >            +1 919 622-1501; kriseberlein (skype)
    >
    >
    >          On 7/9/2019 3:14 PM, Eliot Kimber
    >            wrote:
    >
    >
    >            [I sent this to Zoe yesterday but had intended to send to the main list]
    >
    >      <div> should be the best choice but would need to think it through:
    >
    >      <imagemap> allows <image> and <area>
    >
    >      <area> is currently a specialization of <figgroup>.
    >
    >      <figgroup> is essentially the semantic equivalent to <div> so it would make sense to also make <area> a specialization of <div>.
    >
    >      <div> allows all the elements from which the subelements of <area> are specialized, so that works.
    >
    >      One way to evaluate a specialization design is to generalize it back to the base types and verify that the result is still valid. If it is, then the specialization meets that requirement.
    >
    >      So using <div> for <imagemap> and <area> definitely passes that test.
    >
    >      Then the other question is whether or not the specialization is semantically consistent with the base, which is a more subjective question. But in this case, <div> has no semantic beyond "container" so hard not to be semantically consistent with it. Ditto for <area> specialized from <div>.
    >
    >      Cheers,
    >
    >      E.
    >
    >      --
    >      Eliot Kimber
    >      http://contrext.com
    >
    >
    >      On 7/8/19, 8:30 PM, "Zoe Lawson" <dita@lists.oasis-open.org on behalf of zoelawson17@hotmail.com> <mailto:dita@lists.oasis-open.orgonbehalfofzoelawson17@hotmail.com> wrote:
    >
    >
    >          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
    >
    >
    >
    >
    >
    >      ---------------------------------------------------------------------
    >      To unsubscribe from this mail list, you must leave the OASIS TC that
    >      generates this mail.  Follow this link to all your TCs in OASIS at:
    >      https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
    >
    >
    >
    >
    >
    >
    >
    >
    >
    >
    >      ---------------------------------------------------------------------
    >      To unsubscribe from this mail list, you must leave the OASIS TC that
    >      generates this mail.  Follow this link to all your TCs in OASIS at:
    >      https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
    >
    >
    >
    >
    >
    >
    > ---------------------------------------------------------------------
    > To unsubscribe from this mail list, you must leave the OASIS TC that
    > generates this mail.  Follow this link to all your TCs in OASIS at:
    > https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
    >
    >
    >
    >

    ---------------------------------------------------------------------
    To unsubscribe from this mail list, you must leave the OASIS TC that
    generates this mail.  Follow this link to all your TCs in OASIS at:
    https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php



The content of this email and any attached files are intended for the recipient specified in this message only. It may contain information that is confidential, proprietary, privileged, and/or exempt from disclosure under applicable law. It is strictly forbidden to share any part of this message with any third party or rely on any of its contents, without the written consent of the sender. If you received this message by mistake, please reply to this message and follow with deletion of the original message, any copies and all attachments, so that Oberon Technologies can ensure such a mistake does not occur in the future.