Hi Tarun,

A key value may be set on any topicref element, so it may be associated with any valid target that can be referenced with a topicref.

A topicref element may not reference elements nested inside a topic, but it may be used to reference elements inside of a map. For example, this is a valid reference on a topicref: <topicref href="othermap.ditamap#branch" format="ditamap"/>

If a key is added on that topicref, it is associated with that branch of the map. The topicsetref element is a specialized topicref that references a branch of a map, just like in that example. Specifically, it references a topicset element inside of a map: <topicsetref href="othermap.ditamap#topicset-branch"/>

So, it's not an error to have a keys attribute on topicsetref. In short - any specialized topicref still needs to point to something that is valid for topicref. In this case, it's a branch of a map, which is valid for both elements. Anything referenced by a topicref can be associated with a key ... so the keys attribute is valid in this case as well.

Robert D Anderson IBM Authoring Tools Development Chief Architect, DITA Open Toolkit

From: Tarun Garg <tar...@adobe.com> To: "di...@lists.oasis-open.org" <di...@lists.oasis-open.org> Date: 07/28/2010 07:28 AM Subject: [dita] @keys in <topicsetref>

<topicsetref> points to a <topicset> element in a DITA Map. As per my understanding, a key identifies/points to a Map/Topic. So, if a key is defined on <topicsetref> (using @keys) what shall it refer to?

I think, @keys does not make sense on <topicsetref>, as it points to an element inside a Map (and not to the Map itself). Hence, @keys shall be dropped from <topicsetref>.

Regards, Tarun Garg | Adobe Systems | +91-120-2444711 | tar...@adobe.com