DOCSLIB.ORG

WSDL WSDL Versioning Facts Basic Scenario

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
WSDL WSDL Versioning Facts Basic Scenario Internet Engineering WSDL - Web Services Description Tomasz Babaczy ński , Zofia Kruczkiewicz Language Tomasz Kubik SAWSDL - Semantic Annotations for Information systemsmodelling – UML and WSDL and XML Schema service description languages WSDL versioning WSDL • an XML application, developed by W3C, used to write a • Two major versions of WSDL specification formal, technical description of web service interfaces. – WSDL 1.1 (old W3C proposition, but still used), • provides distinct definitions and terminologies used in web – WSLD 2.0 (current W3C recommendation) service description • The WSDL 2.0 got its name after renaming WSDL 1.2 because • a schema for services declarations as collections of network of some substantial differences between 1.1 and 1.2 versions endpoints, or ports, offering operations, and exchanging data through messages • WSDL 2.0 accepts binding to all the HTTP request methods (not only GET and POST as in WSDL 1.1) so it better suits for separates abstract definitions from concrete use or instance • RESTful web services implementation. • enough to generate code partially, for a client or a server side of the service, in an automatic manner (it is also possible to • There is also SOAP 1.1 binding recommendation available. generate WSDL description on a base of existing code of web However, WSDL 1.1 has better support from software service implementation). development tools. Facts Basic scenario Specification Publication date Status WSDL 1.1 Note 15 Mar 2001 Draft /Proposal WSDL Usage Scenarios 04 Jun 2002 Draft /Proposal WSDL Requirements 28 Oct 2002 Draft /Proposal • a client discovers a web service in the network and WSDL Architecture 11 Feb 2004 Draft /Proposal analyses its description provided in the WSDL Glossary 11 Feb 2004 Draft /Proposal corresponding WSDL document, WSDL Usage Scenarios 11 Feb 2004 Draft /Proposal WSDL 1.2 Core Language 11 Jun 2003 Draft /Proposal • a client learns from the description about operations WSDL 1.2 Message Patterns 11 Jun 2003 Draft /Proposal provided and data types used by the service, WSDL 1.2 Bindings 11 Jun 2003 Draft /Proposal • a client decides, which operations he or she is WSDL 2.0 Primer 26 Jun 2007 Recommendation WSDL 2.0 Core Language 26 Jun 2007 Recommendation interested in, and builds the application code for it WSDL 2.0 Adjuncts 26 Jun 2007 Recommendation • if a client wants and can, it invokes chosen service’s WSDL 2.0 SOAP 1.1 Binding 26 Jun 2007 Recommendation WSDL 2.0 RDF Mapping 26 Jun 2007 Recommendation operations. Web Services Addressing Core 09 May 2006 Recommendation Web Services Addressing SOAP Binding 09 May 2006 Recommendation Web Architecture 15 Dec 2004 Draft /Proposal Structure of WSDL 1.1 document Structure of WSDL 2.0 document • The abstract section includes: port types, messages and types • The abstract section includes: interfaces and types constructs. constructs. – An interface collects together supported operations. Port types are abstract collections of supported operations. – – An operation associates a message exchange pattern with one or – Operations refer to messages that are abstract descriptions of the more messages. data being exchanged. – Messages are described using a type system (usually XML Schema) for – Operations and messages are bound to a concrete network protocol defining bodies of inputs, outputs and faults. and message format. • The concrete section includes: binding that specifies transport • The concrete section includes: binding that defines the and wire format details for one or more interfaces. concrete protocol and data format specifications for a particular port type. – An endpoint associates a network address with a binding. – A group of endpoints that implement a common interface defines a – Port definition associates a network address with a reusable binding. service. – A collection of ports defines a service. WSDL 1.1 WSDL 2.0 input documentation output import definitions description any ##other fault WSDL 1.1 types types types 0.. ∞ 0.. ∞ part Element decl. Element decl. message output 0.. ∞ Type def. Type def. input documentation portType fault documentation 0.. ∞ message operation any ##other 0.. ∞ 0.. ∞ portType interface request-response-or-one-way-operation operation operation solicit-response-or-notification-operation section Abstract input input MEP definitions documentation output output binding fault infault Operation any ##other documentation style 0.. ∞ outfault any ##other documentation operation 0.. ∞ fault 0.. ∞ input any ##other documentation output 0.. ∞ any ##other binding binding service 0.. ∞ fault port 0.. ∞ service service 0.. ∞ documentation section port endpoint Concrete anyTopLevelOptionalElement any ##other 0.. ∞ <definitions> <documentation> • This is a root element of WSDL document. It • Element documentation is used to provide a works as a container for several fragments human readable description. This element (nested elements) that forms together a full can assists (be nested in) any other element service description. appearing in a WSDL document. • It provides namespace declarations valid for its content along with XML namespace prefixes. <import> <types> • This elements works like #include preprocessor • This element is a container for data types directive in C programming language. It allows definitions used in <message> elements. It splitting the description into independent contains zero or more sub-elements documents and integrating them in one, main <schema>, which must adhere to the rules document as necessary. This improves the modularity and legibility definition of the service. for XML Schema documents. The declared The import has two attributes: namespace and types can be complexType or simpleType. location. <message> <operation> • is an abstract definition of an operation supported by a Web • This element defines the format of messages service exchanged between a client and a web • there can be several input, output and fault messages defined service. It may represent a query, a response declared using nested <input>, <output> and <fault> elements. These elements refer to <message> elements or a signal on error. It refers to the data defined in the same WSDL document or imported from types defined in <types>. The data contained external documents. • the order of messages should follows so called Message in <message> are abstract. A message Exchange Patterns (MEP). consists of one or more sub-elements <part> <binding> <portType> • This elements is used to specify a concrete • This element specifies a set of operations protocol binding and data encoding for a given <portType> (i.e. it provides binding to HTTP, SOAP supported by the service endpoint (it MIME or, possibly, custom protocols). provides a unique identifier to a group of • Since in the WSDL document <operation> operations supported by a single endpoint). elements are already defined, the element <binding> maps the abstract definitions of Each <operation> is defined individually. operations, their input and output messages, to the appropriate protocol used by a web service. documentation any ##any 0..∞ 0..∞ WSDL 2.0 <service> import documentation 0.. ∞ description include documentation types 0.. ∞ • This element appears typically at the end of the operation interface WSDL document. It defines a concrete web service input 0.. ∞ fault 0.. ∞ output endpoint with URL to the service location (there is any ##other 0.. ∞ no other occurrences of such URL before service documentation infault 0.. ∞ element). <service> element groups one or more binding operation outfault fault <port> elements. A single <port> element any ##other 0.. ∞ represents an endpoint (access point) to a web any ##other service. documentation 0.. ∞ service endpoint 1.. ∞ any ##other any ##other <description> <documentation> • The <description> is a main element of a WSDL document. The content of this element should conform to the • A human readable description in the WSDL 2.0 following pattern: documents is provided within optional <description <documentation> elements. These elements can targetNamespace=" xs:anyURI " > appear in all elements included in a <description>. <documentation />* The <documentation> syntax is following: [ <import /> | <include /> ]* <types />? <documentation> [ <interface /> | <binding /> | <service [extension elements]* /> ]* </documentation> </description> <include> and <import> <types> • Element <include> allows to include components defined in other WSDL documents in the current interface definition. • Element <types> serves as a place for definitions of data Element <include> has a mandatory location attribute types used by exchanged messages. which specifies the location of the external, included WSDL documents. The target namespace of attached WSDL • XML Schema is preferred as typing language, although it is descriptions must match the target namespace of the base possible to use also the DTD or RELAX NG. document. • The use of custom schemas relies on importing them (with • Element <import> has a similar meaning as <include>. The the use of <xs:import>) or embedding them within <types> difference is that the imported WSDL document can have element of the WSDL document (using <xs:schema>). different target namespace then the base document. This element has a mandatory namespace attribute for an • The elements from imported or included schemas can be imported element and an optional location attribute. referenced by using their QName. Standard content of this element is as follows: <interface> <fault>
Load more

