Arguments for NOT using topics as parents to other topics in DITA-maps

[Martin Jonasson <martinjonassonjobbet -at- gmail -dot- com>]

Hi all,

I had an argument with an experienced developer/technical writer about
creating structures for topic based authoring/DITA.

He argued that you should never use a topics as a parent for another
topic in a structure. Always use a heading without content as a parent.
(topichead)

In DITA that would mean using "topichead" for headings and never place a
"topicref" as a child to another "topicref" in the Ditamap.

Exemple:
topichead "Alarms"
- topicref "Concept: Alarms overview"
- topicref "Fact: List of Alarms"

... is OK!

topicref "Concept: Alarms overview"
- topicref "Fact: List of Alarms"

... is NOT OK as topicref is child of topicref.

He argued that this is the proper way of using topic based authoring and
would make the information more clear and logic.

I've been working with DITA/other systems for a while and can't really see
his point here.

Can someone please clarify me on this? Is he making a valid point I can't
see? How important is his point if this is the case? Or is he plain wrong?

How many of you avoid topicrefs in topicrefs?

Any thoughts are highly appriciated!

//MJ


^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
New! Doc-to-Help 2013 features the industry's first HTML5 editor for authoring.

Learn more: http://bit.ly/ZeOZeQ

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot- 

To unsubscribe send a blank email to
techwr-l-leave -at- lists -dot- techwr-l -dot- com


Send administrative questions to admin -at- techwr-l -dot- com -dot-  Visit
http://www.techwhirl.com/email-discussion-groups/ for more resources and info.

Looking for articles on Technical Communications?  Head over to our online magazine at http://techwhirl.com

Looking for the archived Techwr-l email discussions?  Search our public email archives @ http://techwr-l.com/archives