subjectRelHeader
The <subjectRelHeader> element specifies the roles played by subjects in associations.
You use the subjectRelHeader element to supply a header row for a subject relationship table when you want to identify the roles played by the subjects in each column. Each cell in the header row identifies a subject topic that defines a role. When specializing the subjectRelTable element, you can accomplish the same purpose by specializing the cells within the rows to enforce the roles.
Contains
Note: These models represent only the default document types distributed by OASIS. Actual content models will differ with each new document type.
Doctype | Content model |
subjectScheme | |
Contained by
Doctype | Content model |
subjectScheme | |
Inheritance
- map/relrow subjectScheme/subjectRelHeader
Example 174. Example
The subject relationship table in this example establishes environmentFor relationships between operating systems and applications. Based on the subjectRole element, subjects in the first column are operating systems which are the environment for an application, while subjects in the second column are applications that run in that environment. For a user interested in content about the operating system, content about the applications may also be relevant.
<subjectScheme>
<hasKind>
<subjectdef keys="operatingSystem">
<subjectdef keys="linuxOS"/>
<subjectdef keys="windowsOS"/>
</subjectdef>
<subjectdef keys="application">
<subjectdef keys="IDE">
<subjectdef keys="eclipseIDE"/>
<subjectdef keys="visualStudioIDE"/>
</subjectdef>
<subjectdef keys="webBrowser">
<subjectdef keys="firefoxBrowser"/>
<subjectdef keys="ieBrowser"/>
</subjectdef>
</subjectdef>
</hasKind>
...
<subjectRelTable>
<subjectRelHeader>
<subjectRole>
<subjectdef keyref="operatingSystem">
<hasRelated keyref="environmentFor">
<subjectdef keyref="application"/>
</hasRelated>
</subjectdef>
</subjectRole>
<subjectRole>
<subjectdef keyref="application"/>
</subjectRole>
</subjectRelHeader>
<subjectRel>
<subjectRole>
<subjectdef keyref="linuxOS"/>
<subjectdef keyref="windowsOS"/>
</subjectRole>
<subjectRole>
<subjectdef keyref="eclipseIDE"/>
<subjectdef keyref="firefoxBrowser"/>
</subjectRole>
</subjectRel>
<subjectRel>
<subjectRole>
<subjectdef keyref="windowsOS"/>
</subjectRole>
<subjectRole>
<subjectdef keyref="ieBrowser"/>
<subjectdef keyref="visualStudioIDE"/>
</subjectRole>
</subjectRel>
</subjectRelTable>
</subjectScheme>
A table view of the subjectRelTable may look like this; each <subjectRel> represents a single row, and each <subjectRole> represents a cell.
Table 7. subjectRelTable as a table
<subjectdef keyref="operatingSystem">
<hasRelated keyref="environmentFor">
<subjectdef keyref="application"/>
</hasRelated>
</subjectdef> | <subjectdef keyref="application"/> |
<subjectdef keyref="linuxOS"/>
<subjectdef keyref="windowsOS"/> | <subjectdef keyref="eclipseIDE"/>
<subjectdef keyref="firefoxBrowser"/> |
<subjectdef keyref="windowsOS"/> | <subjectdef keyref="ieBrowser"/>
<subjectdef keyref="visualStudioIDE"/> |
Attributes
Name | Description | Data Type | Default Value | Required? |
univ-atts attribute group (includes select-atts, id-atts, and localization-atts groups) | | | | |
global-atts attribute group (xtrf, xtrc) | | | | |
class | | | | |
Parent topic
