1 / 23

Service Description Language, Repository, Registry and Marketplace: Sample use case s

FI-WARE Applications and Services Ecosystem Torsten Leidig, SAP Research. Service Description Language, Repository, Registry and Marketplace: Sample use case s FI-WARE Webinar, Nov 14, 2012. Service Ecosystem. Highly specialized services Collaborative service value chain

onawa
Download Presentation

Service Description Language, Repository, Registry and Marketplace: Sample use case s

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. FI-WARE Applications and Services Ecosystem Torsten Leidig, SAP Research Service Description Language, Repository, Registry and Marketplace: Sample use cases FI-WARE Webinar, Nov 14, 2012

  2. Service Ecosystem • Highly specialized services • Collaborative service value chain • Bundling of products & services • Outsourcing • Cloud We need a platform for the Service Ecosystem! • Core enablers • Open standardized interfaces

  3. Internet of Services The Internet of Services allows • the trading of services • the bundling of services • the automatic offering, delivery, and execution The Internet of Services is a game of many.

  4. Platform – Service Marketplace • Available as platform services • Matching offering and demand • Negotiation of delivery constraints • Service bundles and compositions • Service configuration • Business model support Clerk Community USDL Repository Enterprise Infrastructure Mobile Infrastructure Partner Infrastructure

  5. High-level Architecture

  6. Service Provider • Agents • Price plans • Service levels • Availability • Licenses • Functionality • Dependencies • Interaction • Composition • Resources USDL • Interface • Protocol • Parameters • Infrastructure Unified Service Description

  7. The Role of Service Description Benefits of USDL

  8. Linked USDL Rationale • Easy to apply • Relying on existing standards • Extensible • Tools available • Link linking information across the service/app life cycle

  9. A way of publishing data inthe Web (URI, HTTP, HTML,XML/RDF) • It‘s about linked data sets • Web-scale data integration • and building coherence What is Linked Data?

  10. Example: Transport & Logistics Paul PlanningK+N Employee • Planning (Focus) • Execution Edward Execution K+N Employee • Planning • Execution (Focus) Kühne+NagelFreight Forwarder • First level • Second level • Third level hires responsible Electrical Devices Inc.Fridge Plant responsible

  11. Service Description

  12. Phase 1 - Planning Paul PlanningK+N Employee • Planning (Focus) • Execution Problems: • Find the best transportation option • Fastest, • Cheapest or • Most reliable • Information overflow • Many/Endless possible routes for one • Many Service Providers • Communication by phone • Lot experience necessary Possible Solutions: Comparable Logistic Service Offers Simplified access to available services (no phone) Real-Time availability information Booking Rollbacks

  13. Phase 1 - Planning • Some (!!) possibilities: Sea Sea Air Air

  14. Insert page title • First level • Second level • Third level truck

  15. Insert page title • First level • Second level • Third level truck Cheap Fast Best Rating

  16. Insert page title • First level • Second level • Third level truck

  17. Insert page title • First level • Second level • Third level truck

  18. Insert page title • First level • Second level • Third level truck

  19. Codes for Modes of Transport • Codes for Modes of Transport http://www.unece.org/fileadmin/DAM/cefact/recommendations/rec19/rec19_ecetrd138.pdf • CODES FOR TYPES OF MEANS OF TRANSPORThttp://www.unece.org/fileadmin/DAM/cefact/recommendations/rec28/rec28_ecetrd315.pdf • ANSI ASC X12 Data Element 91, Transportation Method/Type Codehttp://www.faima.com/edi_4010/el91.htm • DoD transportation mode codeshttp://www.bta.mil/FedeBiz/PRIVATE/EDIT/document/lfwg/flship.pdf

  20. Example: Cloud Services Problems • Countless offerings in the wild • No coherent description of services available • No common marketplace • Comparison of offerings (price, SLA, capabilities, …) is very difficult for users Linked-USDL can help to put light into the dark and make Cloud offerings more transparent to the consumer!

  21. Cloud Vocabulary • CPU Power, Memory and Storage • IP Addresses and I/O Performance • Data Recovery • Availability and Service Level Agreements • Credit system • Legal issues • Support services • Third parties involved

  22. How to express in Linked-USDL Generic USDL vocabularies: • usdl-core • usdl-sla • usdl-price Complementing domain specific Cloud vocabularies • cloud vocabulary taxonomy, specific qualitative and quantitative non-functional properties • operating system taxonomy • support vocabulary

  23. Example service <#service_IaaS> a usdl:Service ; dcterms:modified "2012-05-07"^^xsd:date ; dcterms:created "2012-04-17"^^xsd:date ; dcterms:title "Iaas demo service"@en ; dcterms:abstract "An IaaS demo service."@en ; dcterms:description "This a service demo description for an IaaS service."@en ;usdl:hasProvider :entity_IaaSDemoProvider ;usdl:hasLegalCondition<#terms_IaaS> ;usdl:hasPartMandatory<#service_Support> ; cloud:hasCPUPower [ gr:hasUnitOfMeasurement "A86" ; # gigahertz gr:hasValue "1.5" ; gr;valueReference [ a cloud:numberOfCores ; gr:hasValue "2" ]] ; cloud:hasAmountOfDiskStorage [ gr:hasUnitOfMeasurement "E34" ; # gigabyte gr:hasValue "30" ] ; cloud:hasAmountOfMainMemory [ gr:hasUnitOfMeasurement "4L" ; # megabyte gr:hasValue "1250" ] ; cloud:hasUpstreamCapacity [ gr:hasValue "32" ; gr:hasMinValue "6" ; gr:hasUnitOfMeasurement "D36" ] . # megabit

More Related