Downloaded 10 times
Uploaded byJohn Domingue
Soa4 all technical achievements final
Sven Abels and colleagues presented achievements and new actions from the SOA4All project. Key achievements included the development of MicroWSMO and WSMO-Lite for semantic service annotations, contributions to the USDL incubator activity, and the creation of a real estate finder mobile application using open data. New actions proposed expanding the multimedia search tool, further mobile prototypes, releasing an open source software packaging installer, and providing explanations of using the SOA4All tools together in scenarios.
More Related Content
Similar to Soa4 all technical achievements final
Soa4 all technical achievements final
- 1. Technical Achievements Sven Abels,Sudhir Agarwal, John Domingue, Yosu Gorroñogoitia and Jacek Kopecký Final Review Meeting May 2011, Brussels
- 2. Agenda • Web servicesand Web data • Achievements • New Actions – Multimedia search – Mobile Application – OSS Packaging – University of Seville • OSS Explanations • Conclusions 2
- 3. Web Services andWeb Data
- 4. REST vs SOAPUpdate 4
- 5. REST vs SOAPAPI Searches SOA4All started here 5 http://www.google.com/insights/search/#q=soap%20api%2Crest%20api&cmpt=q
- 6. Sample Data Suppliers Good relations Open Graph Programmes, world cup website Data.gov.uk Ravensburg, DE Courses, research outputs -> data.ac.uk 6
- 7.
- 9. (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
- 10.
- 11. Minimal Service Model,WSMO-Lite
- 12. WSMO-Lite Submission • W3CMember 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."
- 13.
- 14. 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" ; rdfs:isDefinedBy <http://www.w3.org/TR/usdl/service> ; skos:prefLabel "Abstract Service Type"@en . :ComposableEntity rdf:type rdfs:Class ; 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:isDefinedBy <http://www.w3.org/TR/usdl/service> ; rdfs:label "Composable Entity" . :CompositeService rdf:type rdfs:Class ; 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:isDefinedBy <http://www.w3.org/TR/usdl/service> ; rdfs:subClassOf gr:ProductOrServicesSomeInstancesPlaceholder , :Service . 14
- 17.
- 18. Chapter in everyFIA Book SO4All Editor for every book too 18
- 19.
- 20.
- 21.
- 22. D 2.8.1 MultimediaSemantic Search Tool Annomation and SugarTube
- 23.
- 24. SugarTube 24
- 25. 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
- 26. D9.4.3 OpenData/Mobile Prototype (SOA4All Real Estate Finder)
- 27. 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
- 28. Description What does itmean? •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
- 29. User View Scenario fromUser 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
- 30. Frontend Demo Demo 32
- 31. Usage of SOA4All Whatis 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
- 32. Behind the Scenes Services Services Services iServe iPhone Client Meta- data Discovery 38
- 33. 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
- 34. 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
- 36. Status • Officially listed at data.gov.uk as example app for open webservices • http://data.gov.uk/apps/soa4all-real-estate-finder 42
- 37.
- 38. 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
- 39.
- 40. SOA4All ranking beforeUS… • Eclectic ranking – Preferences cannot be combined – Three user interfaces – Some unexploited synergies 46
- 41. … and afterUS • Holistic ranking – Preferences can be combined – Single user interface – Ranking approaches are integrated 47
- 42.
- 43. OSS Explanation • Aholistic 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
- 44. OSS Explanation Scenario Aprovider 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
- 45. Service Annotation andPublishing Implement service: WSDL or REST WSDL: REST: SAWSDL MicroWSMO annotations, annotations, SOWER SWEET Semantic registry: iServe
- 46.
- 47.
- 48.
- 49.
- 50.
- 51.
- 52.
- 53.
- 54.
- 55. Service Discovery andRanking Broad matching by Functional Classification Input / Output Ranking Condition / Effect Consumption / Composition
- 56. Service Discovery andRanking
- 57. Service Discovery andRanking New functional taxonomy, unforeseen during use cases
- 58. Service Discovery andRanking New functional taxonomy, unforeseen during use cases
- 59. Service Discovery andRanking New functional taxonomy, unforeseen during use cases
- 60. Service Discovery andRanking New functional taxonomy, unforeseen during use cases Finer-grained classification reduces number of results
- 61. Service Discovery andRanking Price is a Availability is static NFP obtained from seekda public service
- 62. Service Discovery andRanking
- 63. Service Discovery andRanking
- 64. Service Discovery andRanking Chosen operation can be communicated through toolset using favourites list
- 65. 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
- 66. Service Composition: Phases Process Modelling Process Process Consumption Deployment (Execution) Process Annotation
- 67.
- 68.
- 69.
- 70.
- 71.
- 72.
- 73.
- 74.
- 75.
- 76.
- 77.
- 78.
- 79.
- 80.
- 81.
- 82.
- 83.
- 84.
- 85.
- 86.
- 87.
- 88.
- 89.
- 90. 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
- 91.
- 92. Before SOA4All – 1.8B users – more than 1 trillion pages Static WWW URI, HTML, HTTP
- 93. Before SOA4All Supporting machine delegation and interoperability • search • extraction • representation • interpretation • maintenance Static WWW Semantic Web URI, HTML, HTTP RDF, RDF(S), OWL
- 94. Before SOA4All Dynamic Web Services UDDI, WSDL, SOAP Enable computation over the Web Static WWW Semantic Web URI, HTML, HTTP RDF, RDF(S), OWL
- 95. Before SOA4All Automated Web Service Usage Dynamic Web Services Semantic Web UDDI, WSDL, SOAP Services Static WWW Semantic Web URI, HTML, HTTP RDF, RDF(S), OWL
- 96. After SOA4All Dynamic REST! Web Services Semantic Web UDDI, WSDL, SOAP Services Static WWW Semantic Web URI, HTML, HTTP RDF, RDF(S), OWL
- 97. Conclusions • Web ofdata 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
Editor's Notes
- #17 notification mechanism developed in WP1 of of SOA4All is an important feature of BigOWLIM 3.3 - over the last couple of years we had several requests from commercial customers for such mechanism.