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.

Beyond sparql linked data, software, services and applications. Keynote at Dagstuhl Seminar on Interoperation in Complex Information Ecosystems

This talk gives an overview of the Linked

  • Be the first to comment

Beyond sparql linked data, software, services and applications. Keynote at Dagstuhl Seminar on Interoperation in Complex Information Ecosystems

  1. 1. Beyond SPARQL: LinkedData, Software, Services andApplicationsJohn Domingue with Carlos PedrinaciKnowledge Media Institute
  2. 2. Overview• Motivation• Linked Services• Linked USDL for Service Marketplaces• Other EU Projects–Cloud Computing–Software• Summary
  4. 4. (256)
  5. 5. ASBOrometer
  6. 6. Linked Data is..• Machine readable (not a black box)• (Relatively) Simple• Uses Web standards• Re-usable• Interoperable• LinkableServices in SW are..
  9. 9. Linked Services Principles• Services described as Linked Data– Inputs, outputs, functionality, etc is described using RDF(S) andusing existing vocabularies• Consume and produce RDF– Applications may contain ‘standard services’ too• Process layer on top of the Web of Data
  10. 10. Behind the ScenesTrain stationsBus stopsSchoolsReal estatePublic Data and ServicespublishingService BrokerInvocationEnginediscoveryinvocation
  11. 11. SWEET & SOWERLPMLdeploymentProcess EditorDiscoveryincl. TG, Optimizer, DTCSOA4AllProcess LifecycleServiceannotationProcessmodelingProcessexecutionAnalysis & Monitoringincl. BPEL-based executionenvironmentSPICES
  12. 12. iServe Architecture21
  13. 13. WSDL
  14. 14. SAWSDL
  15. 15. WSMO-Lite TermsOntology rdf:type rdfs:Classrdfs:subClassOf owl:OntologyClassificationRoot rdfs:subClassOf rdfs:ClassNonFunctionalParameter rdf:type rdfs:ClassCondition rdf:type rdfs:ClassEffect rdf:type rdfs:Class
  16. 16. Web APIs
  17. 17. • Microformat–Collaboration with Amit Sheth• Introduces the service model structure–Service–Operations• Address, method–Inputs, Outputs (only their existence)hRESTS
  18. 18. MicroWSMO• Extends hRESTS–mref for model references–lifting, lowering• Applies WSMO-Lite semantics
  19. 19. MicroWSMO & WSMO-Lite
  20. 20. Minimal Service Model,WSMO-Lite
  21. 21. Minimal ServiceModel, WSMO-Lite
  22. 22. Minimal ServiceModel, WSMO-Lite
  23. 23. Minimal Service Model,WSMO-Lite
  24. 24. Minimal ServiceModel, WSMO-Lite
  25. 25. Authentication
  26. 26. KARMA Approach
  27. 27. KARMA Web API Ontology
  29. 29. The Future Internet– Enabler for Global Business NetworksManu-facturingUrbanManagementeEnergyTransportLogistic….Network ofthe FutureCloudComputingInternet ofThingsInternet ofServicesInternet of the FutureConsumersSuppliersWholesalersRetailersCarriersManufacturerGovernments© SAP 2010 /
  30. 30. The Internet of Services– Global Service Delivery Supply ChainA Single Market for ServicesSaaS, On-DemandEnterprise SuitesCloud ServicesServiceMarketplacesMulti-EnterpriseBPPB2BGatewaysBusiness ProcessOutsourcingBusiness Process PlatformService Delivery FrameworkServiceAggregatorServiceHosterServiceProviderServiceGatewayServiceBrokerServiceChannel MakerService-Oriented Architecture© SAP 2010 / Page 39
  31. 31. © SAP 2010 / Page 40ServiceAggregatorServiceHosterServiceProviderServiceGatewayServiceBrokerServiceChannel MakerThe Internet of Services– Unified Service Description Language (USDL)See also: Service Transformation stands for a value-driven, smooth and effective provision of servicesalong the Global Service Delivery Supply Chain Service Transformation implies that Services are being Described considering business, operational and legal requirements Maintained, extended and assembled where needed Applying a common notation named USDL
  32. 32. TRESOR
  33. 33. EU PROJECTS
  34. 34. SOFTWARE
  35. 35. 47MARKOSServiceOpen Source Projects CrawlerOpen SourceForgesOthersoftwarerepositoriesMARKOS RepositoryBrowsing QueryingOpen SourceProjectsSoftware InformationExtraction & AnalysisLicens InformationAnalysisMARKOS FrontendWEBLinked Dataaccess pointMarkos UsersWeb of Data
  37. 37. IaaS, PaaS and SaaSInfrastructure as a Service (IaaS):PIM4Cloud/ CloudML-xa platform virtualizationenvironment as a service.Platform as a Service (PaaS):CloudML-y: a computing platform andsolution stack as a service.Software as a Service (SaaS): SoaML: software as a serviceover the Internet.Different Issues for each layer.Infrastructure as a ServicePlatform as a ServiceSoftware asa Service
  38. 38. Model overview– The Cloud4soa PaaSsemantic model• Solves the semanticdifferences betweenthe Cloud PaaSofferings and allowthe semanticinteroperability amongthem.• Allows developersand Cloud providersexpress in acommon way theirapplications andofferings
  39. 39. Summary (1/2)• As for Linked Data desirable for application componentsto be:–Have machine-readable descriptions based on Webstandards–Discoverable–Re-usable–Interoperable–Linkable• Computing systems now associated with multipleparadigms– Community led Open Source Software initiatives– SOA, Service Marketplaces– Cloud
  40. 40. Summary (2/2)• Some efforts to leverage semantics and Linked Data tosupport interoperability, discovery, linking– Linked Services– Linked USDL for Service Marketplaces– Linked Open Software Source– Semantics in Clouds• Wider reflections on the relationship between LinkedData and current computing system paradigms wouldbenefit all associated communities
  41. 41. URIs• iServe -• Linked USDL -• SOA4All -• Internet of Services Collaboration Session on Semanticsin Services and Clouds–
  42. 42. Credits• Alert, Broker@Cloud, Cloud4SOA, MARKOS, MODAClouds and REMICS, slides taken from the Internet ofServices Collaboration Session on Semantics inServices and Clouds• KARMA slides generated from– Mohsen Taheriyan, Craig Knoblock, Pedro Szekely and José Luis Ambite.Rapidly Integrating Services into the Linked Data Cloud. ISWC 2012• Also slides created by- Jacek Kopecky, Maria Maleshkova