Key scopes enable map authors to specify different sets of key definitions for different map branches.
A key scope is defined by a
element that specifies the
@keyscope attribute. The
attribute specifies the names of the scope, separated by spaces.
A key scope includes the following components:
@keyscope attribute is specified on both a
reference to a DITA map and the root element of the referenced map, only one scope is created;
the submap does not create another level of scope hierarchy. The single key scope that results
from this scenario has multiple names; its names are the union of the values of the
@keyscope attribute on the map reference and the root element of the submap.
This means that processors can resolve references to both the key scopes specified on the map
reference and the key scopes specified on the root element of the submap.
The root element of a root map always defines a key scope, regardless of whether a
@keyscope attribute is present. All key definitions and key references exist
within a key scope, even if it is an unnamed, implicit key scope that is defined by the root
element in the root map.
Each key scope has its own key space that is used to resolve the key references that occur within the scope. The key space that is associated with a key scope includes all of the key definitions within the key scope. This means that different key scopes can have different effective key definitions:
Key references in each key scope are resolved using the effective key definition that is specified within its own key scope.
Consider the following scenario:
<map> <mapref keyscope="A" href="installation.ditamap"/> <!-- ... --> </map>
<map keyscope="B"> <!-- ... --> </map>
Only one key scope is created; it has key scope names of "A" and "B".
Return to main page.
Standards Track Work Product
|Copyright © OASIS Open 2015. All Rights Reserved.||17 December 2015|