Recommended publications
  • V a Lida T in G R D F Da
    Series ISSN: 2160-4711 LABRA GAYO • ET AL GAYO LABRA Series Editors: Ying Ding, Indiana University Paul Groth, Elsevier Labs Validating RDF Data Jose Emilio Labra Gayo, University of Oviedo Eric Prud’hommeaux, W3C/MIT and Micelio Iovka Boneva, University of Lille Dimitris Kontokostas, University of Leipzig VALIDATING RDF DATA This book describes two technologies for RDF validation: Shape Expressions (ShEx) and Shapes Constraint Language (SHACL), the rationales for their designs, a comparison of the two, and some example applications. RDF and Linked Data have broad applicability across many fields, from aircraft manufacturing to zoology. Requirements for detecting bad data differ across communities, fields, and tasks, but nearly all involve some form of data validation. This book introduces data validation and describes its practical use in day-to-day data exchange. The Semantic Web offers a bold, new take on how to organize, distribute, index, and share data. Using Web addresses (URIs) as identifiers for data elements enables the construction of distributed databases on a global scale. Like the Web, the Semantic Web is heralded as an information revolution, and also like the Web, it is encumbered by data quality issues. The quality of Semantic Web data is compromised by the lack of resources for data curation, for maintenance, and for developing globally applicable data models. At the enterprise scale, these problems have conventional solutions. Master data management provides an enterprise-wide vocabulary, while constraint languages capture and enforce data structures. Filling a need long recognized by Semantic Web users, shapes languages provide models and vocabularies for expressing such structural constraints.
    [Show full text]
  • Semantic Description of Web Services
    Semantic Description of Web Services Thabet Slimani CS Department, Taif University, P.O.Box 888, 21974, KSA Abstract syntaxes) and in terms of the paradigms proposed for The tasks of semantic web service (discovery, selection, employing these in practice. composition, and execution) are supposed to enable seamless interoperation between systems, whereby human intervention is This paper is dedicated to provide an overview of these kept at a minimum. In the field of Web service description approaches, expressing their classification in terms of research, the exploitation of descriptions of services through commonalities and differences. It provides an semantics is a better support for the life-cycle of Web services. understanding of the technical foundation on which they The large number of developed ontologies, languages of are built. These techniques are classified from a range of representations, and integrated frameworks supporting the research areas including Top-down, Bottom-up and Restful discovery, composition and invocation of services is a good Approaches. indicator that research in the field of Semantic Web Services (SWS) has been considerably active. We provide in this paper a This paper does also provide some grounding that could detailed classification of the approaches and solutions, indicating help the reader perform a more detailed analysis of the their core characteristics and objectives required and provide different approaches which relies on the required indicators for the interested reader to follow up further insights objectives. We provide a little detailed comparison and details about these solutions and related software. between some approaches because this would require Keywords: SWS, SWS description, top-down approaches, addressing them from the perspective of some tasks bottom-up approaches, RESTful services.
    [Show full text]
  • D1.2.1 WSMO Grounding in SAWSDL
    Project Number: 215219 Project Acronym: SOA4ALL Project Title: Service Oriented Architectures for All Instrument: Integrated Project Thematic Information and Communication Priority: Technologies D1.2.1 WSMO grounding in SAWSDL Activity N: 1 Fundamental and Integration Work Package: 1 Service Web Architecture Due Date: M6 Submission Date: 27/08/2008 Start Date of Project: 01/03/2006 Duration of Project: 36 Months Organisation Responsible of Deliverable: UIBK Revision: 1.0 Author(s): Jacek Kopecký, Adi Schütz UIBK Project co-funded by the European Commission within the Seventh Framework Programme (2007-2013) Dissemination Level PU Public X PP Restricted to other programme participants (including the Commission) RE Restricted to a group specified by the consortium (including the Commission) CO Confidential, only for members of the consortium (including the Commission) SOA4All –FP7 – 215219 – D1.2.1 WSMO grounding in SAWSDL Version History Version Date Comments, Changes, Status Authors, contributors, reviewers 0.1 2008/07/16 Initial version Jacek Kopecký 0.2 2008/07/24 Filling in more Jacek Kopecký, Adi Schütz 0.9 2008/07/25 A complete draft, ready for review Jacek Kopecký, Adi Schütz 0.95 2008/07/19 Review comments incorporated Elisabetta Di Nitto, Marin Dimitrov, Jacek Kopecký 1.0 2008/07/23 Version to be submitted Jacek Kopecký © SOA4ALL consortium Page 2 of 28 SOA4All –FP7 – 215219 – D1.2.1 WSMO grounding in SAWSDL Table of Contents EXECUTIVE SUMMARY ____________________________________________________ 5 1. INTRODUCTION ______________________________________________________
    [Show full text]
  • OGC Testbed-14: Semantically Enabled Aviation Data Models Engineering Report
    OGC Testbed-14 Semantically Enabled Aviation Data Models Engineering Report Table of Contents 1. Summary . 4 1.1. Requirements & Research Motivation . 4 1.2. Prior-After Comparison. 4 1.3. Recommendations for Future Work . 5 1.4. What does this ER mean for the Working Group and OGC in general . 6 1.5. Document contributor contact points . 6 1.6. Foreword . 6 2. References . 8 3. Terms and definitions . 9 3.1. Semantics . 9 3.2. Service Description. 9 3.3. Service-Oriented Architecture (SOA) . 9 3.4. Registry . 9 3.5. System Wide Information Management (SWIM) . 9 3.6. Taxonomy . 9 3.7. Web Service . 10 4. Abbreviated Terms . 11 5. Overview . 12 6. Review of Data Models . 13 6.1. Information Exchange Models . 13 6.1.1. Flight Information Exchange Model (FIXM). 13 6.1.2. Aeronautical Information Exchange (AIXM) Model. 13 6.1.3. Weather Information Exchange Model (WXXM) . 14 6.1.4. NASA Air Traffic Management (ATM) Model . 14 6.2. Service description models . 19 6.2.1. Service Description Conceptual Model (SDCM) . 19 6.2.2. Web Service Description Ontological Model (WSDOM). 23 6.2.3. SWIM Documentation Controlled Vocabulary (FAA) . 25 7. Semantic Enablement Approaches . 27 8. Metadata level semantic enablement . 33 8.1. Issues with existing metadata standards . 34 8.1.1. Identification of Resources. 34 8.1.2. Resolvable URI. 34 8.1.3. Multilingual Support . 35 8.1.4. External Resource Descriptions . 35 8.1.5. Controlled Vocabulary Management . 36 8.1.6. Keywords Types . 37 8.1.7. Keyword Labeling Inconsistencies .
    [Show full text]
  • The Semantic Asset Administration Shell
    The Semantic Asset Administration Shell Sebastian R. Bader and Maria Maleshkova Fraunhofer Institute IAIS, Schloss Birlinghoven, 53757 Sankt Augustin, Germany University of Bonn, Endenicher Allee 19a, 53115 Bonn, Germany Abstract The disruptive potential of the upcoming digital transformations for the industrial manufacturing domain have led to several reference frameworks and numerous standardization approaches. On the other hand, the Semantic Web community has made significant contributions in the field, for instance on data and service description, integration of heterogeneous sources and devices, and AI techniques in distributed systems. These two streams of work are, however, mostly unrelated and only briefly regard each others requirements, practices and termi- nology. We contribute to closing this gap by providing the Semantic Asset Administration Shell, an RDF-based representation of the Indus- trie 4.0 Component. We provide an ontology for the latest data model specification, created a RML mapping, supply resources to validate the RDF entities and introduce basic reasoning on the Asset Admin- istration Shell data model. Furthermore, we discuss the different as- sumptions and presentation patterns, and analyze the implications of a semantic representation on the original data. We evaluate the thereby created overheads, and conclude that the semantic lifting is manage- able, also for restricted or embedded devices, and therefore meets the needs of Industrie 4.0 scenarios. 1 Introduction Even though the various digital developments and
    [Show full text]
  • Semantics Enhanced Services: METEOR-S, SAWSDL and SA-REST
    Semantics Enhanced Services: METEOR-S, SAWSDL and SA-REST Amit P. Sheth, Karthik Gomadam, Ajith Ranabahu Services Research Lab, kno.e.sis center, Wright State University, Dayton, OH {amit,karthik, ajith}@knoesis.org Abstract Services Research Lab at the Knoesis center and the LSDIS lab at University of Georgia have played a significant role in advancing the state of research in the areas of workflow management, semantic Web services and service oriented computing. Starting with the METEOR workflow management system in the 90’s, researchers have addressed key issues in the area of semantic Web services and more recently, in the domain of RESTful services and Web 2.0. In this article, we present a brief discussion on the various contributions of METEOR-S including SAWSDL, publication and discovery of semantic Web services, data mediation, dynamic configuration and adaptation of Web processes. We finally discuss our current and future research in the area of RESTful services. 1 Overview Our body of research can be divided into three major phases. The first phase related to the METEOR (for “Managing End To End OpeRations”) system [6] focused on workflow management and addressed issues of formal modeling, centralized as well as distributed scheduling and execution (including exception handling, security, survivability, scalability and adaptation). The work yielded two notable frameworks:1)WebWork [7], a Web based implementation and 2) ORBWork, a CORBA based implementation. The METEOR project initally started at BellCore in 1990 and was continued at the LSDIS lab until 1998. A commercial spinoff, Infocosm, inc. and the product METEOR EAppS (for Enterprise Application Suite) are other notable accomplishments.
    [Show full text]
  • Requirements for an Ontology Supporting Certificates Interoperability
    ASSERT4SOA Advanced Security Service cERTificate for SOA CP - STREP - Grant No. 257351 Requirements for an ontology supporting certificates interoperability Deliverable D3.1 Rev. 1.0 Legal Notice All information included in this document is subject to change without notice. The Members of the As- sert4Soa Consortium make no warranty of any kind with regard to this document, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. The Members of the Assert4Soa Consortium shall not be held liable for errors contained herein or direct, indirect, special, incidental or consequential damages in connection with the furnishing, performance, or use of this material. Assert4Soa Project Title Assert4Soa - Advanced Security Service cERTificate for SOA Grant Number 257351 Project Type CP - STREP Requirements for an ontology supporting cer- Title of Deliverable tificates interoperability Subtitle of Deliverable Deliverable No. D3.1 Dissemination Level Public Internal Rev. No. 1.0 Contractual Delivery 30 September 2011 Date Actual Delivery Date 30 September 2011 Contributing WPs WP3 Editor(s) Claudia Pandolfo (ENG), Domenico Presenza (ENG) Author(s) Marco Anisetti (UNIMI), Claudio A. Ardagna (UNIMI), Ernesto Damiani (UNIMI), Stefa- nia D'Agostini (ENG), Valentina Di Giacomo (ENG), Claudia Pandolfo (ENG), Domenico Presenza (ENG), Antonino Sabetta (SAP), Gimena Pujol (UMA) Reviewer(s) Renato Menicocci (FUB), Zaharina Stoynova (SIT) D3.1 - Requirements for an ontology supporting certificates interoperability 3 / 69 Executive Summary The objective of this document is to present the requirements for an ontology suitable to support some of the functionalities envisaged for the ASSERT4SOA software infrastructure. Broadly speaking an ontology can be understood as a description, given in a formal language, of part of the world (a domain) with the purpose to give a firm basis to the language that a community of agents (either human or computational) shares to predicate about that part of the world.
    [Show full text]
  • Building the WSMO-Lite Test Collection on the SEALS Platform
    Building the WSMO-Lite Test Collection on the SEALS Platform Liliana Cabral, Ning Li, and Jacek Kopeck´y KMI, The Open University Milton Keynes, UK {L.S.Cabral,N.Li,J.Kopecky}@open.ac.uk Abstract. We present a test collection for WSMO-Lite that is suitable for evaluating systems, tools or algorithms for Semantic Web Service discovery or matchmaking. We describe the design of the test collection and how the collection has been implemented on the SEALS platform. In addition, we discuss lessons learned with respect to the WSMO-Lite ontology and our implementation of the test collection. Keywords: Semantic Web Service Evaluation, WSMO-Lite, Test col- lection, Service Discovery, Service matchmaking 1 Introduction Semantic Web Service (SWS) technologies enable the automation of discovery, selection, composition, mediation and execution of Web Services by means of semantic descriptions of their interfaces, capabilities and non-functional proper- ties. SWS build on Web service standards such as WSDL1, SOAP2 and REST (HTTP), and as such provide a layer of semantics for service interoperability. Current results of SWS research and industry efforts include a number of ref- erence service ontologies, such as OWL-S3, WSMO4 and WSMO-Lite5 and se- mantic annotation extension mechanisms, as provided by SAWSDL6, SA-REST7 and MicroWSMO8. The SWS discovery activity consists of finding Web Services based on their semantic descriptions. Tools for SWS discovery or matchmaking can be evaluated on retrieval performance, where for a given goal, i.e. a semantic
    [Show full text]
  • Rule Interchange on the Web
    Rule Interchange on the Web Harold Boley1, Michael Kifer2, Paula-Lavinia P˘atrˆanjan3, and Axel Polleres4 1 University of New Brunswick, Faculty of Computer Science Institute for Information Technology - e-Business, NRC 46 Dineen Drive, Fredericton, Canada [email protected] http://www.cs.unb.ca/ boley/ 2 State University of New York at Stony Brook Department of Computer Science Stony Brook, New York 11794-4400, USA [email protected] http://www.cs.sunysb.edu/ kifer/ 3 University of Munich, Institute for Informatics Oettingenstr. 67, D-80538 M¨unchen [email protected] http://www.pms.ifi.lmu.de 4 Digital Enterprise Research Institute National University of Ireland, Galway [email protected] http://www.polleres.net/ Abstract. Rules play an increasingly important role in a variety of Se- mantic Web applications as well as in traditional IT systems. As a univer- sal medium for publishing information, the Web is envisioned to become the place for publishing, distributing, and exchanging rule-based knowl- edge. Realizing the importance and the promise of this vision, W3C has created the Rule Interchange Format Working Group (RIF WG) and chartered it to develop an interchange format for rules in alignment with the existing standards in the Semantic Web architecture stack. However, creating a generally accepted interchange format is by no means a trivial task. First, there are different understandings of what a “rule” is. Researchers and practitioners distinguish between deduction rules, nor- mative rules, production rules, reactive rules, etc. Second, even within the same category of rules, systems use different (often incompatible) semantics and syntaxes.
    [Show full text]
  • Injecting Semantic Annotations Into (Geospatial) Web Service Descriptions
    Undefined 0 (0) 1 1 IOS Press Injecting semantic annotations into (geospatial) Web service descriptions Editor(s): Thomas Lukasiewicz, University of Oxford, UK Solicited review(s): Jacek Kopecký, The Open University, UK; Tudor Groza, The University of Queensland, Australia; Marinos Kavouras, National Technical University of Athens, Greece Patrick Maué a Henry Michels a and Marcell Roth a a Institute for Geoinformatics (ifgi) University of Münster, Germany Weseler Str. 253 48151 Münster Germany e-mail: fi[email protected] Abstract. Geospatial Web services comply with well- 1. Introduction established standards to support seamless integration into applications ranging from commercial Geographic Efficient discovery relies on search engines with Information Systems (GIS) to open source web map- sophisticated indexing and scoring techniques. ping clients. Descriptions of service capabilities con- These techniques can not be simply applied on tain information about the provided data. Updates to structured data without textual content such as the underlying database result in changing descrip- tions. To ensure compatibility with existing solutions, geospatial data, or any kind of binary data, in- semantic enablement of Geospatial Web services has cluding pictures or videos. Finding such content to reflect both, standards and changing metadata. Se- relies on annotations which associate descriptive mantic annotations link between legacy non-semantic metadata with the resource [1]. The metadata is Web service descriptions and their semantic counter- then again used for common indexing and scor- parts. The open source Semantic Annotations Proxy ing techniques. Semantic annotations link to for- (SAPR) is a light-weight RESTful API deployed as mally specified vocabularies capturing the con- free service which “injects” semantic annotations into tent’s meaning.
    [Show full text]
  • Leveraging Semantic Web Service Descriptions for Validation by Automated Functional Testing
    Leveraging Semantic Web Service Descriptions for Validation by Automated Functional Testing Ervin Ramollari1, Dimitrios Kourtesis1, Dimitris Dranidis2, and Anthony J.H. Simons3 1 South East European Research Centre (SEERC), Research Centre of the University of Sheffield and CITY College Mitropoleos 17, 54624, Thessaloniki, Greece [email protected], [email protected] 2 Computer Science Department, CITY College, Affiliated Institution of the University of Sheffield Tsimiski 13, 54624 Thessaloniki, Greece [email protected] 3 Department of Computer Science, University of Sheffield Regent Court, 211 Portobello Street, Sheffield S1 4DP, UK [email protected] Abstract. Recent years have seen the utilisation of Semantic Web Service de- scriptions for automating a wide range of service-related activities, with a pri- mary focus on service discovery, composition, execution and mediation. An important area which so far has received less attention is service validation, whereby advertised services are proven to conform to required behavioural specifications. This paper proposes a method for validation of service-oriented systems through automated functional testing. The method leverages ontology- based and rule-based descriptions of service inputs, outputs, preconditions and effects (IOPE) for constructing a stateful EFSM specification. The specification is subsequently utilised for functional testing and validation using the proven Stream X-machine (SXM) testing methodology. Complete functional test sets are generated automatically at an abstract level and are then applied to concrete Web services, using test drivers created from the Web service descriptions. The testing method comes with completeness guarantees and provides a strong method for validating the behaviour of Web services. Keywords: Semantic Web Services, Web service testing, Service Validation.
    [Show full text]
  • FAA Web Service Description Ontological Model (WSDOM) – an Introduction
    Federal Aviation Administration FAA Web Service Description Ontological Model (WSDOM) – an Introduction Presented to: Semantic Web for Air Transportation (SWAT) interest group By: Mark Kaplun (FAA) Date: August 24, 2015 Agenda . Context . Problem . Solution . Architecture . Application SWAT Meeting 2 August 24, 2015 Context . SWIM - A technological framework for making available a wide range of capabilities in Air Traffic Management information domain through a common infrastructure of reusable and shared services with consistent application of principals of Service-Oriented Architecture (SOA). Service Description – A key ingredient of SOA; a document representing information that is necessary for using a service or considering using the service. The notion of service description is central to the service discovery process. For every service to be usable, a service description for this service must exist and be discoverable. SWAT Meeting 3 August 24, 2015 Problem . The current service description standards (e.g., WSDL, OWS and XML Schema) operate almost entirely at the syntactic level, focusing only on describing exposed functionality (methods signatures, input/output types) and failing to capture enough semantics (i.e., they define structure, not meaning). The standards for free-text, human-consumable documents, (e.g., FAA’s WSDD), support a sufficient amount of semantics but are not suitable for automated discovery and provide very limited support for semantic interoperability. SWAT Meeting 4 August 24, 2015 Solution Develop an ontology (“a formal, explicit specification of shared conceptualization”*) that: . Presents all relevant aspects of services in a manner suitable for semantic software agents and humans. Adopts industry service description standards and models to take advantage of future adaptations by business partners and vendors.
    [Show full text]