ISO/TR 24097-2:2015

TECHNICAL ISO/TR
REPORT 24097-2
First edition
2015-10-15
Intelligent transport systems — Using
web services (machine-machine
delivery) for ITS service delivery —
Part 2:
Elaboration of interoperable web
services’ interfaces
Utilisation des services du Web (livraison de machine à machine) pour
la livraison de services ITS
Reference number
©
ISO 2015
© ISO 2015, Published in Switzerland
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or 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 ISO’s member body in the country of
the requester.
ISO copyright office
Ch. de Blandonnet 8 • CP 401
CH-1214 Vernier, Geneva, Switzerland
Tel. +41 22 749 01 11
Fax +41 22 749 09 47
copyright@iso.org
www.iso.org
ii © ISO 2015 – All rights reserved

Contents Page
Foreword .iv
Introduction .v
1 Scope . 1
2 Normative references . 1
3 Terms and definitions . 1
4 Abbreviated terms . 2
5 Notation and conventions . 3
5.1 Namespace URI and prefixes used in this specification . 3
5.2 Web service syntax notation: pseudo-schemas . 3
5.3 XPath 1.0 expression . 4
5.4 SOA stack name notation . 4
5.5 The context of the terms WSDL, SOAP, and BP . 4
5.6 Examples . 4
5.7 The term {service, user}. 4
6 Interoperable version selection of interface description metadata .4
7 SOAP version selection . 5
7.1 SOAP 1.1 or SOAP 1. 2? . 5
7.2 Creating a SOAP 1.2 web service . 5
7.3 SOAP 1.2 usage indication . 6
8 WS-I basic profile conformance . 7
8.1 What is WS-I? . 7
8.2 Specific WS metadata and WS metadata relationships . 8
8.3 Creating a basic profile conformant service . 9
8.3.1 Using a WSDL editor .10
8.3.2 Using an XML editor .11
8.4 BP conformance claim .13
Annex A (informative) Pseudo WSDL 1.1 expression .14
Annex B (informative) Main standard schema locations .16
Annex C (informative) BP 1.2 and BP2.0 Coverage items .17
Annex D (informative) BP 1.2 and BP2.0 conformance policy assertion schema .19
Bibliography .20
Foreword
ISO (the International Organization 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 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 procedures 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
editorial rules of the ISO/IEC Directives, Part 2 (see 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 identified during the development of the document will be in the Introduction and/or
on the ISO list of patent declarations received (see 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.
For an explanation on the meaning of ISO specific terms and expressions related to conformity
assessment, as well as information about ISO’s adherence to the WTO principles in the Technical
Barriers to Trade (TBT) see the following URL: Foreword - Supplementary information
The committee responsible for this document is ISO/TC 204, Intelligent transport systems.
ISO 24097 consists of the following parts, under the general title Intelligent transport systems — Using
web services (machine-machine delivery) for ITS service delivery:
— Part 1: Realization of interoperable web services
— Part 2: Elaboration of interoperable web services’ interfaces [Technical Report]
The following parts are under preparation:
— Part 3: Quality of service [Technical Report]
iv © ISO 2015 – All rights reserved

Introduction
ITS services have been evolving from single functional and limited area services, to services in which
many systems co-operate to provide effective and efficient services across a wide area. In today’s world,
ITS services are required to communicate not just with other parts of the same ITS service provision,
but between different ITS services, and even with non-ITS services or a user’s system directly. (Some
examples of these systems are communication with/between traffic management, route guidance
systems, security systems, environment protection systems, private freight management systems, and
transport-related electronic payment service with banking or credit industry.)
These systems (even those limited to ITS services) are usually deployed in a heterogeneous
circumstance, use different hardware, different operating systems (OS), middleware, or development
(programing) languages. This therefore creates a challenge in order to realize system coordination
across the organizations in a way that is flexible, quick, and at reasonable cost. Web services (WS)
are a recent methodology that overcomes these difficulties. Using WS technology for ITS services can
significantly simplify and reduce the cost of internet based service provision, which may well affect the
level and speed of take up of use of ITS services.
WS require a lot of functionalities, and as a result, architecture is indispensable. WS standardization
organizations construct standards by Service-Oriented Architecture (SOA). SOA is an evolutional form
of distributed computing and object orientation.
By applying SOA based standards to the ITS services, the following effects are expected.
From a business viewpoint:
— increased service value;
— internationalization;
— expansion to the business automation.
From a system development viewpoint:
— Easy and quick development of ITS service coordination and service area expansion;
— WS enables system developer focus on “WHAT” not “HOW”. “HOW” is covered by standard-based
tools. This enables quick and easy system software development;
— WS standards have a composable structure, and so promote reusability of software by SOA;
— Easy connection to a legacy system.
In the ITS sector, message standardization of many applications have already been completed, are
well-advanced, or are determined regionally. Message standardization is intended to improve system
coordination, interoperability, and re-use. So the conditions for WS are considered already mature. In
addition, the use of WS will increase the flexibility of ITS services to interoperate and communicate
beyond the ITS sector and in areas where the delineation between ITS services and general commercial
services converge.
From the viewpoint of WS standards evolution, 2007 was an epoch-making year. Web Service
Description Language (WSDL) 2.0 became a W3C recommendation. Corresponding with this, relevant
WS specifications were standardized by open standard bodies (W3C and OASIS). These standards
cover all functional layers. Using these standards, the ITS sector has a sound base for interoperable WS.
ITS service collaboration with other sectors is expected to increase mutual effectiveness. Globalization
of economies also requires communication across the domains and jurisdictions. All these
collaborations rely on the interoperability of services. Interoperability can be achieved if based on
open international standards.
WS was created to use distributed network resources in an interoperable way. However, to realize
interoperable WS various functionalities are required.
In most ITS services, availability and quick recovery from a fault is critical. Business process
management and monitoring help to realize these requirements. Business Process Execution Language
(BPEL) is considered one method. It is based on web services. BPEL also enables various services
combination and automatic execution of business process. All these apply to web services.
This Technical Report presents a base of high quality ITS services with easy and quick development as
well as a base for further service expansion.
“Using web services (machine-machine delivery) for ITS service delivery” has been developed considering
these requirements. ISO 24097 consists of three parts: ISO 24097-1, ISO 24097-2, and ISO 24097-3.
ISO 24097-1 is an International Standard. ISO 24097-2 and ISO 24097-3 are Technical Reports.
ISO 24097-1 focused on an approach to realize interoperable ITS WS. ISO 24097-2 and ISO 24097-3 are
example based documents that show how to realize interoperable ITS web services that are already
described in ISO 24097-1.
Fundamental concept
Metadata, as this term reminds us, may be considered a higher level description of requirements and
constraints of a web service. Metadata are, by its nature, declarative. Declarative means one does not
care about how to realize requirement, but only about what functionality is wanted in a WS.
ISO 24097-1 proposed to construct metadata description based on standards. Recap key points of
ISO 24097-1 are as follows:
a) To construct interoperable WS, standards-based metadata description is mandatory. This also
implies a technical contract between service provider
...