OASIS Darwin Information Typing Architecture (DITA) TC

 View Only

  • 1.  Is using a "null" keydef with

    Posted 08-26-2011 03:00
    I'm in the process of describing how to deal with the case where you have an xref through a key and you use the topic in two maps. In one map you want the link to work and in the other map you want the link to be completely ignored. I tried creating a "null" keydef, e.g.: <keydef keys="gloss-tenkan"/> With the hope that the Open Toolkit would treat this as a link to nothing and simply suppress the xref. I don't think the Toolkit's behavior is necessarily wrong, but I'm wondering if the behavior I was hoping for is sensible? That is, would it be appropriate to say something like "A cross reference to a key that has no remote resource and for which link text is available, either in the key definition or in the content of the xref, should not be treated as a link. If the cross reference has empty content, the link text provided by the key definition should be rendered."? This would allow you to have cross references that could be easily "turned off" by using "null" key definitions. Of course, in most, if not all cases, the use of xref could (and probably should) be replaced with use of <keyword> or <term>, but I thought this was still an interesting edge case. Cheers, Eliot -- Eliot Kimber Senior Solutions Architect "Bringing Strategy, Content, and Technology Together" Main: 512.554.9368 www.reallysi.com www.rsuitecms.com


  • 2.  Re: [dita] Is using a "null" keydef with

    Posted 08-26-2011 03:05
    On 8/25/11 9:59 PM, "Eliot Kimber" <ekimber@reallysi.com> wrote: > With the hope that the Open Toolkit would treat this as a link to nothing > and simply suppress the xref. I meant to include "It did not". That is, the Toolkit didn't do what I sort of hoped it might do. The question is: is what I hoped for sensible? Cheers, E. -- Eliot Kimber Senior Solutions Architect "Bringing Strategy, Content, and Technology Together" Main: 512.554.9368 www.reallysi.com www.rsuitecms.com


  • 3.  RE: [dita] Is using a "null" keydef with

    Posted 08-30-2011 18:05
    Eliot, I'd swear that this behavior (a key definition with no href 'turns off' linking elements when referenced) was explicit in the spec, but I can't find it. In any case, that's what I'd expect, and it's how Arbortext processes such things. Chris
    Original Message


  • 4.  Re: [dita] Is using a "null" keydef with

    Posted 08-30-2011 20:21
    It's explicit for elements that take only @keyref, but not for <xref>. That is, if a <keyword> has a keyref and it either has local content or the key definition has no href and no link text, then there can be no link, just as if the keyref had not bee specified and that's how the Toolkit behaves. The Toolkit definitely treats an <xref> to a "null" keydef as a broken link, rather than as an inactive link. Cheers, E. On 8/30/11 1:05 PM, "Nitchie, Chris" <cnitchie@ptc.com> wrote: > Eliot, > > I'd swear that this behavior (a key definition with no href 'turns off' > linking elements when referenced) was explicit in the spec, but I can't > find it. In any case, that's what I'd expect, and it's how Arbortext > processes such things. > > Chris > >
    Original Message


Related Content