I think there may be two different issues at work here relative to the use of keys, glossref’s default of print=”no” and the fact that you can’t reliably crossref to resource-only keys.
If you have a cross reference from a topic to a key and that key is defined only as a resource-only resource (e.g., only defined on a <keydef>) then the target topic *should not be rendered* in any rendition and the cross reference should be unresolved. If the topic is also included as a normal-role resource but the key reference is to the resource-only key topic will be rendered but the cross reference should still not resolve because the reference was to a resource-only key. That is, the processing role of the target key matters.
In HTML, depending on how your processor works, the topic may be rendered for other reasons and the key reference may work *by accident* (even though it shouldn’t).
However, in PDF the resource-only *cannot be rendered* because it has not been put in the navigational flow of the publication and therefore the cross reference cannot be resolved, even by accident.
In order to have correct key-based cross references to topics you *must* use keys on navigation topicrefs. This should be true for *all* rendition types but it is necessarily true for PDF (because it’s a monolithic rendition type and therefore there’s no way for a resource-only topic to be accidently included in the result).
That is, given this map:
<map>
<title>My publication</title>
<keydef keys=”topic-02” href="">
…
<topicref href="">
</map>
And this reference in topic-one.dita:
<p>See <xref keyref=”topic-02”/>…</p>
The link as rendered should *never* be resolvable in any rendition because the key “topic-02” binds to a resource-only topic, which by definition *is not rendered*.
To make the cross reference resolvable you need to include topic-02 in the navigation structure, e.g.:
<map>
<title>My publication</title>
<topicref keys=”topic-02” href="">
<topicref href="">
</map>
Or:
<map>
<title>My publication</title>
<keydef keys=”topic-02-resonly” href="">
…
<topicref href="">
<topicref keys=”topic-02” keyref=”topic-02-resonly”/>
</map>
Cheers,
E.
--
Eliot Kimber
http://contrext.com
From: <dita@lists.oasis-open.org> on behalf of Scott Hudson <scott.hudson@jeppesen.com>
Date: Tuesday, February 21, 2017 at 11:05 AM
To: Eric Sirois <eric.sirois@ixiasoft.com>, "dita@lists.oasis-open.org" <dita@lists.oasis-open.org>
Subject: Re: [dita] RE: Overall fixes for bookmap for 2.0
Well, the most annoying thing IMO is that even if the keys resolve, they won’t show up in output unless you specifically set print=“yes”. I’ve run into this a ton with term/abbreviated-form.
—Scott
From: <dita@lists.oasis-open.org> on behalf of Éric Sirois <eric.sirois@ixiasoft.com>
Date: Tuesday, February 21, 2017 at 10:03 AM
To: Éric Sirois <eric.sirois@ixiasoft.com>, "dita@lists.oasis-open.org" <dita@lists.oasis-open.org>
Subject: [dita] RE: Overall fixes for bookmap for 2.0
Specifically looking to allow Keydefs in a more natural position in the map versus the first instance were topicref is allowed in the current content model. Are there other things that we have ignored about bookmaps in DITA 1.3?
Éric Sirois
DITA Toolsmith
IXIASOFT
825 Querbes, Suite 200, Montréal, Québec, Canada, H2V 3X1
tel + 1 514 279-4942 / toll free + 1 877 279-4942
mobile + 1 647 462-3620
eric.sirois@ixiasoft.com/www.ixiasoft.com
From: dita@lists.oasis-open.org [mailto:dita@lists.oasis-open.org] On Behalf Of Éric Sirois
Sent: February 21, 2017 11:33 AM
To: dita@lists.oasis-open.org
Subject: [dita] Overall fixes for bookmap for 2.0
Hi,
We have a number of clients that have hit some limitations for keyref and ditavalref in bookmaps. I would like to work on a proposal that would address those limitations in DITA 2.0. Would it be possible to create a project entry in the DITA 2.0 project?
Kind regards,
Éric Sirois
DITA Toolsmith
IXIASOFT
825 Querbes, Suite 200, Montréal, Québec, Canada, H2V 3X1
tel + 1 514 279-4942 / toll free + 1 877 279-4942
mobile + 1 647 462-3620
eric.sirois@ixiasoft.com/www.ixiasoft.com
--------------------------------------------------------------------- To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail. Follow this link to all your TCs in OASIS at: https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php