1.Technical AchievementsSven Abels, Sudhir Agarwal, John Domingue,Yosu Gorroogoitia and Jacek KopeckFinal Review MeetingMay 2011, Brussels

2. Agenda Web services and Web data Achievements New Actions Multimedia search Mobile Application OSS Packaging University of Seville OSS Explanations Conclusions2 3. Web Services and Web Data 4. REST vs SOAP Update4 5. REST vs SOAP API Searches SOA4All started here5http://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.uk6 7. Achievements 8. (WP2)LPMLAnalysis &SWEET & SOWER (WP2) deployment DiscoveryMonitoring SPICES (WP5)(WP2, 1) (WP2)Process Editor (WP2) incl. BPEL-based executionenvironment (WP6, 1) incl. TG, Optimizer, DTC (WP6)Processmodeling(WP6, 2, 5)Service Process annotatio SOA4All execution n(WP6, 1, 2) (WP2) Process Lifecycle 9. MicroWSMO & WSMO-Lite 10. Minimal Service Model, WSMO-Lite 11. WSMO-Lite Submission W3C Member Submission as of 23 August 2010 http://www.w3.org/Submission/WSMO-Lite/ Directors Acknowledgment received on 14 September2010 "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." 12. USDL Incubator Activity13 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. AbstractServiceenables the capturing of these characteristics as a set (configuration) ofpredefined description properties (USDL objects)." ; rdfs:isDefinedBy ; rdfs:label "Abstract Service" ; rdfs:subClassOf gr:ProductOrServiceModel .:AbstractServiceType rdf:subClassOf skos:Concept ; rdfs:comment "Types of Abstract Service. Schemes for classifying AbstractService should start from here" ; rdfs:isDefinedBy ; skos:prefLabel "Abstract Service Type"@en .:ComposableEntityrdf:type rdfs:Class ;rdfs:comment "Composable serves as the super type of all USDL classesthat can be included in a composite service or service bundle. Valid classesare Service, ServiceBundle and AbstractService." ;rdfs:isDefinedBy ;rdfs:label "Composable Entity" .:CompositeService rdf:type rdfs:Class ; rdfs:comment "A CompositeService is a special type of Service thataggregates other services, service bundles or abstract services. Unlike servicebundles, which group services for single-point selling, composite servicesprovide new functionality by combining the capabilities of their parts." ; rdfs:isDefinedBy ; rdfs:subClassOf gr:ProductOrServicesSomeInstancesPlaceholder ,:Service .14 14. 17 15. Chapter in every FIA BookSO4All Editor for every book too 18 16. Training Movie 19 17. SOA4All Movie20 18. New Actions 19. D 2.8.1 Multimedia SemanticSearch Tool Annomation and SugarTube 20. 23 21. SugarTube24 22. SugarTube ArchitectureMashup layer (1)(2) (3)(4)(5) (6) Linked Service layer Annomation videoannotation RDF SPARQL Invocationrepository 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 23. D9.4.3 OpenData/Mobile Prototype (SOA4All Real Estate Finder) 24. 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 25. DescriptionWhat does it mean?User View: Application for finding real estate offers with an iPhone App based on querying localized informationSOA4All View: Validation of components in real-world mobile use case, creation of backend components optimized for mobile useDeveloper 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 26. User ViewScenario from User Perspectiove1. User starts app on his iPhone and selects a location2. User enters criteria, e.g. looking for a house with 5 rooms3. 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 neigborhood4. User gets combined results and explores them on a map 31 27. Frontend DemoDemo32 28. Usage of SOA4AllWhat is the role of SOA4All in the scenario?Service Annotation & iServe For annotating restful and SOAP based services and publishing them in iServeService 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 Initiativese.g. Nestoria, Schools, Bus Stations, Train StationsService Execution 37 29. Behind the ScenesServices ServicesServicesiServe iPhone Client Meta- data Discovery 38 30. Behind the Scenes{ Real Estate Service "Nestoria"REST MashupBus Stop Service Not iServe SOA4Re Server SideiPhone ClientfromMeta-usdataTrain Station Discovery Service School ServiceSparQL RequestServer 39 31. 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/soa4re40 32. Status Officially listed at data.gov.uk as example app for open webservices http://data.gov.uk/apps/soa4all-real-estate-finder 42 33. OSS Packaging 34. 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 35. University of Seville 36. SOA4All ranking before US Eclectic ranking Preferencescannot becombined Three userinterfaces Someunexploitedsynergies 46 37. and after US Holistic ranking Preferences canbe combined Single userinterface Rankingapproaches areintegrated 47 38. OSS Explanations 39. 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 andmatched Covering SWS lifecycle 40. OSS Explanation ScenarioA provider with local knowledge example: bank service for ATM locationswants it service to be used. semantic annotation, publishingThe service is visible to a client discovery, rankingwho reuses it in a complex process. composition 50 41. Service Annotation and PublishingImplement service:WSDL or REST WSDL:REST:SAWSDLMicroWSMO annotations, annotations, SOWERSWEETSemanticregistry: iServe 42. Service Annotation 43. Service Annotation 44. Service Annotation 45. Service Annotation 46. Service Annotation 47. Service Annotation 48. Service Annotation 49. Service Annotation 50. Service Registry 51. Service Discovery and Ranking Broadmatching by FunctionalClassification Input / OutputRanking Condition /EffectConsumption/ Composition 52. Service Discovery and Ranking 53. Service Discovery and RankingNew functionaltaxonomy,unforeseenduring usecases 54. Service Discovery and RankingNew functionaltaxonomy,unforeseenduring usecases 55. Service Discovery and RankingNew functionaltaxonomy,unforeseenduring usecases 56. Service Discovery and RankingNew functionaltaxonomy,unforeseenduring usecasesFiner-grainedclassificationreducesnumber ofresults 57. Service Discovery and RankingPrice is a Availability isstatic NFPobtained from seekda public service 58. Service Discovery and Ranking 59. Service Discovery and Ranking 60. Service Discovery and RankingChosenoperation canbecommunicatedthrough toolsetusingfavourites list 61. Service Composition Goal: Creating a service for setting a call to a particular Point OfInterest (POI) Roles: Business modeller, Process annotator Requirements: Third PartySemantic DomainProcessServices Descriptions Ontologies Models iServe Result: a executable process accepting incoming requests(consumption) Related Scenarios: service annotation (provisioning), servicediscovery, service consumption 62. Service Composition: Phases Process Modelling Process ProcessConsumptionDeployment (Execution)Process Annotation 63. Composition: Process Modelling 64. Composition: Process Modelling 65. Composition: Process Modelling 66. Composition: Process Modelling 67. Composition: Process Modelling 68. Composition: Process Modelling 69. Composition: Process Modelling 70. Composition: Process Modelling 71. Composition: Process Modelling 72. Composition: Process Modelling 73. Composition: Process Modelling 74. Composition: Process Modelling 75. Composition: Process Modelling 76. Composition: Process Modelling 77. Composition: Process Modelling 78. Composition: Process Modelling 79. Composition: Process Modelling 80. Composition: Process Modelling 81. Composition: Process Modelling 82. Composition: Process Modelling 83. Composition: Process Modelling 84. Composition: Process Modelling 85. Composition: Process Deployment 86. 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 87. Conclusion 88. Before SOA4All 1.8B users more than 1 trillion pagesStatic WWW URI, HTML, HTTP 89. Before SOA4All Supporting machine delegation and interoperability search extraction representation interpretation maintenanceStatic WWWSemantic Web URI, HTML, HTTPRDF, RDF(S), OWL 90. Before SOA4AllDynamicWeb Services UDDI, WSDL, SOAPEnable computationover the WebStatic WWW Semantic Web URI, HTML, HTTP RDF, RDF(S), OWL 91. Before SOA4All Automated Web Service UsageDynamicWeb ServicesSemantic Web UDDI, WSDL, SOAPServicesStatic WWW Semantic Web URI, HTML, HTTP RDF, RDF(S), OWL 92. After SOA4AllDynamicREST! Web Services Semantic Web UDDI, WSDL, SOAP ServicesStatic WWWSemantic Web URI, HTML, HTTPRDF, RDF(S), OWL 93. 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 theWeb Supported by a comprehensive suite ofeasy-to-use tools 103