Soa4 all technical achievements final

Technical Achievements
Sven Abels, Sudhir Agarwal, John Domingue,
Yosu Gorroñogoitia and Jacek Kopecký

Final Review Meeting
May 2011, Brussels

Agenda

• Web services and Web data
• Achievements
• New Actions
– Multimedia search
– Mobile Application
– OSS Packaging
– University of Seville
• OSS Explanations
• Conclusions
2

REST vs SOAP Update

4

REST vs SOAP API Searches

SOA4All started here

5
http://www.google.com/insights/search/#q=soap%20api%2Crest%20api&cmpt=q

Sample Data Suppliers

Good relations
Open Graph
Programmes, world cup
website
Data.gov.uk
Ravensburg, DE
Courses, research outputs ->
data.ac.uk
6

(WP2)
LPML Analysis &
SWEET & SOWER (WP2) deployment
Discovery Monitoring SPICES
(WP5) (WP2, 1) (WP2)

Process Editor (WP2)

incl. BPEL-based execution
environment (WP6, 1)
incl. TG, Optimizer, DTC
(WP6)

Process
modeling
(WP6, 2, 5)
Service Process
annotatio SOA4All execution
n (WP6, 1, 2)
(WP2) Process Lifecycle

Minimal Service Model, WSMO-Lite

WSMO-Lite Submission

• W3C Member Submission as of 23 August 2010
– http://www.w3.org/Submission/WSMO-Lite/

• Director's Acknowledgment received on 14 September
2010
– "It is a useful addition to SAWSDL for annotations of
existing services and the combination of both
techniques can certainly be applied to a large number
of semantic Web services use cases."

USDL Incubator Activity

13

USDL -> RDF

:AbstractService
rdf:type rdfs:Class ;
rdfs:comment "AbstractService is used to represent 'classes' of services,
i.e. groups of services that share a number of characteristics. AbstractService
enables the capturing of these characteristics as a set (configuration) of
predefined description properties (USDL objects)." ;
rdfs:isDefinedBy <http://www.w3.org/TR/usdl/service> ;
rdfs:label "Abstract Service" ;
rdfs:subClassOf gr:ProductOrServiceModel .

:AbstractServiceType
rdf:subClassOf skos:Concept ;
rdfs:comment "Types of Abstract Service. Schemes for classifying Abstract
Service should start from here" ;
skos:prefLabel "Abstract Service Type"@en .

:ComposableEntity
rdfs:comment "Composable serves as the super type of all USDL classes
that can be included in a composite service or service bundle. Valid classes
are Service, ServiceBundle and AbstractService." ;
rdfs:label "Composable Entity" .

:CompositeService
rdfs:comment "A CompositeService is a special type of Service that
aggregates other services, service bundles or abstract services. Unlike service
bundles, which group services for single-point selling, composite services
provide new functionality by combining the capabilities of their parts." ;
rdfs:subClassOf gr:ProductOrServicesSomeInstancesPlaceholder ,
:Service .

14

Chapter in every FIA Book

SO4All Editor for every book too

18

D 2.8.1 Multimedia Semantic
Search Tool
Annomation and SugarTube

SugarTube Architecture

Mashup layer

(1) (2) (3) (4) (5) (6)

Linked Service layer
Annomation video
annotation RDF SPARQL Invocation
repository query API API

(1) Query Annomation repository
(2) Return query result
(3) Query services via iServe
(4) Return service endpoints
(5) Invoke services via iServe
(6) Return services’ responses

D9.4.3 OpenData/Mobile Prototype
(SOA4All Real Estate Finder)

Description

• New action with budget that was left: Not in DOW; completely new, no additional costs

• Content:
– Usage of SOA4All components in a mobile environment:
service discovery, composition, execution

– Usage of Open Data initiatives including mobile environments with SOA4All
technologies; Usage of Data for localized information (e.g. bus stations…)

– Provision of a mobile application for assessing real estate investments

• Why Real Estate?

• All Services from data.gov.uk initiative
27

Description

What does it mean?
•User View:
– Application for finding real estate offers with an iPhone App
– based on querying localized information

•SOA4All View:
– Validation of components in real-world mobile use case,
– creation of backend components optimized for mobile use

•Developer View:
– Provision of examples on how to use SOA4All in iPhone apps on the code level.
– Components are adopting their view based on service descriptions.
– All source code (including the iPhone app) is opened:
https://sourceforge.net/projects/soa4re/

30

User View

Scenario from User Perspectiove

1. User starts app on his iPhone and selects a location

2. User enters criteria, e.g. looking for a house with 5 rooms

3. User refines search with location based criteria, e.g. Looking for a house in a
low crime area of london with a bus stop located in the neigborhood

4. User gets combined results and explores them on a map

31

Frontend Demo

Demo

32

Usage of SOA4All

What is the role of SOA4All in the scenario?

•Service Annotation & iServe
– For annotating restful and SOAP based services and publishing them in iServe

•Service Discovery
– For finding location based services automatically
– For wrapping service descriptions into XML for better consumption on iPhone side
– Dynamic creation of forms on top on the discovery results! (beta, exploitable)

