[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Third draft of keyref FAQ item #3: How should elements with keyref attributes be rendered? (formerly 'Key resolution for complex <topicmeta> content')
I think this is is the final draft of this FAQ item, or close to final: http://wiki.oasis-open.org/dita/Review-FAQ-#preview . Please let us know in the next week if you have any suggestions or questions on it, as I would like to post it to dita.xml.org after next Tuesday's DITA TC meeting. Thanks to Chris, Kris, Robert, Michael, Bruce, and Dave for reviewing the earlier drafts over the past two months.
I should point out a couple of issues which we've clarified or noticed recently, which have some important implications for information architects adopting DITA:
1) Topicmeta never overrides local content. This means that you cannot use a strategy of writing topics with general terminology for a product line, and using <topicmeta> in key definitions to make the output more specific for particular products within the product line.
2) If a team requires a particular alt text string to be reused wherever a particular image is used, it is not possible to do this using keys that point directly to image files (e.g. <keydef keys="smile" href=""images/smile.gif"/>). As an alternative strategy, teams with this requirement could put <image> elements with alt text in resource-only topics, and use conkeyref to include those images in the topics where they ought to be displayed.
JustSystems Canada, Inc.
Office: 1 (778) 327-6356
XMetaL Community Forums: http://forums.xmetal.com