Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
The international standard ISO/IEC 13250-3:2015 (adopted in Canada as CAN/CSA-ISO/IEC 13250-3:2015, also referenced as IEC 13250-3-15) defines the XML Syntax for Topic Maps (XTM). This part of the ISO/IEC 13250 series specifies an XML grammar for interchanging topic maps—a powerful paradigm for representing and navigating knowledge structures. This article provides a detailed technical overview of the standard, focusing on its scope, core requirements, implementation guidelines, and compliance considerations.
The scope of CAN/CSA-ISO/IEC 13250-3:2015 is to define a standardized XML representation for Topic Maps. Topic Maps are a formalism for organizing and linking information about topics (subjects) and their relationships, known as associations. The standard specifies:
This standard applies to any application that needs to exchange topic map data in XML, including semantic web tools, knowledge management systems, and content aggregation platforms. It is intended to be used in conjunction with ISO/IEC 13250-1:2013 (Topic Maps — Reference Model) and ISO/IEC 13250-2:2015 (Topic Maps — Data Model).
This section outlines the essential technical elements defined by the standard. Implementers must adhere to the XML syntax rules and data model constraints to ensure interoperable topic map interchange.
The core XML elements defined by the standard are derived from the Topic Maps data model. Each topic map construct has a corresponding XML element, as summarized in the table below.
| Topic Map Construct | XML Element | Key Attributes | Occurrence |
|---|---|---|---|
| Topic Map | topicMap | id, reifier | 1 (root) |
| Topic | topic | id, subjectIdentifier, subjectLocator, reifier | 0..n |
| Topic Name | name | id, reifier | 0..n per topic |
| Name Variant | variant | id, reifier | 0..n per name |
| Occurrence | occurrence | id, type, reifier | 0..n per topic |
| Association | association | id, type, reifier | 0..n |
| Role | role | id, type, reifier | 1..n per association |
Each element must adhere to the cardinality and content models defined in the standard’s XML Schema (XSD) and Relax NG schemas. For example, a topic element must contain at least one subjectIdentifier or subjectLocator unless it is a reifier.
The standard defines the namespace http://www.topicmaps.org/xtm/1.0/ for XTM 1.0 and http://www.topicmaps.org/xtm/2.0/ for XTM 2.0 (adopted in this edition). The 2015 edition uses the XTM 2.0 namespace. Documents must declare the correct namespace and use the version attribute to indicate conformance.
http://www.topicmaps.org/xtm/2.0/ to indicate compliance with ISO/IEC 13250-3:2015. Avoid deprecated URIs from earlier drafts. Two levels of conformance are defined:
The standard provides normative XML Schemas and Relax NG grammars for validation. Processors must support these schemas to verify conformance.
When implementing support for CAN/CSA-ISO/IEC 13250-3:2015 (IEC 13250-3-15), developers should consider the following practical aspects:
The XTM syntax is closely aligned with the Topic Maps Data Model (ISO/IEC 13250-2). Implementers should ensure that their data model representation can map losslessly to the XML syntax. For example, reification constructs (the reifier attribute) must be supported to preserve identity relations.
Subject identifiers (URIs) and subject locators (URIs) are used to identify topics. The standard requires that these URIs be normalized according to Section 6 of RFC 3986. Processors should apply URI normalization to avoid false mismatches.
http://example.org/ vs http://EXAMPLE.ORG/). Always perform case normalization and percent-encoding normalization. The standard allows for the inclusion of foreign elements and attributes from other namespaces, provided they do not interfere with the core XTM syntax. Extension elements should be placed in a separate namespace and must not change the meaning of standard elements. Processors may ignore or propagate such extensions.
Ensuring compliance with CAN/CSA-ISO/IEC 13250-3:2015 requires attention to both the XML syntax and the semantic constraints of the Topic Maps data model.
For formal compliance declarations, organizations should conduct independent testing or use recognized compliance suites. The standard encourages implementers to publish their validation results and participate in conformance testing initiatives.