1、 ISO 2013 Intelligent transport systems System architecture, taxonomy and terminology Using XML in ITS standards, data registries and data dictionaries Systmes intelligents de transport Architecture, taxinomie et terminologie des systmes Usage de XML dans les normes, registres de donnes et dictionna
2、ires de donnes, en ITS INTERNATIONAL STANDARD ISO 24531 Second edition 2013-06-01 Reference number ISO 24531:2013(E) ISO 24531:2013(E)ii ISO 2013 All rights reserved COPYRIGHT PROTECTED DOCUMENT ISO 2013 All rights reserved. Unless otherwise specified, no part of this publication may be reproduced o
3、r utilized 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 c
4、opyright 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 ISO 24531:2013(E) ISO 2013 All rights reserved iii Contents Page Foreword v Introduction vi 1 Scope . 1 2 Conformance . 1 3 Normative refere
5、nces 1 4 T erms and definitions . 2 5 Abbreviated terms 7 6 Document convention . 8 7 Requirements 9 7.1 Required conditions . 9 7.2 Required items 9 7.3 Rules for modelling data exchanges . 9 7.4 Rules for using XML in ITS standards .12 8 Rules for registration and management of XML schema construc
6、ts in data registry (DR) and/or data dictionaries (DDs) 34 8.1 Objectives of schema constructs registration and management 34 8.2 Why use ISO 14817 data registry/ data dictionary (DR/DD)? .35 8.3 Schema constructs mapping to the ISO 14818 constructs 35 8.4 Registration and management rules .36 Annex
7、 A (informative) Model/document transformation.37 Annex B (normative) Definition of the Message class .40 Annex C (informative) Example Message Exchange: Model .47 Annex D (normative) Unqualified data types schema .50 Annex E (normative) Common basic components schema 68 Annex F (normative) Common a
8、ggregate components schema 72 Annex G (normative) Common extension components schema .79 Annex H (normative) Extension content data type schema 82 Annex I (normative) Common message components schema 84 Annex J (informative) Example message exchange: request message schema86 Annex K (informative) Ex
9、ample message exchange: response message schema .88 Annex L (informative) Ex ample message e x change: default generic ode files 90 Annex M (informative) Ex ample message e x change: default c ont e xt v alue association file .95 Annex N (informative) Ex ample CV A tr ansformation file 97 Annex O (i
10、nformative) Ex ample message e x change: default v alue v alidation tr ansformation file .99 Annex P (informative) Ex ample message e x change: cust omized generic ode files 101 Annex Q (informative) Example message exchange: customized context value associatio n file 104 Annex R (informative) Examp
11、le message exchange: customized value validation tr ansformation file 106 Annex S (informative) Example message exchange: customized extension content data type schema 108 Annex T (informative) Ex ample message e x change: cust omized data type definition .112 ISO 24531:2013(E)iv ISO 2013 All rights
12、 reserved Annex U (informative) Example message exchange: example request 113 Annex V (informative) Example message exchange: example responses .114 Annex W (informative) Comparison Between ISO 24531 and UBL NDR 2.1 117 Bibliography .123 ISO 24531:2013(E) Foreword ISO (the International Organization
13、 for Standardization) is a worldwide federation of national standards bodies (ISO member bodies). The work of preparing International Standards is normally carried out through ISO technical committees. Each member body interested in a subject for which a technical committee has been established has
14、the right to be represented on that committee. International organizations, governmental and non-governmental, in liaison with ISO, also take part in the work. ISO collaborates closely with the International Electrotechnical Commission (IEC) on all matters of electrotechnical standardization. The pr
15、ocedures used to develop this document and those intended for its further maintenance are described in the ISO/IEC Directives, Part 1. In particular the different approval criteria needed for the different types of ISO documents should be noted. This document was drafted in accordance with the edito
16、rial rules of the ISO/IEC Directives, Part 2. www.iso.org/directives Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights. ISO shall not be held responsible for identifying any or all such patent rights. Details of any patent rights ide
17、ntified during the development of the document will be in the Introduction and/or on the ISO list of patent declarations received. www.iso.org/patents Any trade name used in this document is information given for the convenience of users and does not constitute an endorsement. The committee responsi
18、ble for this document is ISO/TC 204, Intelligent Transport Systems. This second edition cancels and replaces the first edition (ISO 24531:2006). Clause 7 onwards has been technically revised. ISO 2013 All rights reserved v ISO 24531:2013(E) Introduction As the exchange of information via the interne
19、t and other wired and wire-free networks develops and expands, the use of XML (Extended Mark-up Language) and its variants continues to grow and develop. XML will be an important tool in the development and operation of “Intelligent Transport Systems” (ITS) services. However, within XML and its vari
20、ants there are options. In order to obtain maximum benefit, interoperability and re-use of data within the ITS sector, it is important to implement XML and its variants in a consistent manner. This International Standard provides definitions of how to use XML and its variants in a consistent and int
21、eroperable manner within the ITS sector.vi ISO 2013 All rights reserved INTERNATIONAL ST ANDARD ISO 24531:2013(E) Intelligent transport systems System architecture, taxonomy and terminology Using XML in ITS standards, data registries and data dictionaries 1 Scope This International Standard assists
22、ITS standards developers and users of ITS standards who wish to use XML, by providing a consistent definition of the rules and rule references for the use of XML within ITS systems. This International Standard defines consistent rules and rule references to provide a framework to be used when implem
23、enting XML-based applications in ITS, and particularly in specifying XML in ITS standards, ITS data registries and ITS data dictionaries. This International Standard also provides guidance and examples in respect of the use of XML in ITS, and the elaboration of XML within the ASN.1 data definitions
24、required by ISO 14813-6 and ISO 14817. NOTE A table of language comparisons (XML, ASN.1, UML) can be found in ISO 14813-6:2009. 2 Conformance This International Standard prescribes a conceptual model; it does not define any single physical implementation. It provides a consistent and interoperable m
25、eans of achieving interoperability for the international exchange of information in XML application programs. Regional and national XML schema have the option of providing additional schema and variants for use in local situations. In order to claim conformance with this International Standard, it i
26、s only required to design systems and exchange data consistently in accordance with the provisions of this International Standard. No external conformance procedures are proposed or defined in this International Standard, although regional, national and local implementations are free to, and may cho
27、ose to, define and require local conformance procedures. 3 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 (incl
28、uding any amendments) applies. ISO 14812:1999, Transport information and control systems Glossary standard terminologies for the transport information and control sector ISO 14817:2002, Transport information and control systems Requirements for an ITS/TICS central Data Registry and ITS/TICS Data Dic
29、tionaries ISO/IEC 19501:2005, Information technology Open Distributed Processing Unified Modeling Language (UML) Version 1.4.2 W3C Recommendation, Extensible Mark-up Language (XML) 1.0 (Fifth Edition), 26 November 2008 W3C Recommendation, Namespaces in XML 1.0 (Second Edition), 16 August 2006 W3C Re
30、commendation, XML Schema Part 1: Structures (Second Edition), 28 October 2004 W3C Recommendation, XML Schema Part 2: Datatypes (Second Edition), 28 October, 2004 W3C Recommendation, XML Linking Language (XLink), Version 1.0, 27 June 2001 ISO 2013 All rights reserved 1 ISO 24531:2013(E) W3C Recommend
31、ation, XSL Transformations (XSLT), Version 2.0, 23 January 2007 OASIS, Code List Representation (Genericode), Version 1.0, December 2007 OASIS, Context/value association using genericode 1.0, April 2010 ISOC, RFC 5141, A Uniform Resource Name (URN) Namespeace for the International Organization for S
32、tandardization (ISO), March 2008 4 T erms a nd definiti ons For the purposes of this document, the terms and definitions given in ISO 14812 and the following apply. 4.1 applicationprogram that reads XML documents and “does something useful” with them Note 1 to entry: Applications will normally be in
33、terfaced to an XML parser, for example via DOM or SAX. 4.2 ASN.1 application application that uses ASN.1 encodings for communication (except XER) 4.3 ASN.1 schema definition of the content and structure of data using an ASN.1 type definition 4.4 association endendpoint of an association, which conne
34、cts the association to a classifier 4.5 attributeproperty of an element Note 1 to entry: It is additional information about a piece of data (element). Often attributes are used to pass information about the element and hence can be said to provide metadata for the element. An attribute is a value in
35、dicator (=) and the attribute value is specified within the tag (i.e. ). Attribute in XML is a name=”value” pair that can be placed in the start tag of an element. For XML, all values have to be quoted with single or double quotes. 4.6 attributefeature within a classifier that describes a range of v
36、alues those instances of the classifier may hold 4.7 child elementelement contained within another element Note 1 to entry: The element containing other elements is a parent element. 4.8 classdescription of a set of objects that share the same attributes, operations, methods, relationships, and sema
37、ntics 4.9 class diagramdiagram that shows a collection of declarative (static) model elements, such as classes, types, and their contents and relationships2 ISO 2013 All rights reserved ISO 24531:2013(E) 4.10 constraintsemantic condition or restriction Note 1 to entry: Certain constraints are predef
38、ined in the UML, others may be user defined. Constraints are one of three extensibility mechanisms in UML. 4.11 contentall data between the start tag and end tag of an element Note 1 to entry: Content may be made up of mark-up characters and character data. 4.12 content modelexpression specifying wh
39、at elements and data are allowed within an element 4.13 data concept any of a group of data dictionary structures defined in ISO 14817 (i.e. object class, property, value domain, data element concept, data element, data frame, message, interface dialogue, association) referring to abstractions or th
40、ings in the natural world that can be identified with explicit boundaries and meaning and whose properties and behaviour all follow the same rules ISO 14817:2002, definition 4.4 4.14 Data Dictionary organized and constructed (electronic data base) compilation of descriptions of data concepts that pr
41、ovides a consistent means for documenting, storing and retrieving the syntactical form (i.e. representational form) and the meaning and connotation of each data concept ISO 14817:2002, definition 4.6 4.15 data element data concept; some single unit of information of interest (such as a fact, proposi
42、tion, observation, etc.) about some (entity) class of interest (e.g. a person, place, process, property, concept, association, state, event) ISO 14817:2002, definition 4.7 Note 1 to entry: A data element is considered to be indivisible in a particular context. 4.16 data frame data concept; grouping
43、of data elements primarily for the purpose of referring to the group with a single name, and thereby efficiently reusing groups of data elements that commonly appears together (as an ASN.1 SEQUENCE, SEQUENCE OF, SET, SET OF or CHOICE) in a message specification 4.17 data registry store of data, char
44、acterized in a consistent manner, as determined according to the provisions of this International Standard, used for a specific purpose (in this case ITS) ISO 14817:2002, definition 4.11 4.18 data typetype of content that an element contains in XML and UML Note 1 to entry: An author can specify an e
45、lements data type. ISO 2013 All rights reserved 3 ISO 24531:2013(E) 4.19 declarationcreate new types (both simple and complex) 4.20 de f i n i t ionenable elements and attributes with specific names and types (both simple and complex) to appear in document instances 4.21 d o c u m e n t t y p e d e
46、f i n i t i o nrules that define the tags that can be used in an XML file and their valid values 4.22 elementlogical data structure within an XML document, a piece of data within a file Note 1 to entry: An XML element consists of a start tag, and end tag, and the information between the tags, which
47、is often referred to as the contents. Start tags and end tags show the beginning and end of an element. A schema that can provide a description of the structure of the data describes elements used in an XML file. 4.23 elementatomic constituent of the UML model 4.24 end tagelement delimiter Note 1 to
48、 entry: In: this is a bar the construct is the end-tag. End tags cannot include anything other than the element name and trailing space. 4.25 global construct (e.g. element, group, attribute, attribute group, or data type) that is declared as a direct child of the schema root element 4.26 i n t e r
49、n e t ( u n i f o r m ) r e s o u r c e i d e n t i f i e r IRI compact string of characters for identifying an abstract or physical resource 4.27 lexical spaceset of valid literals for a data type 4.28 localelement, group, attribute, attribute group, or data types that are not global 4.29 mark-upidentification of element types and structure within a document Note 1 to entry: The mark-up is not actually part of the content, but identifies the components and their roles. 4.31 message data concept; grouping of data elements and
