atom feed6 messages in org.oasis-open.lists.ditaRe: [dita] Conref push of different c...
FromSent OnAttachments
Eliot KimberJan 25, 2010 6:29 am 
Ogden, JeffJan 25, 2010 6:44 am 
Eliot KimberJan 25, 2010 7:01 am 
Bruce Nevin (bnevin)Jan 25, 2010 9:18 am 
Eliot KimberJan 25, 2010 9:26 am 
Bruce Nevin (bnevin)Jan 25, 2010 1:41 pm 
Subject:Re: [dita] Conref push of different content to the same topic in different contexts
From:Eliot Kimber (ekim@reallysi.com)
Date:Jan 25, 2010 9:26:52 am
List:org.oasis-open.lists.dita

On 1/25/10 11:19 AM, "Bruce Nevin (bnevin)" <bne@cisco.com> wrote:

Does it have to be the ultimate root map, or can the governing map be a submap?

Not sure I understand your question.

Assuming that PDF pagination is consecutive from chapter to chapter, then the publication must be represented by single map processed as a unit, as opposed to treating each chapter as a separate publication processed separately.

In that case, it doesn't matter where the reference is, a given will have exactly one binding, so you can't have a single resolve to a different target in different submaps.

Cheers,

E.

-----Original Message----- From: Eliot Kimber [mailto:ekim@reallysi.com] Sent: Monday, January 25, 2010 9:30 AM To: dita Subject: [dita] Conref push of different content to the same topic in different contexts

I'm pretty sure the answer is "no" based on my understanding of the feature, but I wanted to confirm that one cannot use conref push to impose different elements onto the same topic used in different places within the same map.

The question was asked today on the DITA users list how to have a topic used in four chapters of a single manual where the topic differed only a couple of details.

Because in this case it's a single publication (single root map), you cannot use keys to get different results and a conref push likewise points from the pusher to exactly one pushee.

If my analysis is correct, it suggests there might be a useful feature for 1.3 consideration to enable associating a pushing topic with a target topic in a use-specific way, perhaps a new attribute on topicref or something.

Cheers,