Beyond sparql linked data, software, services and applications. Keynote at Dagstuhl Seminar on Interoperation in Complex Information Ecosystems
•Descargar como PPTX, PDF•
3 recomendaciones•1,259 vistas
This talk gives an overview of the Linked
Recomendados
Recomendados
Más contenido relacionado
La actualidad más candente
La actualidad más candente (9)
Similar a Beyond sparql linked data, software, services and applications. Keynote at Dagstuhl Seminar on Interoperation in Complex Information Ecosystems
Similar a Beyond sparql linked data, software, services and applications. Keynote at Dagstuhl Seminar on Interoperation in Complex Information Ecosystems (20)
Más de John Domingue
Más de John Domingue (20)
Último
Último (20)
Beyond sparql linked data, software, services and applications. Keynote at Dagstuhl Seminar on Interoperation in Complex Information Ecosystems
- 1. Beyond SPARQL: Linked Data, Software, Services and Applications John Domingue with Carlos Pedrinaci Knowledge Media Institute
- 2. Overview • Motivation • Linked Services • Linked USDL for Service Marketplaces • Other EU Projects –Cloud Computing –Software • Summary
- 3. MOTIVATION
- 5. (256)
- 6. ASBOrometer
- 8. Linked Data is.. • Machine readable (not a black box) • (Relatively) Simple • Uses Web standards • Re-usable • Interoperable • Linkable Services in SW are..
- 10. LINKED SERVICES APPROACH AND PRINCIPLES
- 16. Linked Services Principles • Services described as Linked Data – Inputs, outputs, functionality, etc is described using RDF(S) and using existing vocabularies • Consume and produce RDF – Applications may contain ‘standard services’ too • Process layer on top of the Web of Data
- 19. Behind the Scenes Train stations Bus stops Schools Real estate Public Data and Services publishing Service Broker Invocation Engine discovery invocation
- 20. SWEET & SOWER LPML deployment Process Editor Discovery incl. TG, Optimizer, DTC SOA4All Process Lifecycle Service annotation Process modeling Process execution Analysis & Monitoring incl. BPEL-based execution environment SPICES
- 22. WSDL
- 23. SAWSDL
- 24. WSMO-Lite Terms Ontology rdf:type rdfs:Class rdfs:subClassOf owl:Ontology ClassificationRoot rdfs:subClassOf rdfs:Class NonFunctionalParameter rdf:type rdfs:Class Condition rdf:type rdfs:Class Effect rdf:type rdfs:Class
- 25. Web APIs
- 26. • Microformat –Collaboration with Amit Sheth • Introduces the service model structure –Service –Operations • Address, method –Inputs, Outputs (only their existence) hRESTS
- 27. MicroWSMO • Extends hRESTS –mref for model references –lifting, lowering • Applies WSMO-Lite semantics
- 34. Authentication
- 35. KARMA Approach
- 36. KARMA Web API Ontology
- 38. The Future Internet – Enabler for Global Business Networks Manu- facturing Urban Management eEnergyTransport Logistic …. Network of the Future Cloud Computing Internet of Things Internet of Services Internet of the Future Consumers Suppliers Wholesalers Retailers Carriers Manufacture r Governments © SAP 2010 /
- 39. The Internet of Services – Global Service Delivery Supply Chain A Single Market for Services SaaS, On-Demand Enterprise Suites Cloud Services Service Marketplaces Multi-Enterprise BPP B2B Gateways Business Process Outsourcing Business Process Platform Service Delivery Framework Service Aggregator Service Hoster Service Provider Service Gateway Service Broker Service Channel Maker Service-Oriented Architecture © SAP 2010 / Page 39
- 40. © SAP 2010 / Page 40 Service Aggregator Service Hoster Service Provider Service Gateway Service Broker Service Channel Maker The Internet of Services – Unified Service Description Language (USDL) See also: http://www.internet-of-services.de/index.php?id=24 Service Transformation stands for a value-driven, smooth and effective provision of services along 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
- 41. TRESOR
- 45. EU PROJECTS
- 46. SOFTWARE
- 47. 47 MARKOS Service Open Source Projects Crawler Open Source Forges Other software repositories MARKOS Repository Browsing Querying Open Source Projects Software Information Extraction & Analysis Licens Information Analysis MARKOS Frontend WEB Linked Data access point Markos Users Web of Data
- 49. IaaS, PaaS and SaaS Infrastructure as a Service (IaaS): PIM4Cloud/ CloudML-x a platform virtualization environment as a service. Platform as a Service (PaaS): CloudML-y: a computing platform and solution stack as a service. Software as a Service (SaaS): SoaML: software as a service over the Internet. Different Issues for each layer. Infrastructure as a Service Platform as a Service Software as a Service
- 50. Model overview – The Cloud4soa PaaS semantic model • Solves the semantic differences between the Cloud PaaS offerings and allow the semantic interoperability among them. • Allows developers and Cloud providers express in a common way their applications and offerings
- 51. Summary (1/2) • As for Linked Data desirable for application components to be: –Have machine-readable descriptions based on Web standards –Discoverable –Re-usable –Interoperable –Linkable • Computing systems now associated with multiple paradigms – Community led Open Source Software initiatives – SOA, Service Marketplaces – Cloud
- 52. Summary (2/2) • Some efforts to leverage semantics and Linked Data to support interoperability, discovery, linking – Linked Services – Linked USDL for Service Marketplaces – Linked Open Software Source – Semantics in Clouds • Wider reflections on the relationship between Linked Data and current computing system paradigms would benefit all associated communities
- 53. URIs • iServe - http://iserve.kmi.open.ac.uk/ • Linked USDL - http://www.linked-usdl.org/ • SOA4All - http://www.soa4all.eu/ • Internet of Services Collaboration Session on Semantics in Services and Clouds –http://ec.europa.eu/digital- agenda/events/cf/ios12/item-display.cfm?id=8726
- 54. Credits • Alert, Broker@Cloud, Cloud4SOA, MARKOS, MODAClo uds and REMICS, slides taken from the Internet of Services Collaboration Session on Semantics in Services 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
Notas del editor
- Thanks for the introduction. Thanks for coming. Flavour of the work related to the notion of a Future Internet.
- So how do we link to this wealth of data?We have our own repository of service descriptions within the cloud. We are the first and still only service repository in this space. The are created using a variety of tools. Note that when creating our descriptions we can rely on existing descriptions in the cloud. In the same way as one web page can point to another to expand a description.
- As well as creating descriptions within the cloud we support
- The creation of services which consume and produce semantic data.
- We also support the management and use of ‘standard’ services
- Which can produce data for this large semantic cloud
- Within one of my projects (soa4all) we have developed an iPhone App to support this. Its available in the store and called the soa4all real estate finder
- Mulberry school and others
- Services over public data (to the singers in the virtual choir)Service broker is like the conductor. Services are published in our broker. An engine translates between user actions and details of invoking services (each service may have its own idiosyncratic way of being invoked)User interacts with the iPhone Appdiscovery based on user preferences and location -> services are available Services are not fixed (like singers for each performance). adding more for crime statistics also based on public data.
- The AuthenticationMechanism class has six subclasses, corresponding to com-mon authentication mechanisms, Credentials class has a number of instances includingAPI Key , Username , Password and OAuth Credentials , which can be combinedto produce composite credentials, such as authentication through username andPassword.The TransmissionMedium has two instances(ViaHTTPHeader and ViaURI ), used to describe that the credentials are sentby using only the URI or through constructing an HTTP header.he composedOf relationship as well as the class AuthenticationMech-anism , which can have further subclasses, represent points of extensibility forthe ontology. The Service class has a relationship to the ServiceAuthentication class, which has three instances including All , Some and None that are used topoint out that the service requires authentication for all its operations, for onlysome of them or for none of them.
- SAP 4th largest software producer in the world by revenue Microsoft, IBM and Oracle. 109,000 customers 120 countriesSAP with 12.46B euro of revenue Very much interested in the Internet of the Future
- Complete Ecosystem for value added services based on Service Objects Lower barriers to develop, select, combine and use value added servicesObject DescriptionCapture data exposed and its semanticsCapture objects capabilities (frequency of data provisioned, processing capabilities)Capture contextual information e.g., geolocationBetter support Discovery, Composition and UseReusable assetsSemantic Sensor Networks Ontology (W3C)Domain ontologiesDynamic Large Scale Data Processing InfrastructureCapture data streams and their provenanceSense making of large quantities of streaming data (e.g., feature inferencing, data correlation, etc)Secure end-to-end channelsReusable AssetsProvenance vocabulary (W3C)Domain ontologiesAdvance Data Mining and Machine Learning algorithmsObjects Virtualisation as ServicesExpose Objects as reusable servicesVirtualisation of sensors into services for the development of advanced applications through compositionUse of capabilities for optimised decomposition and deploymentReusable assetsMinimal Service ModelAI planning and (de)composition algorithms
- open sourceprojectsperiodicallycrawledandchangesnotifiedavailablemetadataextracted (jar manifest, Mavenpom, OSGimetadata etc.)software & licencecodeanalysedtoproducefurthermetadatametadatastored in a triple-store toenablesemanticqueryingandbrowsing.Interfaces formachines (Linked Data) andhumans (Front End)