Recorded: January 12, 2017
DITA 1.3 introduces scoped keys, which expand the key functionality introduced in DITA 1.2. In DITA 1.2, a key could have only one definition with a root map. This limitation proved a barrier to a fully-realized reuse strategy for many documentation teams.
Scoped keys enable a key to be redefined at multiple levels (key spaces) in a map, with each key definition effective within its own key space. A key space can be the entire root map, a sub-map, a topichead or topicgroup, or even a single topicref, meaning (for one thing) that a topic can be reused many times in a map with its keys being resolved different in each instance of the topic.
The scoped keys functionality makes use of a new keyscope attribute added to the appropriate map node. This attribute is not required; unscoped keys can still be used and continue to function as they did in DITA 1.2.
This webinar explains the evolution of keys between DITA 1.2 and DITA 1.3, and presents several basic examples and use cases for scoped keys. It also explains key spaces and the interaction between multiple key spaces in a map. During this webinar, the presenter will use the oXygen XML editor with the understanding that other XML editors might choose to visually represent the scoped key functionality differently.
Presented by: Leigh W. White, IXIASOFT Technologies
Leigh is a DITA Specialist at IXIASOFT, where she helps documentation groups evaluate their workflows and content models and transition into the DITA CCMS. Leigh has spoken on DITA, content management systems and content conversion at a number of conferences, including DITA North America, DITA Europe, Intelligent Content, DITA-OT Day, the STC Summit, Lavacon, and Writers UA. She is the author of DITA For Print: A DITA Open Toolkit Workbook and a contributor to The Language of Content Strategy and The Language of Technical Communication.