Oxygen XML Forum

Posted: **Sun Oct 03, 2010 3:17 am**

I'm using the conkeyref features, and I found something rather strange:

When I add a conkeyref range for a few steps, the conref attribute is fine, but the conrefend attribute gets a strange value:

Code: Select all

        <steps>

            <step conkeyref="resource/step1" conrefend="fake.dita#fake/step3">

                <cmd/>

            </step>

        </steps>

In my ditamap I have defined a keydef for resource that points to a resource.dita topic. But where does this fake.dita come from? There is no such file, and yet the editor inserts it in the conrefend... Strangely, the conkeyref works fine. It also works fine if I manually change conkeyrefend to resource/step3. But I would have expected the editor to insert that value directly when I choose the steps in the conkeyref dialog?

What is happening here?

Regards,

Anders

Posted: **Mon Oct 04, 2010 10:18 am**

Hi Anders,

The thing is that if you use ranges with conkeyref the DITA Open Toolkit is only interested in the range-end index, in this case the step3 attribute. But the strange (not well-thought in my opinion) thing using the DITA architecture is that you still have to specify the end range using conrefend. The conrefend needs to have a special format in order to be processed succesfully (because it was designed to be used with conref) so that is why it needs to also have the fake.dita#fake in its value (or anything else like default.dita#default).
Those values are ignored by the DITA OT processor but they still need to be there.

See the section Using conrefend together with conkeyref from this specification:
http://docs.oasis-open.org/dita/v1.2/cd ... ibute.html

Regards,
Radu

Posted: **Mon Oct 04, 2010 11:45 am**

Ok, thanks!

Oxygen XML Forum

Strange value in conkeyref

Strange value in conkeyref

Re: Strange value in conkeyref

Re: Strange value in conkeyref