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] Question about <navtitle> in <topicgroup> allowed by DITA 1.2

The title was added as a by-product of the requirement to make @navtitle
into an element - we added it into <topicmeta>, which meant that there was
no way to exclude it from the topicgroup context. The specification
includes a note about this saying that the element must be ignored for

As for editing, I think I'd tend to agree with Eliot's comment that it can
be used to help an author, though I disagree that this was the intent - it
was only added because we could not prevent it in the DTD / XSD
implementation, which is why the specification explicitly says to ignore
it. Similar language (and reasoning) exists for the topichead element - the
DTD / XSD cannot actually require the navtitle element now that it can be
specified in either location, but the intent is still to treat this as
requiring a title.

Robert D Anderson
IBM Authoring Tools Development
Chief Architect, DITA Open Toolkit (http://dita-ot.sourceforge.net/)

From:	"Mullins, Cheri" <Cheri.Mullins@amd.com>
To:	Eliot Kimber <ekimber@rsicms.com>, dita
Date:	06/25/2012 12:56
Subject:	RE: [dita] Question about <navtitle> in <topicgroup> allowed by
            DITA 1.2
Sent by:	<dita@lists.oasis-open.org>

I'm not necessarily opposed to that behavior, although that would be
opposite behavior from other navtitles, which, if specified, replace the
title both in the authoring environment and the output.

-----Original Message-----
From: dita@lists.oasis-open.org [mailto:dita@lists.oasis-open.org] On
Behalf Of Eliot Kimber
Sent: Monday, June 25, 2012 7:43 AM
To: dita
Subject: Re: [dita] Question about <navtitle> in <topicgroup> allowed by
DITA 1.2

My expectation would be that editors would show the title, even in a map
viewer like Oxygen's Map Manager.

That's because the value of titles on topic groups is for authors, letting
you label topic groups in order to clarify their intent and use.

If the spec doesn't make it clear that that behavior is allowed, I think we
need to clarify it.

It is definitely the case that topicgroup titles should not contribute to
the navigation hierarchy defined in a map as reflected in final-form
deliverables, but I don't think that same restriction should apply to
authoring environments.



On 6/25/12 6:57 AM, "Kristen James Eberlein" <kris@eberleinconsulting.com>

>    A question from Radu Coravu for us to consider.
>  Kris
>  -------- Original Message --------
>  Subject:  [Dita-ot-developer] Question about  in  allowed by DITA 1.2
>  Date:  Mon, 25 Jun 2012 11:51:31 +0300
>  From:  Radu Coravu <radu_coravu@sync.ro> <mailto:radu_coravu@sync.ro>
>  To:  dita-ot-developer@lists.sourceforge.net
> Hi everybody,
> The DITA OT specification states this:
> Beginning with DITA 1.2, you are able to specify a <navtitle> element
> within the <topicmeta> element inside of a <topicgroup>. The
> <topicgroup> element is meant as a non-titled grouping element, so
> adding a <navtitle> element to the <topicgroup> element has no defined
> purpose, and processors must ignore the title.
> I know the construct is not illegal according to the schemas but is
> the construct illegal according to the DITA 1.2 specification?
>> <topicgroup>
>>     <topicmeta>
>>       <navtitle>Navigation title</navtitle>
>>     </topicmeta>
>>   </topicgroup>
> One of our users has such constructs and wants Oxygen XML Editor to
> display these titles for <topicgroup>s when editing the DITA Map in
> the DITA Maps Manager view (which shows a TOC-like outline of the DITA
> I know there has been an older discussion about this:
>> https://lists.oasis-open.org/archives/dita/201008/msg00105.html
> In your opinion what would be the best approach for an editor which
> shows the TOC-like structure of the DITA Map?
> If the construct is not considered invalid by the spec (but more in a
> gray area) I guess we can make this improvement.
> Regards,
> Radu
> Radu Coravu
> <oXygen/>  XML Editor, Schema Editor and XSLT Editor/Debugger
> http://www.oxygenxml.com
> ----------------------------------------------------------------------
> --------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond.
> Discussions will include endpoint security, mobile security and the
> latest in malware threats.
> http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Dita-ot-developer mailing list
> Dita-ot-developer@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/dita-ot-developer

Eliot Kimber
Senior Solutions Architect, RSI Content Solutions "Bringing Strategy,
Content, and Technology Together"
Main: 512.554.9368
Book: DITA For Practitioners, from XML Press,

To unsubscribe, e-mail: dita-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: dita-help@lists.oasis-open.org

To unsubscribe, e-mail: dita-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: dita-help@lists.oasis-open.org

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