Soa4 all technical achievements final

699 views

Published on

Published in: Education, Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
699
On SlideShare
0
From Embeds
0
Number of Embeds
6
Actions
Shares
0
Downloads
9
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • 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.
  • Soa4 all technical achievements final

    1. 1. Technical AchievementsSven Abels, Sudhir Agarwal, John Domingue, Yosu Gorroñogoitia and Jacek Kopecký Final Review Meeting May 2011, Brussels
    2. 2. Agenda• Web services and Web data• Achievements• New Actions – Multimedia search – Mobile Application – OSS Packaging – University of Seville• OSS Explanations• Conclusions 2
    3. 3. Web Services and Web Data
    4. 4. REST vs SOAP Update 4
    5. 5. REST vs SOAP API Searches SOA4All started here 5http://www.google.com/insights/search/#q=soap%20api%2Crest%20api&cmpt=q
    6. 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. 7. Achievements
    8. 8. (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
    9. 9. MicroWSMO & WSMO-Lite
    10. 10. Minimal Service Model, WSMO-Lite
    11. 11. WSMO-Lite Submission• W3C Member Submission as of 23 August 2010 – http://www.w3.org/Submission/WSMO-Lite/• Directors 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."
    12. 12. USDL Incubator Activity 13
    13. 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" ; 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
    14. 14. 17
    15. 15. Chapter in every FIA Book SO4All Editor for every book too 18
    16. 16. Training Movie 19
    17. 17. SOA4All Movie 20
    18. 18. New Actions
    19. 19. D 2.8.1 Multimedia Semantic Search Tool Annomation and SugarTube
    20. 20. 23
    21. 21. SugarTube 24
    22. 22. 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
    23. 23. D9.4.3 OpenData/Mobile Prototype (SOA4All Real Estate Finder)
    24. 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. 25. DescriptionWhat 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
    26. 26. User ViewScenario 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
    27. 27. Frontend Demo Demo 32
    28. 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 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 Initiativese.g. Nestoria, Schools, Bus Stations, Train Stations…•Service Execution 37
    29. 29. Behind the ScenesServices Services Services iServe iPhone Client Meta- data Discovery 38
    30. 30. Behind the Scenes { Real Estate Service "Nestoria" REST Mashup Bus Stop Service Not iServe SOA4Re Server Side iPhone Clientfrom Meta- us data Train Station Discovery Service School Service SparQL Request Server 39
    31. 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/soa4re 40
    32. 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. 33. OSS Packaging
    34. 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. 35. University of Seville
    36. 36. SOA4All ranking before US…• Eclectic ranking – Preferences cannot be combined – Three user interfaces – Some unexploited synergies 46
    37. 37. … and after US• Holistic ranking – Preferences can be combined – Single user interface – Ranking approaches are integrated 47
    38. 38. OSS Explanations
    39. 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 and matched• Covering SWS lifecycle
    40. 40. OSS Explanation ScenarioA provider with local knowledge… example: bank service for ATM locations…wants it service to be used. semantic annotation, publishingThe service is visible to a client… discovery, ranking…who reuses it in a complex process. composition 50
    41. 41. Service Annotation and Publishing Implement service: WSDL or REST WSDL: REST: SAWSDL MicroWSMO annotations, annotations, SOWER SWEET Semantic registry: iServe
    42. 42. Service Annotation
    43. 43. Service Annotation
    44. 44. Service Annotation
    45. 45. Service Annotation
    46. 46. Service Annotation
    47. 47. Service Annotation
    48. 48. Service Annotation
    49. 49. Service Annotation
    50. 50. Service Registry
    51. 51. Service Discovery and Ranking Broad matching by Functional Classification Input / Output Ranking Condition / Effect Consumption / Composition
    52. 52. Service Discovery and Ranking
    53. 53. Service Discovery and RankingNew functionaltaxonomy,unforeseenduring usecases
    54. 54. Service Discovery and RankingNew functionaltaxonomy,unforeseenduring usecases
    55. 55. Service Discovery and RankingNew functionaltaxonomy,unforeseenduring usecases
    56. 56. Service Discovery and RankingNew functionaltaxonomy,unforeseenduring usecasesFiner-grainedclassificationreducesnumber ofresults
    57. 57. Service Discovery and RankingPrice is a Availability isstatic NFP obtained from seekda public service
    58. 58. Service Discovery and Ranking
    59. 59. Service Discovery and Ranking
    60. 60. Service Discovery and RankingChosenoperation canbecommunicatedthrough toolsetusingfavourites list
    61. 61. 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
    62. 62. Service Composition: Phases Process Modelling Process Process Consumption Deployment (Execution) Process Annotation
    63. 63. Composition: Process Modelling
    64. 64. Composition: Process Modelling
    65. 65. Composition: Process Modelling
    66. 66. Composition: Process Modelling
    67. 67. Composition: Process Modelling
    68. 68. Composition: Process Modelling
    69. 69. Composition: Process Modelling
    70. 70. Composition: Process Modelling
    71. 71. Composition: Process Modelling
    72. 72. Composition: Process Modelling
    73. 73. Composition: Process Modelling
    74. 74. Composition: Process Modelling
    75. 75. Composition: Process Modelling
    76. 76. Composition: Process Modelling
    77. 77. Composition: Process Modelling
    78. 78. Composition: Process Modelling
    79. 79. Composition: Process Modelling
    80. 80. Composition: Process Modelling
    81. 81. Composition: Process Modelling
    82. 82. Composition: Process Modelling
    83. 83. Composition: Process Modelling
    84. 84. Composition: Process Modelling
    85. 85. Composition: Process Deployment
    86. 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. 87. Conclusion
    88. 88. Before SOA4All – 1.8B users – more than 1 trillion pagesStatic WWW URI, HTML, HTTP
    89. 89. Before SOA4All Supporting machine delegation and interoperability • search • extraction • representation • interpretation • maintenanceStatic WWW Semantic Web URI, HTML, HTTP RDF, RDF(S), OWL
    90. 90. Before SOA4AllDynamic Web Services UDDI, WSDL, SOAP Enable computation over the Web Static WWW Semantic Web URI, HTML, HTTP RDF, RDF(S), OWL
    91. 91. Before SOA4All Automated Web Service UsageDynamic Web Services Semantic Web UDDI, WSDL, SOAP Services Static WWW Semantic Web URI, HTML, HTTP RDF, RDF(S), OWL
    92. 92. After SOA4AllDynamic REST! Web Services Semantic Web UDDI, WSDL, SOAP Services Static WWW Semantic Web URI, HTML, HTTP RDF, RDF(S), OWL
    93. 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 the Web – Supported by a comprehensive suite of easy-to-use tools 103

    ×