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] Groups - DITA Proposed Feature #12021: Nesting sections (12021.html) uploaded

Hi Paul

The biggest difference is that the bodydiv/sectiondiv elements act more
like "informal" containers rather than "formal" (titled) blocks like

One concern raised was that if section was made recursive, it might lead
authors to believe that they could create embedded, nested content that
would be better managed as topics.  

The following posts on the mailing list provide some additional


The biggest advantage I see is that it provides badly needed structure
for specializations that do rely on nested content (I keep going back to
S1000D and ATA as examples since I have had to deal with these recently,
but there are certainly others).  The other advantage that I see is that
these elements provide a logical container for blocks of content that
could potentially be conref'ed elsewhere.  To me, this compliments the
conref range proposal and offers users the ability to structure and
reuse information without needing a heavyweight container like a topic.

Given the suggested content models, there wouldn't be any limitation for
specializations to create their own version of recursive "formal"
blocks, similar to the current DITA section. By doing this, there is the
potential that information that would be better managed as standard
topics could get lost within embedded, nested sections within a topic. 

Hope that helps.


Jim Earley
XML Architect/Consultant
Flatirons Solutions
4747 Table Mesa Drive
Boulder, CO 80301

Voice: 303.542.2156
Fax:   303.544.0522
Cell:  303.898.7193

Yahoo.IM: jmearley
MSN.IM: jearley22@hotmail.com

-----Original Message-----
From: Grosso, Paul [mailto:pgrosso@ptc.com] 
Sent: Tuesday, October 30, 2007 7:13 AM
To: dita@lists.oasis-open.org
Subject: RE: [dita] Groups - DITA Proposed Feature #12021: Nesting
sections (12021.html) uploaded

I was a little surprised to see this suggesting a bodydiv/sectiondiv
element but still not allowing sections to nest, which is what I
thought was meant by nesting sections.

I thought one of the drivers of this requirement was to be able
to model DocBook's nested sections more easily, but with the
suggested model, this would be even harder.

What are the benefits of this suggested model over simply allowing
section to contain section?


> -----Original Message-----
> From: jim.earley@flatironssolutions.com 
> [mailto:jim.earley@flatironssolutions.com] 
> Sent: Tuesday, 2007 October 30 7:15
> To: dita@lists.oasis-open.org
> Subject: [dita] Groups - DITA Proposed Feature #12021: 
> Nesting sections (12021.html) uploaded
> This is the HTML version of proposal 12021
>  -- Mr. Jim Earley
> The document named DITA Proposed Feature #12021:  Nesting sections
> (12021.html) has been submitted by Mr. Jim Earley to the OASIS Darwin
> Information Typing Architecture (DITA) TC document repository.
> Document Description:
> View Document Details:
> http://www.oasis-open.org/apps/org/workgroup/dita/document.php
> ?document_id=25904
> Download Document:  
> http://www.oasis-open.org/apps/org/workgroup/dita/download.php
> /25904/12021.html

To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail.  You may a link to this group and all your TCs in

FN:Jim Earley
ORG:Flatirons Solutions
TITLE:XML Developer/Consultant
ADR;WORK:;;4747 Table Mesa Rd, Suite 200;Boulder;CO;80305;United States of America
LABEL;WORK;ENCODING=QUOTED-PRINTABLE:4747 Table Mesa Rd, Suite 200=0D=0ABoulder, CO 80305=0D=0AUnited States of A=

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