[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [dita] Question from keys review: addressing non-topicref elements in a map
I'd settle for removing the word 'non-topicref' so that it reads, "and elements within maps." If you bind a map to a key
<mapref href="" keys="mapKey"/>
Then to reference any element in that map via key, keyref="mapKey/elementId". For example:
<topicref conkeyref="mapKey/topicrefId"/>
-or-
<navtitle conkeyref="mapKey/someTitle"/>
You'd use conkeyref instead of keyref on the former to pull in the whole branch, as opposed to referencing whatever content is referenced by that topicref. I don't think you could use conkeyref="someRandomKey" to effectively conref the key-defining topicref.
Chris
P.S. I'm on vacation this week and only checking e-mail occasionally, but I wanted to contribute my $0.02 while my thoughts were fresh. From: dita@lists.oasis-open.org <dita@lists.oasis-open.org> on behalf of Robert D Anderson <robander@us.ibm.com>
Sent: Thursday, May 7, 2015 11:58 AM To: DITA TC Subject: [dita] Question from keys review: addressing non-topicref elements in a map DITAWeb URL:
My own additional commentary: For elements within topics, we always have the #topic/element syntax for linking with @href. So it's clear to me that when a key name resolves to a topic, "key/element" means the XML element with id="element" inside that topic. It maps easily to the @href syntax of #[variable-topic]/element. When referencing any element in a map (a topicref, a navtitle, a phrase inside link text), the syntax is file.ditamap#element or just #element. If we do in fact allow a key syntax of keyref="key/mapelement", I don't know how it resolves. Robert D Anderson IBM Authoring Tools Development Chief Architect, DITA Open Toolkit (http://www.dita-ot.org/) |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]