Browse Prior Art Database

Common Visual Representation of Web Services

IP.com Disclosure Number: IPCOM000238119D
Publication Date: 2014-Aug-03
Document File: 6 page(s) / 168K

Publishing Venue

The IP.com Prior Art Database

Abstract

Due to conceptual differences betweet resource-based and procedural-based service a common visual representation is challanging. We defined a common description language that can describe both REST and SOAP based web services. A service descriptor is a well structured XML instance and uses an embedded XML Schema to define the messages and resources types. We also designed a common visual representation of the web services that rely on the former description language to allow end users to visually map data object to/from web services indifferently of the service type .

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 39% of the total text.

Page 01 of 6

Common Visual Representation of Web Services

When working with web services one can split those into two main methodologies - REST and SOAP based services. RESTful services are based on HTTP verbs to manage the life cycle of resource that are being serialized in the format of JSON or XML messages. On the other hand a SOAP-based web service mainly refers to services that are well defined using a WSDL and transportation layer is based on the SOAP standard with, mainly, XML based payloads. Therefore there is a conceptual difference between the two as RESTful service is a way to manage resources on the back-end while SOAP services are remote procedural calls (RPC) to invoke functionality on the back-end. SOAP based service are usually being described using the WSDL standard (v1.x / 2.0). This is not the case for REST as there is no commonly used description language for the services although several were suggested in the past (e.g. WSDL 2.0 and WADL).

Because of those major differences developing an application that allows user to integrate the services invocation into the generated application is challenging. Usually there is no common representation for the services and the developer needs to choose between the two types. In a system where a Business/Data Objects needs to be mapped to back-end service currently there is no common way of visually presenting the input/output of the services to be mapped into the BO/DO fields.

WSDL 2.0 is trying to address the two different methodology by defining a description language that can describe both REST and SOAP based web services. However, this version of the standard hasn't been adapted by the community and RESTful services are rarely being described using this language. Therefore making it impossible to rely on this standard as a common representation language that can be the basis for visually representing the services. Furthermore, WSDL 2.0 is not backward compatible

with WSDL v1.x and it require transformation between the revisions.

We developed a common description language that can describe both REST and SOAP based web services. The description language is based on well known XML Schema language to define the messages and resources. We also developed a visual representation of the web services that rely on the former description language to allow end users to visually map data object to/from web services indifferently of the type . Background
Our application is assisting a developer in building a mobile application rapidly and

without writing code. It was beta released within IBM Worklight* Studio v6.1 and named Worklight* Application Framework.

Major functionality of this component allows a developer to discover web services and integrate those into a mobile application by mapping the service payload to Business Object. The Business Object (a data model) is then mapped to application views for gathering and presenting the data to the end-user. The development environment support bot...