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: [dita] Discussion item - do we still need itemgroup?

Based on Robert's analysis, I can't see any reason to maintain itemgroup except possibly as a specialization of <div>.



Eliot Kimber

ïOn 10/19/20, 10:21 AM, "Robert Anderson" <dita@lists.oasis-open.org on behalf of robert.dan.anderson@oracle.com> wrote:

    The <itemgroup> element has been around since the beginning of DITA. Itâs the basis for most of the elements inside of a task step (like stepxmp, tutorialinfo, etc). In the specification, weâve always defined it in the âspecialization elementsâ section â itâs intended for cases like the task step, where you want to subdivide a list. A special container was used because we needed exactly that container for task steps, and because at the time we didnât want to have an arbitrary âdivâ container available everywhere. Since DITA 1.0, that <itemgroup> element has been available exclusively in list items and in <dd> elements.

    In DITA 1.3 we added the <div> element. In the base vocabulary, itâs available anywhere that itemgroup can go. It has exactly the same content model, exactly the same set of attributes, and itâs ideal for specializations.

    I was editing the <itemgroup> element reference topic this weekend and found it hard to come up with an example â I kept coming back to âWhy wouldnât I do this with <div>?â

    Which got me wondering â is <itemgroup> needed anymore? What would we lose if we got rid of it?

    * I think everyone expects <div> to have formatting like it does in HTML (itâs a block). Iâve never been clear on formatting for <itemgroup>, and Iâve seen it formatted as both inline and as a block. So, for those who choose to format itemgroup as inline, they might end up with blocks.
    * In theory, you can create a domain specialization of itemgroup and it only shows up within list items + DD. That would require a lot of constraints if you used <div>. Iâve never had any reason to do this, and it seems unlikely to me.
    * The task specialization would require a change to @class values to base elements off of div. Because itemgroup and div have the same content models, everything else remains valid (no migration of source).
    * Anyone who has specialized list items as weâve done in task would have to make the same update, but it should be similarly simple.

    Iâm curious what others think about this?


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