1、BSI Standards Publication BS ISO/IEC 13250-3:2013 Information technology Topic Maps Part 3: XML syntaxBS ISO/IEC 13250-3:2013 BRITISH STANDARD National foreword This British Standard is the UK implementation of ISO/IEC 13250-3:2013. It supersedes BS ISO/IEC 13250-3:2007 which is withdrawn. The UK pa
2、rticipation in its preparation was entrusted to Technical Committee IST/41, Document description and processing language. A list of organizations represented on this committee can be obtained on request to its secretary. This publication does not purport to include all the necessary provisions of a
3、contract. Users are responsible for its correct application. The British Standards Institution 2013. Published by BSI Standards Limited 2013 ISBN 978 0 580 81278 1 ICS 35.240.30 Compliance with a British Standard cannot confer immunity from legal obligations. This British Standard was published unde
4、r the authority of the Standards Policy and Strategy Committee on 30 November 2013. Amendments issued since publication Date Text affectedBS ISO/IEC 13250-3:2013Reference number ISO/IEC 13250-3:2013(E) ISO/IEC 2013INTERNATIONAL STANDARD ISO/IEC 13250-3 Second edition 2013-11-01 Information technolog
5、y Topic Maps Part 3: XML syntax Technologies de linformation Plans relatifs des sujets Partie 3: Syntaxe XML BS ISO/IEC 13250-3:2013 ISO/IEC 13250-3:2013(E) COPYRIGHT PROTECTED DOCUMENT ISO/IEC 2013 All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or uti
6、lized otherwise in any form or by any means, electronic or mechanical, including photocopying, or posting on the internet or an intranet, without prior written permission. Permission can be requested from either ISO at the address below or ISOs member body in the country of the requester. ISO copyri
7、ght office Case postale 56 CH-1211 Geneva 20 Tel. + 41 22 749 01 11 Fax + 41 22 749 09 47 E-mail copyrightiso.org Web www.iso.org Published in Switzerland ii ISO/IEC 2013 All rights reservedBS ISO/IEC 13250-3:2013 ISO/IEC 13250-3:2013(E) iii ISO/IEC 2013 All rights reserved Contents Page Foreword iv
8、 Introduction. v 1 Scope 1 2 Normative references 1 3 Terms and definitions. 1 4 Syntax definition. 2 4.1 About the syntax. 2 4.2 Deserialization. 2 4.3 Common syntactical constructs 2 4.3.1 Common declarations. 2 4.3.2 The reifier attribute. 3 4.3.3 The reifier element. 3 4.3.4 The href attribute 3
9、 4.3.5 Creating IRIs from strings 3 4.4 The topicMap element. 4 4.5 The topic element. 4 4.6 The itemIdentity element 4 4.7 The subjectLocator element 4 4.8 The subjectIdentifier element. 5 4.9 The instanceOf element 5 4.10 The name element. 5 4.11 The value element. 6 4.12 The variant element. 6 4.
10、13 The scope element. 6 4.14 The type element. 6 4.15 The occurrence element 6 4.16 The resourceData element 7 4.16.1 General. 7 4.16.2 Deserialization. 7 4.16.3 Canonicalizing embedded XML. 7 4.17 The resourceRef element 7 4.18 The association element 8 4.19 The role element. 8 4.20 The topicRef el
11、ement. 8 4.21 The subjectIdentifierRef element. 8 4.22 The subjectLocatorRef element. 9 4.23 The mergeMap element. 9 5 Conformance. 9 Annex A (normative) A RELAX-NG schema for XTM 2.1 10 Annex B (informative) The XTM 2.1 DTD 12 Annex C (informative) A W3C XML Schema schema for XTM 2.1 16 Annex D (in
12、formative) Differences from XTM 2.0 to XTM 1.0. 21 Annex E (informative) Differences from XTM 2.1 to XTM 2.0. 22 Annex F (informative) Subject identifiers for defined terms. 23 Bibliography 24BS ISO/IEC 13250-3:2013 ISO/IEC 13250-3:2013(E) iv ISO/IEC 2013 All rights reservedForeword ISO (the Interna
13、tional Organization for Standardization) and IEC (the International Electrotechnical Commission) form the specialized system for worldwide standardization. National bodies that are members of ISO or IEC participate in the development of International Standards through technical committees establishe
14、d by the respective organization to deal with particular fields of technical activity. ISO and IEC technical committees collaborate in fields of mutual interest. Other international organizations, governmental and non-governmental, in liaison with ISO and IEC, also take part in the work. In the fiel
15、d of information technology, ISO and IEC have established a joint technical committee, ISO/IEC JTC 1. International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2. The main task of the joint technical committee is to prepare International Standards. Draft
16、International Standards adopted by the joint technical committee are circulated to national bodies for voting. Publication as an International Standard requires approval by at least 75 % of the national bodies casting a vote. Attention is drawn to the possibility that some of the elements of this do
17、cument may be the subject of patent rights. ISO and IEC shall not be held responsible for identifying any or all such patent rights. ISO/IEC 13250-3 was prepared by Joint Technical Committee ISO/IEC JTC 1, Information technology, Subcommittee SC 34, Document description and processing languages. Thi
18、s second edition cancels and replaces the first edition (ISO/IEC 13250-3:2007), which has been technically revised. ISO/IEC 13250-3 is part of a multi-part standard. The complete series will cancel and replace ISO/IEC 13250:2003. ISO/IEC 13250 consists of the following parts, under the general title
19、 Information technology Topic Maps: Part 2: Data model Part 3: XML syntax Part 4: Canonicalization Part 5: Reference model Part 6: Compact syntax BS ISO/IEC 13250-3:2013 ISO/IEC 13250-3:2013(E) v ISO/IEC 2013 All rights reserved Introduction XTM (XML Topic Maps) 2.1 is a syntax for the interchange o
20、f Topic Maps. The syntax is not designed to be extended or modified. Ease of human authoring was not prioritized during the design of XTM, and consequently it is not recommended to edit the syntax directly. This part of ISO/IEC 13250 should be read in conjunction with ISO/IEC 13250-2 since the inter
21、pretation of the XTM syntax is defined through a mapping from the syntax to the data model there defined. XTM 2.1 is a revision of the XTM 2.0 syntax defined in ISO/IEC 13250-3:2007. A description of the differences between the two versions can be found in Annex E.BS ISO/IEC 13250-3:2013 ISO/IEC 132
22、50-3:2013(E) vi ISO/IEC 2013 All rights reservedBS ISO/IEC 13250-3:2013 INTERNATIONAL STANDARD ISO/IEC 13250-3:2013(E) 1 ISO/IEC 2013 All rights reserved Information technology Topic Maps Part 3: XML syntax 1 Scope This part of ISO/IEC 13250 defines an XML-based interchange syntax for Topic Maps, wh
23、ich can be used to interchange instances of the data model defined in ISO/IEC 13250-2. It also defines a mapping from the interchange syntax to the data model. The syntax is defined with a RELAX-NG schema, and more precision is provided through the mapping to the data model, which effectively also d
24、efines the interpretation of the syntax. 2 Normative references The following referenced documents are indispensable for the application of this document. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendm
25、ents) applies. NOTE Each of the following documents has a unique identifier that is used to cite the document in the text. The unique identifier consists of the part of the reference up to the first comma. ISO/IEC 13250-2, Information technology Topic Maps Data Model W3C XML, Extensible Markup Langu
26、age (XML) 1.1 (Second Edition), W3C Recommendation, 29 September 2006, available at W3C XML-Names, Namespaces in XML, W3C Recommendation, 14 January 1999, available atW3C XML-Infoset, XML Information Set (Second Edition), W3C Recommendation, 4 February 2004, available atW3C Canonical XML, Canonical
27、XML Version 1.0, W3C Recommendation, 15 March 2001, available atISO/IEC 19757-2, Information technology Document Schema Definition Languages (DSDL) Part 2: Grammar- based validation RELAX NG IETF RFC 3986, Uniform Resource Identifiers (URI): Generic Syntax, Internet Standards Track Specification, Ja
28、nuary 2005, available at IETF RFC 3987, Internationalized Resource Identifiers (IRIs), Internet Standards Track Specification, January 2005, available at 3 Terms and definitions For the purposes of this part of ISO/IEC 13250, the following terms and definitions apply. 3.1 XTM the syntax defined in t
29、his part of ISO/IEC 13250BS ISO/IEC 13250-3:2013 ISO/IEC 13250-3:2013(E) 2 ISO/IEC 2013 All rights reserved 4 Syntax definition 4.1 About the syntax The acronym XTM is often used to refer to the syntax defined in this part of ISO/IEC 13250. Its full name is XML Topic Maps. The namespace for the XTM
30、syntax is http:/www.topicmaps.org/xtm/. An XTM document is an XML document that conforms to the XTM syntax. This clause defines the syntax of XTM documents using a RELAX-NG schema in compact syntax ISO/IEC 19757-2, and their semantics using prose describing the mapping from XTM documents to ISO/IEC
31、13250-2. The full schema can be found in Annex A, a DTD in Annex B, and a W3C XML Schema in Annex C. 4.2 Deserialization The process of exporting Topic Maps from an implementations internal representation of the data model to an instance of a Topic Maps syntax is known as serialization. The opposite
32、 process, deserialization, is the process of building an instance of an implementations internal representation of the data model from an instance of a Topic Maps syntax. This clause defines how instances of the XTM syntax are deserialized into instances of the data model defined in ISO/IEC 13250-2.
33、 Serialization is only implicitly defined, but implementations should guarantee that for any data model instance the XTM serialization produced by the implementation should when deserialized to a new data model instance produce one that has the same canonicalization as the original data model instan
34、ce, according to ISO/IEC 13250-4:2009. The input to the deserialization process is: A document item as defined by W3C XML-Infoset, representing an XTM document. (Information item properties from W3C XML-Infoset are referred to using property name, in order to distinguish them from properties from IS
35、O/IEC 13250-2.) An absolute IRI. This is the IRI from which the XTM document was retrieved, known as the document IRI. This IRI shall always be provided, as it is necessary in order to assign the item identifiers of the topic items created during deserialization. If the XTM document was not read fro
36、m any particular IRI the application is responsible for providing an IRI considered suitable. Deserialization is done by processing each element item in the document item in document order. For each element item encountered the operations specified in the clause for that element type are performed.
37、An input element item matches a clause in this document when the namespace uri property is set to “http:/www.topicmaps.org/ xtm/“, and the local name matches the element type name given in the title of that clause. Whenever a new information item is created, those of its properties which have set va
38、lues are initialized to the empty set; all other properties are initialized to null. NOTE This part of ISO/IEC 13250 requires an instance of the XML Information Set as input to the deserialization process, but in most cases the actual input will be an XML document. This part of ISO/IEC 13250 does no
39、t constrain how XML Information Set instances are built from XML documents, but assumes that in most cases this will be done by simply using an XML processor. XML processors conformant to the XML Recommendation may produce different results given the same XML document, depending on whether they are
40、validating or non-validating, and depending on which optional features they support. Reliance on any particular behaviour in the XML processors used by recipients is strongly discouraged. 4.3 Common syntactical constructs 4.3.1 Common declarations The following declarations are used throughout the s
41、chema for brevity. default namespace = “http:/www.topicmaps.org/xtm/“ namespace xtm = “http:/www.topicmaps.org/xtm/“BS ISO/IEC 13250-3:2013 ISO/IEC 13250-3:2013(E) 3 ISO/IEC 2013 All rights reserved datatypes xsd = “http:/www.w3.org/2001/XMLSchema-datatypes“ start = topicMap2 | topicMap21 href = att
42、ribute href xsd:anyURI any-markup = (text |element * - xtm:* attribute * text *, any-markup* )* reifiable21 = (attribute reifier xsd:anyURI | reifier)?,itemIdentity* tref = topicRef | subjectIdentifierRef | subjectLocatorRef NOTE The schema used in this part of ISO/IEC 13250 merges the XTM 2.0 and 2
43、.1 syntaxes into a single schema. Patterns specific to XTM 2.1 have names ending in 21, whereas those specific to 2.0 have names ending in 2. Only the XTM 2.1 patterns are given here, but the complete schema can be found in Annex A. 4.3.2 The reifier attribute The reifier attribute is used to refer
44、from the topic map construct on which it appears to the topic reifying that construct. The reference is an IRI matching one of the topics item identifiers. During deserialization the value in the normalized value property of the attribute node representing the reifier attribute is resolved into an a
45、bsolute IRI following the procedure in 4.3.5. If there is a topic item with that IRI in its item identifiers property, that topic item is set as the value of the reifier property of the topic map construct being processed. If no such topic item exists, a new topic item is created, the IRI added to i
46、ts item identifiers property, and that topic item is set as the value of the reifier property of the topic map construct being processed. NOTE This attribute duplicates the function of the reifier element (see 4.3.3) in a less general form. It is a legacy from XTM 2.0 retained only in order to prese
47、rve backwards compatibility. 4.3.3 The reifier element The reifier element is used to assign a reifying topic to the topic map construct represented by its parent element. The reference is a child element referencing the topic. The reifier element is declared as follows: reifier = element reifier tr
48、ef During deserialization the child element produces a topic item following the procedure in the clause defining deserialization of that element type. The topic item produced is set as the value of the reifier property of the information item produced by the parent element. 4.3.4 The href attribute
49、The href attribute always references an information resource using a relative or absolute IRI valid according to IETF RFC 3986 and IETF RFC 3987, but the meaning of the reference depends on context. During deserialization the value in the normalized value property of the attribute node representing the href attribute is turned into an IRI following the procedure in 4.3.5. 4.3.5 Creating IRIs from strings To create an IRI from a stri
