[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [dita-comment] DITA1.2: Query on <desc> element's content in a keyreferencing <link> element
Hi Nakshatra, First - sorry for the delay in this response. My interpretation of this is that the shortdesc / desc content should work much the same as the linktext. That is to say, assume I have this key definition: <topicref keys="a" href="maptarget"> <topicmeta> <linktext>Map linktext</linktext> <shortdesc>Map shortdesc</shortdesc> </topicmeta> </topicref> Now say I have these two uses in a topic: <link keyref="a"/> <link keyref="a" href="topictarget"> <linktext>Topic linktext</linktext> <desc>Topic desc</desc> </link> In this case, the target for each link will be "maptarget" and the link text for each link will be "Map linktext". It is logical that the short description should work the same way as the link text, so the effective <desc> content for each link will be "Map shortdesc". I believe that the topic should be updated to clarify that shortdesc works the same way here as linktext. Does that make sense? Thanks - Robert D Anderson IBM Authoring Tools Development Chief Architect, DITA Open Toolkit From: Nakshatra Bhardwaj <nbhardwa@adobe.com> To: "dita-comment@lists.oasis-open.org" <dita-comment@lists.oasis-open.org> Date: 07/21/2010 08:19 AM Subject: [dita-comment] DITA1.2: Query on <desc> element's content in a key referencing <link> element Hi All, I would like to have some additional input on section “2.1.3.4.3.3 Processing key references” in the Specs_Review#5. The specs say that “For <link> tags with a keyref attribute, the contents of the <shortdesc> tag in the key-defining element should provide the <desc> contents.” The question I have is how should DITA processors handle insertion of links in such a case. As per my understanding I have come to these conclusions for linktext and desc elements- On insertion of <link> element the <linktext> element would automatically get the effective content from topicmeta’s <linktext> element. In case the element has been provided alternate text by the author, the processor should honour that and not bring in content from the topicmeta of the key-defining element. Now coming to my question- What should the processor ideally do with the linktext’s <desc> element if the topicmeta provides a <shortdesc> element. Should the <shortdesc> element be pulled in automatically *every time* the links are created? OR the <desc> element should be populated with content only when the user inserts the <desc> element and also in case where the topic has an empty <desc> element for that <link> element. Regards, Nakshatra
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]