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 PublicationIntelligent transport systems Using web services (machine-machine delivery) for ITS service deliveryPart 2: Elaboration of interoperable web services interfacesPD ISO/TR 24097-2:2015National forewordThis Published Document is the UK implementation of ISO/TR24097-2:2015.The U

2、K participation in its preparation was entrusted to TechnicalCommittee EPL/278, Intelligent transport systems.A list of organizations represented on this committee can be obtained onrequest to its secretary.This publication does not purport to include all the necessary provisions ofa contract. Users

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

4、theStandards Policy and Strategy Committee on 30 November 2015.Amendments/corrigenda issued since publicationDate Text affectedPUBLISHED DOCUMENTPD ISO/TR 24097-2:2015 ISO 2015Intelligent transport systems Using web services (machine-machine delivery) for ITS service delivery Part 2: Elaboration of

5、interoperable web services interfacesUtilisation des services du Web (livraison de machine machine) pour la livraison de services ITSTECHNICAL REPORTISO/TR24097-2Reference numberISO/TR 24097-2:2015(E)First edition2015-10-15PD ISO/TR 24097-2:2015ISO/TR 24097-2:2015(E)ii ISO 2015 All rights reservedCO

6、PYRIGHT PROTECTED DOCUMENT ISO 2015, Published in SwitzerlandAll 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,

7、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 officeCh. de Blandonnet 8 CP 401CH-1214 Vernier, Geneva, SwitzerlandTel. +41 22 749 01 11Fax +41 22 749 09 47copyrightiso.orgwww.iso.or

8、gPD ISO/TR 24097-2:2015ISO/TR 24097-2:2015(E)Foreword ivIntroduction v1 Scope . 12 Normative references 13 Terms and definitions . 14 Abbreviated terms 25 Notation and conventions . 35.1 Namespace URI and prefixes used in this specification 35.2 Web service syntax notation: pseudo-schemas 35.3 XPath

9、 1.0 expression 45.4 SOA stack name notation . 45.5 The context of the terms WSDL, SOAP, and BP 45.6 Examples 45.7 The term service, user 46 Interoperable version selection of interface description metadata 47 SOAP version selection . 57.1 SOAP 1.1 or SOAP 1. 2? . 57.2 Creating a SOAP 1.2 web servic

10、e . 57.3 SOAP 1.2 usage indication . 68 WS-I basic profile conformance 78.1 What is WS-I? . 78.2 Specific WS metadata and WS metadata relationships 88.3 Creating a basic profile conformant service 98.3.1 Using a WSDL editor 108.3.2 Using an XML editor .118.4 BP conformance claim . 13Annex A (informa

11、tive) Pseudo WSDL 1.1 expression .14Annex B (informative) Main standard schema locations .16Annex C (informative) BP 1.2 and BP2.0 Coverage items .17Annex D (informative) BP 1.2 and BP2.0 conformance policy assertion schema .19Bibliography .20 ISO 2015 All rights reserved iiiContents PagePD ISO/TR 2

12、4097-2:2015ISO/TR 24097-2:2015(E)ForewordISO (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 inter

13、ested 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

14、 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 docume

15、nts 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 responsibl

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

17、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 to the WTO principles in the Technical Barriers to Trade (TBT) see the following URL:

18、Foreword - Supplementary informationThe 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

19、: Realization of interoperable web services Part 2: Elaboration of interoperable web services interfaces Technical ReportThe following parts are under preparation: Part 3: Quality of service Technical Reportiv ISO 2015 All rights reservedPD ISO/TR 24097-2:2015ISO/TR 24097-2:2015(E)IntroductionITS se

20、rvices 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 services are required to communicate not just with other parts of the same ITS service provisi

21、on, 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, security systems, environment protection systems, private freight management systems, and tran

22、sport-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 therefo

23、re 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 t

24、he 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). S

25、OA 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 v

26、iewpoint: 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 prom

27、ote 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, a

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

29、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. Usi

30、ng 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 intero

31、perability of services. Interoperability can be achieved if based on open international standards. ISO 2015 All rights reserved vPD ISO/TR 24097-2:2015ISO/TR 24097-2:2015(E)WS was created to use distributed network resources in an interoperable way. However, to realize interoperable WS various funct

32、ionalities 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 v

33、arious 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) f

34、or 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 interope

35、rable 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 conceptMetadata, as this term reminds us, may be considered a higher level description of requirements and constraints o

36、f 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 follo

37、ws: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 description metadata consists of interface metadata and Quality of Services (QoS) metadata. Only by describing b

38、oth 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 down approach);2) quick and effective and high quality system delivery of service from metadata with support from a

39、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.c) Interface metadata describes the interface between a service program and a service consumer program. Therefore, t

40、his metadata represents interface contract between service provider and consumer. This information is published by the service provider and evaluated by potential consumers. This metadata are expressed in Web Service Description Langage (WSDL).d) QoS metadata are composite of domain specific require

41、ments and constraints such as security, reliable messaging, message addressing, Simple Object Access Protocol (SOAP) message transmission optimization. QoS metadata are described using WS-Policy. WS-Policy is constructed by two standards; “WS-Policy 1.5 Framework” and “WS-Policy 1.5 Attachment”.Figu

42、re 1 depicts web service descriptive language metadata USE Case and its role in web services.vi ISO 2015 All rights reservedPD ISO/TR 24097-2:2015ISO/TR 24097-2:2015(E)Figure 1 High level ITS web service metadata roleTable 1 is a high-level use case description of ITS web service metadatas role. ISO

43、 2015 All rights reserved viiPD ISO/TR 24097-2:2015ISO/TR 24097-2:2015(E)Table 1 Use case description of ITS WS metadatas role in high levelUse case description (Level 1)Name ITS Web Services metadata roleActors Service providerPotential service consumerService consumerDescription This use case depi

44、cts 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-sion number individually. (See Alt-1 for alternative scenario)2. Service provider publishes metadata through Universal Description, Dis

45、covery, and Integration (UDDI), Service end point, web page, etc.3. Service provider develops web service, including (Generating skeleton or stub).4. Service provider provides the service.5. Potential service consumer estimates the service from the view point of business value to him and/or interope

46、rability realization difficulty.6. If potential user decides to utilize the service, he develops client WS program, includ-ing the generation of a skeleton or stub.7. Service consumer tests his program interoperability to the service program.8. After successful interoperability test consumer utilize

47、s the service.Alternative scenario Alt-1: In the case of the service provider service1. He changes the metadata and the relevant version number.2. Publishes revised metadata.3. Resume.Use case description (Level 2)Name Generate skeleton or stubDescription Service provider or service consumer creates

48、 skeleton or stub, respectively. Usually this process is done by using WS development tools. This enables stakeholder to quickly develop program and go 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

49、 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 program and service consumer program are interoperable.f) “WS-Policy 1.5Attachment” gives mechanism to attach policy to WSDL that policy is effective