•Services and data stores coming from UK Open Data Initiatives
e.g. Nestoria, Schools, Bus Stations, Train Stations…

•Service Execution

37

Behind the Scenes

Services
Services
Services iServe iPhone Client
Meta-
data
Discovery

38

Behind the Scenes

{
Real Estate Service
"Nestoria"
REST Mashup

Bus Stop Service
Not iServe SOA4Re Server Side iPhone Client
from Meta-
us data
Train Station Discovery
Service

School Service
SparQL Request
Server

39

Status

• 2 Prototypes have been finished

• Really working (unlike in other projects ;-))

• Version 1.0 already accepted by Apple and listed in the official Apple AppStore
• Version 2.0 under submission
• Works on iPhone (iOS 4.3) and iPad

• Listed at data.gov.uk initiative / Website as featured App

• Source opened: https://sourceforge.net/projects/soa4re

40

Status

• Officially listed at data.gov.uk as example app for open webservices

• http://data.gov.uk/apps/soa4all-real-estate-finder

42

Open Source Software

• SOA4All OSS Packaging Installer
– Installs SOA4All Studio tools and platform services.
– A separate installer available for fDSB
– Available soon on soa4all.eu under Apache and LGPL licenses
• Scenarios for local deployment by third parties
– Private deployment (e.g. private registry)
– Development: contributing features and fixes
• Sources available
– http://sourceforge.net/projects/soa4all-st-core
– http://fdsb.gforge.inria.fr/
– https://github.com/liudong/iserve
– https://github.com/mmale/sweet
– …
44

SOA4All ranking before US…

• Eclectic ranking
– Preferences
cannot be
combined
– Three user
interfaces
– Some
unexploited
synergies

46

… and after US

• Holistic ranking
– Preferences can
be combined
– Single user
interface
– Ranking
approaches are
integrated

47

OSS Explanation

• A holistic view on using the major tools
– Illustrated by a comprehensive scenario
– Outside the formal Use Cases
– In other scenarios, tools can be mixed and
matched
• Covering SWS lifecycle

OSS Explanation Scenario

A provider with local knowledge…
example: bank service for ATM locations
…wants it service to be used.
semantic annotation, publishing

The service is visible to a client…
discovery, ranking
…who reuses it in a complex process.
composition

50

Service Annotation and Publishing

Implement
service:
WSDL or
REST

WSDL: REST:
SAWSDL MicroWSMO
annotations, annotations,
SOWER SWEET

Semantic
registry:
iServe

Service Discovery and Ranking

Broad
matching by
Functional
Classification

Input / Output
Ranking Condition /
Effect

Consumption
/ Composition


New functional
taxonomy,
unforeseen
during use
cases


New functional
taxonomy,
unforeseen
during use
cases

Finer-grained
classification
reduces
number of
results


Price is a Availability is
static NFP obtained from
seekda public service


Chosen
operation can
be
communicated
through toolset
using
favourites list

Service Composition

• Goal: Creating a service for setting a call to a particular Point Of
Interest (POI)

• Roles: Business modeller, Process annotator

• Requirements:
Third Party Semantic Domain Process
Services Descriptions Ontologies Models
iServe

• Result: a executable process accepting incoming requests
(consumption)

• Related Scenarios: service annotation (provisioning), service
discovery, service consumption

Service Composition: Phases

Process
Modelling

Process
Process
Consumption
Deployment
(Execution)

Process
Annotation

Composition: Process Modelling

Composition: Process Deployment

Composition: Process Execution

• The process can be consumed using SOA4All SPICES
• Execution runs within the SOA4All Execution Environment.
• The process execution can be monitored using SOA4All Monitoring platform

Before SOA4All

– 1.8B users
– more than 1 trillion pages

Static
WWW
URI, HTML, HTTP

Before SOA4All

Supporting machine
delegation and
interoperability
• search
• extraction
• representation
• interpretation
• maintenance

Static
WWW Semantic Web
URI, HTML, HTTP RDF, RDF(S), OWL

Before SOA4All

Dynamic Web Services
UDDI, WSDL, SOAP
Enable computation
over the Web

Static
WWW Semantic Web

Before SOA4All

Automated Web Service Usage

Dynamic Web Services Semantic Web
UDDI, WSDL, SOAP Services

Static
WWW Semantic Web

After SOA4All

Dynamic REST!
Web Services Semantic Web
UDDI, WSDL, SOAP Services

Static
WWW Semantic Web

Conclusions

• Web of data is here
• Rest services dominate the Web
• SOA4All technologies uniquely
– Align service descriptions with Web of Data
– Abstract over service technologies on the
Web
– Supported by a comprehensive suite of
easy-to-use tools
103

Soa4 all technical achievements final

Recommandé

Recommandé

Contenu connexe

En vedette

En vedette (13)

Similaire à Soa4 all technical achievements final

Similaire à Soa4 all technical achievements final (20)

Plus de John Domingue

Plus de John Domingue (10)

Dernier

Dernier (20)

Soa4 all technical achievements final

Notes de l'éditeur