BS PD ISO TR 24097-2-2015 Intelligent transport systems Using web services (machine-machine delivery) for ITS service delivery Elaboration of interoperable web services' interfaces.pdf

《BS PD ISO TR 24097-2-2015 Intelligent transport systems Using web services (machine-machine delivery) for ITS service delivery Elaboration of interoperable web services' interfaces.pdf》由会员分享，可在线阅读，更多相关《BS PD ISO TR 24097-2-2015 Intelligent transport systems Using web services (machine-machine delivery) for ITS service delivery Elaboration of interoperable web services' interfaces.pdf（34页珍藏版）》请在麦多课文档分享上搜索。

1、BSI Standards Publication Intelligent transport systems Using web services (machine-machine delivery) for ITS service delivery Part 2: Elaboration of interoperable web services interfaces PD ISO/TR 24097-2:2015National foreword This Published Document is the UK implementation of ISO/TR 24097-2:2015.

2、 The UK participation in its preparation was entrusted to Technical Committee EPL/278, Intelligent transport systems. 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 cont

3、ract. Users are responsible for its correct application. The British Standards Institution 2015. Published by BSI Standards Limited 2015 ISBN 978 0 580 87307 2 ICS 35.240.60 Compliance with a British Standard cannot confer immunity from legal obligations. This Published Document was published under

4、the authority of the Standards Policy and Strategy Committee on 30 November 2015. Amendments/corrigenda issued since publication Date Text affected PUBLISHED DOCUMENT PD ISO/TR 24097-2:2015 ISO 2015 Intelligent transport systems Using web services (machine-machine delivery) for ITS service delivery

5、Part 2: Elaboration of interoperable web services interfaces Utilisation des services du Web (livraison de machine machine) pour la livraison de services ITS TECHNICAL REPORT ISO/TR 24097-2 Reference number ISO/TR 24097-2:2015(E) First edition 2015-10-15 PD ISO/TR 24097-2:2015 ISO/TR 24097-2:2015(E)

6、ii ISO 2015 All rights reserved COPYRIGHT PROTECTED DOCUMENT 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 posti

7、ng 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 copyright office Ch. de Blandonnet 8 CP 401 CH-1214 Vernier, Geneva, Switzerland Tel. +41 22 749 01 11 Fax +4

8、1 22 749 09 47 copyrightiso.org www.iso.org PD ISO/TR 24097-2:2015 ISO/TR 24097-2:2015(E)Foreword iv Introduction v 1 Scope . 1 2 Normative references 1 3 T erms 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 W

9、eb 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.

10、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 W S-I basic pr ofile c onformanc e 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

11、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 schem

12、a .19 Bibliography .20 ISO 2015 All rights reserved iii Contents Page PD ISO/TR 24097-2:2015 ISO/TR 24097-2:2015(E) Foreword ISO (the International Organization for Standardization) is a worldwide federation of national standards bodies (ISO member bodies). The work of preparing International Standa

13、rds 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 tak

14、e 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 pa

15、rticular 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 o

16、f 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

17、 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 ISOs adherence

18、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 transpor

19、t 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 Reportiv I

20、SO 2015 All rights reserved PD ISO/TR 24097-2:2015 ISO/TR 24097-2:2015(E) 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 todays world, ITS s

21、ervices 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 users system directly. (Some examples of these systems are communication with/between traffic management, route guidance systems, s

22、ecurity 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, dif

23、ferent 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 th

24、ese 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.

25、 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 serv

26、ice 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

27、 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

28、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

29、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 st

30、andardized 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 req

31、uires 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. ISO 2015 All rights reserved v PD ISO/TR 24097-2:2015 ISO/TR 24097-2:2015(E) WS was created to use d

32、istributed 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 Pro

33、cess 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 de

34、velopment 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 Standar

35、d. 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 Met

36、adata, 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 2409

37、7-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 and service consumers. b) WS service

38、 description metadata consists of interface metadata and Quality of Services (QoS) metadata. Only by describing both metadata could WS be interoperable. In addition to interoperability, this metadata provides the following: 1) easy development of WS starting from requirements and constraints (top do

39、wn approach); 2) quick and effective and high quality system delivery of service from metadata with support from a software tool called a generator (especially this feature is especially important for a service consumer); 3) readily realize service evolution and maintenance throughout its lifecycle.

40、 c) Interface metadata describes the interface between a service program and a service consumer program. Therefore, this metadata represents interface contract between service provider and consumer. This information is published by the service provider and evaluated by potential consumers. This meta

41、data are expressed in Web Service Description Langage (WSDL). d) QoS metadata are composite of domain specific requirements and constraints such as security, reliable messaging, message addressing, Simple Object Access Protocol (SOAP) message transmission optimization. QoS metadata are described usi

42、ng WS-Policy. WS-Policy is constructed by two standards; “WS-Policy 1.5 Framework” and “WS-Policy 1.5 Attachment”. Figure 1 depicts web service descriptive language metadata USE Case and its role in web services.vi ISO 2015 All rights reserved PD ISO/TR 24097-2:2015 ISO/TR 24097-2:2015(E) Figure 1 H

43、igh level ITS web service metadata role Table 1 is a high-level use case description of ITS web service metadatas role. ISO 2015 All rights reserved vii PD ISO/TR 24097-2:2015 ISO/TR 24097-2:2015(E) Table 1 Use case description of ITS WS metadatas role in high level Use case description (Level 1) Na

44、me ITS Web Services metadata role Actors Service provider Potential service consumer Service consumer Description This use case depicts a high level ITS WS metadata role through an ITS WS lifecycle. Main scenario 1. Service provider creates standard-based interface and QoS metadata, and gives ver- s

45、ion number individually. (See Alt-1 for alternative scenario) 2. Service provider publishes metadata through Universal Description, Discovery, and Integration (UDDI), Service end point, web page, etc. 3. Service provider develops web service, including (Generating skeleton or stub). 4. Service provi

46、der provides the service. 5. Potential service consumer estimates the service from the view point of business value to him and/or interoperability realization difficulty. 6. If potential user decides to utilize the service, he develops client WS program, includ- ing the generation of a skeleton or s

47、tub. 7. Service consumer tests his program interoperability to the service program. 8. After successful interoperability test consumer utilizes the service. Alternative scenario Alt-1: In the case of the service provider service 1. He changes the metadata and the relevant version number. 2. Publishe

48、s revised metadata. 3. Resume. Use case description (Level 2) Name Generate skeleton or stub Description Service provider or service consumer creates skeleton or stub, respectively. Usually this process is done by using WS development tools. This enables stakeholder to quickly develop program and go

49、 sooner to interoperability test. Main scenario 1. A tool reads interface metadata and QoS metadata. 2. It creates the interface part and run time data for required QoS. e) “WS-Policy 1.5Framework” acts as a structure for connecting domain specific metadata in one policy document. Each domain specific metadata has its own vocabulary and is identified by its namespace. Joining service side policy and service consumer policy, interoperability can then be tested. If join is not empty, then service provider pr