Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
Semantic Web Services
State of the Art
Markus Lanthaler
Graz University ofTechnology
©SprengBen
Programming today is a race between software engineers
striving to build bigger and better idiot-proof programs,
and the U...
SOAP + WSDL + UDDI
© Capture Queen
SOAP ≈ RPC not Web-friendly
© jvs11
REST (Representational StateTransfer)
specifically developed for the Web
© longhorndave
© Michael Glasgow
(Perceived) complexity High Low
Usage of HTTP as an
application protocol
No, abused as
transport protoco...
REST typically has just a
human-readable documentation
WRDLNSDLRSWSSMEX-DResedelWDLMost natural description by HTML
containing hyperlinks and forms
The only regularly updated
pr...
Syntactic description is not enough
Semantic annotation of
data and behavior
© Clever Cupcakes
Semantic Description Formats
 OWL-S
 WSMO
 SAWSDL
 SA-REST
 MicroWSMO
 WSMO-Lite
 Atom/RSS
 OpenSearch
 oEmbed
 ...
Profile
Service Process Model
Grounding
described by
What does
the service
How to access
the service
How the
service works...
Connectors between these components
handles heterogeneities
allows loose coupling
Goals
Ontologies
Service
Description
Med...
SAWSDL
modelReference
liftingSchemaMapping
loweringSchemaMapping
WSDL/XSD
MicroWSMO
Model
Lifting
Lowering
HTML + microformats
(relies on hRESTS)
SA-REST
Action
Input/Output/Fault
Lifting
HTML + RDFa
Operation
Lowering
WSMO-Lite
Information
Model
Behavioral
Semantics
Functionality the
service offers
How has a client to
talk to the service
...
Possible to create matching
stacks for SOAP and REST
SAWSDL
WSDL
Ontology, e.g. WSMO-Lite
extends
hRESTS
MicroWSMO
Service...
All of these approaches assume a
RPC-style service. REST is different.
©Nesster
©DaveJoyce
Atom, OpenSearch + Linked Open Data
Domain-specific Description
Formats
Atom/AtomPub OpenSearch
© 2010, Markus Lanthaler. Some Rights Reserved.
http://creativecommons.org/licenses/by-nc-sa/3.0/
ThankYou
Markus Lanthaler
Markus.Lanthaler@student.TUGraz.at
©MichaelSauers
Image Credits
(1) http://www.flickr.com/photos/sprengben/4550315185/
(2) http://www.flickr.com/photos/rickharris/324128591...
Bonus Slides
Use lifting/lowering schemas
Translation between service’s native and ontology’s format
© Anders Sandberg
Data mediation/integration is a
common and still open problem
© mdid
Publishers are willing to annotate
their data if there is an incentive
Facebook’s Open Graph
Protocol was implemented
in o...
“We know the hard things are
possible, we just have to make the
easy things easy.”
[Norman Walsh, 2006]
©LuisdeBethencourt
Semantic Web Services: State of the Art
Semantic Web Services: State of the Art
Upcoming SlideShare
Loading in …5
×

Semantic Web Services: State of the Art

2,437 views

Published on

Presentation at the IADIS International Conference on Internet Technologies & Society (ITS 2010) in Perth, Australia

Published in: Technology, Education
  • Be the first to comment

