BS ISO/IEC 13250:2000

1 Scope
2 Normative references
3 Definitions
      3.1 added themes
      3.2 association
      3.3 association link
      3.4 association role
      3.5 association type
      3.6 base name
      3.7 bounded object set (BOS)
      3.8 display name
      3.9 facet
      3.10 facet link
      3.11 facet type
      3.12 facet value
      3.13 hub document
      3.14 occurrence role
      3.15 public subject descriptor
      3.16 scope
      3.17 sort name
      3.18 subject
      3.19 subject descriptor
      3.20 theme
      3.21 topic
      3.22 topic association
      3.23 topic characteristic
      3.24 topic characteristic assignment
      3.25 topic link
      3.26 topic map
      3.27 topic name
      3.28 topic occurrence
      3.29 topic type
      3.30 unconstrained scope
4 Notation
      4.1 RCS name, full name, description, and clause
      4.2 Constraints
      4.3 Note
5 Topic Maps architecture
      5.1 Topic Map Architectural Form
      5.2 Topic link
             5.2.1 Topic Link Architectural Form
             5.2.2 Topic Name Architectural Form
             5.2.3 Topic Occurrence Architectural Form
      5.3 Association Link
             5.3.1 Association Link Architectural Form
             5.3.2 Association Role Architectural Form
      5.4 Themes To Be Added Architectural Form
      5.5 Facet Linking
             5.5.1 Facet Link Architectural Form
             5.5.2 Facet Value Architectural Form
6 Conformance
Annex A (Normative) Topic Maps Meta-DTD
Annex B (Informative) Example Architectural Support
                      Declaration for the Topic Maps
                      Architecture

Relates to Topic Maps which enable multiple, concurrent views of sets of information objects. The structural nature of these views is unconstrained; they may reflect an object orientated approach, or they may be hierarchical, relational, ordered, unordered or any combination. An unlimited number of topic maps may be overlaid on a given set of information resources. Does not require or disallow the use of any scheme for addressing information objects. Except for the requirement that topic map documents be expressed themselves using SGML (or WebSGML) and HyTime, using the syntax described, neither does it require or disallow the use of any notation used to express information.