[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [dita] Attributes for topicrefs that use @keyref
Hi Robert, Thanks a lot for explaining. Also, what about the @keyref, @conkeyref and @class ? I think these shouldn't be combined. Regards, Tarun Garg | Adobe Systems | +91-120-2444711 | tarung@adobe.com -----Original Message----- From: Robert D Anderson [mailto:robander@us.ibm.com] Sent: Monday, August 16, 2010 11:56 PM To: Tarun Garg Cc: dita@lists.oasis-open.org Subject: Re: [dita] Attributes for topicrefs that use @keyref Hi Tarun, The href behavior you are describing is correct. The @href value is only a fallback value for instances where the key does not resolve; if the key resolves, then the original @href value is never used. That is the primary purpose of the keyref function. Are there other attributes that cause concern? Robert D Anderson IBM Authoring Tools Development Chief Architect, DITA Open Toolkit From: Tarun Garg <tarung@adobe.com> To: "dita@lists.oasis-open.org" <dita@lists.oasis-open.org> Date: 07/28/2010 07:06 AM Subject: [dita] Attributes for topicrefs that use @keyref The section “2.1.3.4.3.3 Processing key references”, mentions: “The attributes that are common to a key definition element and a key reference element using that key, other than the @keys and @id attributes, are combined as for content references, including……..” As I understand, I see concerns for other attributes that will get combined/derived. Like if @href is derived from the key defining element, then the fallback target of the topicref shall be lost… or in other words the @href mentioned in key defining element shall get used as the fallback in all the topicrefs referring to that key. Regards, Tarun Garg
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]