Semantic Web Services: State of the Art

  1. 1. Semantic Web Services State of the Art Markus Lanthaler Graz University ofTechnology ©SprengBen
  2. 2. Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. © Rick Harris [Rick Cook,The Wizardry Compiled] So far, the Universe is winning.
  3. 3. SOAP + WSDL + UDDI © Capture Queen
  4. 4. SOAP ≈ RPC not Web-friendly © jvs11
  5. 5. REST (Representational StateTransfer) specifically developed for the Web © longhorndave
  6. 6. © Michael Glasgow (Perceived) complexity High Low Usage of HTTP as an application protocol No, abused as transport protocol Yes Web-friendly (direct support of caches, proxies, etc.) No Yes Stateless No (most of the time) Yes Addressable resources No Yes Data handling Automatic mapping to objects (O/X) No automatism Data security WS-Security, … HTTPS SOAP REST
  7. 7. REST typically has just a human-readable documentation
  8. 8. WRDLNSDLRSWSSMEX-DResedelWDLMost natural description by HTML containing hyperlinks and forms The only regularly updated proposals are hRESTS and WADL WADL: closely related to WSDL hRESTS: microformats for HTML doc.
  9. 9. Syntactic description is not enough
  10. 10. Semantic annotation of data and behavior © Clever Cupcakes
  11. 11. Semantic Description Formats  OWL-S  WSMO  SAWSDL  SA-REST  MicroWSMO  WSMO-Lite  Atom/RSS  OpenSearch  oEmbed  … Domain-specific formats General-purpose formats
  12. 12. Profile Service Process Model Grounding described by What does the service How to access the service How the service works OWL-S
  13. 13. Connectors between these components handles heterogeneities allows loose coupling Goals Ontologies Service Description Mediators Objectives a client might have when consulting the service Description of servicesDefines the formalized domain knowledge WSMO
  14. 14. SAWSDL modelReference liftingSchemaMapping loweringSchemaMapping WSDL/XSD
  15. 15. MicroWSMO Model Lifting Lowering HTML + microformats (relies on hRESTS)
  16. 16. SA-REST Action Input/Output/Fault Lifting HTML + RDFa Operation Lowering
  17. 17. WSMO-Lite Information Model Behavioral Semantics Functionality the service offers How has a client to talk to the service Data model for input, output and fault messages Functional Semantics Non-functional Descriptions Non-functional properties, e.g. QoS or pricing
  18. 18. Possible to create matching stacks for SOAP and REST SAWSDL WSDL Ontology, e.g. WSMO-Lite extends hRESTS MicroWSMO Service interface description Semantic annotation extends annotations point to
  19. 19. All of these approaches assume a RPC-style service. REST is different. ©Nesster
  20. 20. ©DaveJoyce Atom, OpenSearch + Linked Open Data Domain-specific Description Formats Atom/AtomPub OpenSearch
  21. 21. © 2010, Markus Lanthaler. Some Rights Reserved. http://creativecommons.org/licenses/by-nc-sa/3.0/ ThankYou
  22. 22. Markus Lanthaler Markus.Lanthaler@student.TUGraz.at ©MichaelSauers
  23. 23. Image Credits (1) http://www.flickr.com/photos/sprengben/4550315185/ (2) http://www.flickr.com/photos/rickharris/3241285917/ (4) http://www.flickr.com/photos/uaeincredible/64162372/ (4) http://www.flickr.com/photos/uaeincredible/64162372/ (5) http://www.flickr.com/photos/jvs11/4253275748/ (7) http://www.flickr.com/photos/davidw/3501319155/ (8) http://www.flickr.com/photos/glasgows/2200685325/ (12) http://www.flickr.com/photos/clevercupcakes/4397152402/ (21) http://www.flickr.com/photos/nesster/3168425434/ (22) http://www.flickr.com/photos/deapeajay/2597109669/ (24) http://www.flickr.com/photos/travelinlibrarian/223839049/ (27) http://www.flickr.com/photos/arenamontanus/2530501831/ (28) http://www.flickr.com/photos/mdid/2698688454/ (30) http://www.flickr.com/photos/luisbg/2072134438/
  24. 24. Bonus Slides
  25. 25. Use lifting/lowering schemas Translation between service’s native and ontology’s format © Anders Sandberg
  26. 26. Data mediation/integration is a common and still open problem © mdid
  27. 27. Publishers are willing to annotate their data if there is an incentive Facebook’s Open Graph Protocol was implemented in over 50,000 Web sites within the first week [http://developers.facebook.com/blog/post/379] … and it’s simple enough
  28. 28. “We know the hard things are possible, we just have to make the easy things easy.” [Norman Walsh, 2006] ©LuisdeBethencourt

×