[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Discussion item - do we still need itemgroup?
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âm curious what others think about this?