Re: [dita-lightweight-dita] Full DITA compatibility

[Joe Pairman <joe.pairman@mekon.com>]

I'd add to that — <section> in DITA isn't intended to be a nestable, navigable unit as many people would assume from the name "section". It's not nestable and in the default processing, section titles aren't displayed in navigation. It's really intended for specialized containers *within* a unit of navigation, such as the examples that Mark gave.

It might sound odd, but if users want arbitrarily nestable, navigable units that are contained in a single storage object, nested topics are a better fit. More on this from conversations on DITA-Users regarding Jarno's Markdown DITA plugin:

https://groups.yahoo.com/neo/groups/dita-users/conversations/messages/36903

https://groups.yahoo.com/neo/groups/dita-users/conversations/messages/36928

So I'd suggest that, if possible, we steer clear of using non-specialized sections for arbitrary titled chunks in Lightweight DITA.

Just my 2p.

Joe
________________________________________
From: dita-lightweight-dita@lists.oasis-open.org <dita-lightweight-dita@lists.oasis-open.org> on behalf of Mark Poston <mark.poston@mekon.com>
Sent: Monday, May 11, 2015 9:12 AM
To: Noz Urbina; Michael Priestley
Cc: Fredrik Geers; dita-lightweight-dita@lists.oasis-open.org
Subject: Re: [dita-lightweight-dita] Full DITA compatibility

Not sure I agree with that statement. Sections are also very useful to break content up into more semantic groupings that do not necessarily need a title. A title might be implied by the name of the specialised tag, and not actually require the title element itself. It is then down to the delivery stylesheet to decide whether a title is displayed or not.

<prereq>, <context> etc. in a task are examples of this.



On 11/05/2015 08:20, "Noz Urbina" <noz.urbina@urbinaconsulting.com> wrote:

>The entire point of a section would be to have a heading.