The FI-WARE Project – Core Platform for the Future Internet 1 st Webinar Session on Registry, Torsten Leidig, Repository, and Marketplace May 28, 2013;

Slides:



Advertisements
Similar presentations
UBIQUITY V3 An extensible platform for creating dynamic, customized, and geocentric native mobile applications.
Advertisements

Putting the Pieces Together Grace Agnew Slide User Description Rights Holder Authentication Rights Video Object Permission Administration.
IATI Technical Advisory Group Technical Proposals Simon Parrish IATI Technical Advisory Group, DIPR March 2010.
Page 1 Copyright © 2010 Data Access Technologies, Inc. Model Driven Solutions May 2009 Cory Casanave Architecture of Services SOA for E-Government Conference.
Multi-level SLA Management for Service-Oriented Infrastructures Wolfgang Theilmann, Ramin Yahyapour, Joe Butler, Patrik Spiess consortium / SAP.
Policy based Cloud Services on a VCL platform Karuna P Joshi, Yelena Yesha, Tim Finin, Anupam Joshi University of Maryland, Baltimore County.
The FI-WARE Project – Core Platform for the Future Internet Service Description Language, Repository, Registry and Marketplace: Sample use cases FI-WARE.
Web Services Nasrullah. Motivation about web service There are number of programms over the internet that need to communicate with other programms over.
UDDI, Discovery and Web Services Registries. Introduction To facilitate e-commerce, companies needed a way to locate one another and exchange information.
Kantara: From IRM to Context. The World of Access Keeps Expanding App sourcing and hosting User populations App access channels SasS apps Apps in public.
SmartER Semantic Cloud Sevices Karuna P Joshi University of Maryland, Baltimore County Advisors: Dr. Tim Finin, Dr. Yelena Yesha.
A New Computing Paradigm. Overview of Web Services Over 66 percent of respondents to a 2001 InfoWorld magazine poll agreed that "Web services are likely.
Brokering Mathematical Services Through a Web Registry.
FI-WARE – Future Internet Core Platform FI-WARE Apps/Services Ecosystem and delivery July 2011 High-level Description.
SaaS, PaaS & TaaS By: Raza Usmani
Cloud based linked data platform for Structural Engineering Experiment Xiaohui Zhang
Presenter: NAME Date: MM/DD/YYYY CUSTOMER NAME Presenter: Harris Date: 04/06/ An extensible platform for creating.
Processing of structured documents Spring 2003, Part 6 Helena Ahonen-Myka.
Just a collection of WS diagrams… food for thought Dave Hollander.
DESIGN OF A PLATFORM OF VIRTUAL SERVICE CONTAINERS FOR SERVICE ORIENTED CLOUD COMPUTING Carlos de Alfonso Andrés García Vicente Hernández.
Page  1 SaaS – BUSINESS MODEL Debmalya Khan DEBMALYA KHAN.
 Cloud computing  Workflow  Workflow lifecycle  Workflow design  Workflow tools : xcp, eucalyptus, open nebula.
CIS 375—Web App Dev II Microsoft’s.NET. 2 Introduction to.NET Steve Ballmer (January 2000): Steve Ballmer "Delivering an Internet-based platform of Next.
THE GITB TESTING FRAMEWORK Jacques Durand, Fujitsu America | December 1, 2011 GITB |
OASIS ebXML Registry Standard Open Forum 2003 on Metadata Registries 10:30 – 11:15 January 20, 2003 Kathryn Breininger The Boeing Company Chair, OASIS.
M.A.Doman Short video intro Model for enabling the delivery of computing as a SERVICE.
Open Data Protocol * Han Wang 11/30/2012 *
OASIS Week of ebXML Standards Webinars June 4 – June 7, 2007.
Agenda Motivation on why a “Business Framework” is relevant in the Future Internet Provide insights into possibilities with the framework Catch a glimpse.
FI-CORE Data Context Media Management Chapter Release 4.1 & Sprint Review.
XML Registries Source: Java TM API for XML Registries Specification.
1 Schema Registries Steven Hughes, Lou Reich, Dan Crichton NASA 21 October 2015.
The FI-WARE Project – Base Platform for Future Service Infrastructures FI-WARE Interface to the network and Devices Chapter.
Web Services Based on SOA: Concepts, Technology, Design by Thomas Erl MIS 181.9: Service Oriented Architecture 2 nd Semester,
Ocean Observatories Initiative Data Management (DM) Subsystem Overview Michael Meisinger September 29, 2009.
©Ferenc Vajda 1 Semantic Grid Ferenc Vajda Computer and Automation Research Institute Hungarian Academy of Sciences.
What’s MPEG-21 ? (a short summary of available papers by OCCAMM)
Jose Jimenez Telefónica I+D Future Network & Mobile Summit 2011 The vision of Future Internet in the FI PPP Core Platform project.
OWL Representing Information Using the Web Ontology Language.
The FI-WARE Project – Base Platform for Future Service Infrastructures FI-WARE Stefano De Panfilis (Fi-WARE PCC Member) 4 th July 2011 FInES - Samos Summit.
Registries, ebXML and Web Services in short. Registry A mechanism for allowing users to announce, or discover, the availability and state of a resource:
WEB SERVICE DESCRIPTION LANGUAGE (WSDL). Introduction  WSDL is an XML language that contains information about the interface semantics and ‘administrivia’
Independent Insight for Service Oriented Practice Summary: Service Reference Architecture and Planning David Sprott.
1 Registry Services Overview J. Steven Hughes (Deputy Chair) Principal Computer Scientist NASA/JPL 17 December 2015.
Web Services An Introduction Copyright © Curt Hill.
Providing web services to mobile users: The architecture design of an m-service portal Minder Chen - Dongsong Zhang - Lina Zhou Presented by: Juan M. Cubillos.
Enteprise Content Management from Microsoft. 20% structured 80% unstructured 90% of unstructured data is unmanaged Volume of data is increasing ~36%/year.
Software Architecture Patterns (3) Service Oriented & Web Oriented Architecture source: microsoft.
International Planetary Data Alliance Registry Project Update September 16, 2011.
The Web Web Design. 3.2 The Web Focus on Reading Main Ideas A URL is an address that identifies a specific Web page. Web browsers have varying capabilities.
12. DISTRIBUTED WEB-BASED SYSTEMS Nov SUSMITHA KOTA KRANTHI KOYA LIANG YI.
E-Business Infrastructure PRESENTED BY IKA NOVITA DEWI, MCS.
Dr. Ir. Yeffry Handoko Putra
Defining ONAP APIs With BSS/OSS
Cloud based linked data platform for Structural Engineering Experiment
Autonomic Resource Virtualization in Cloud-like Environments A
Sabri Kızanlık Ural Emekçi
Marketplace & service catalog concepts, first design analysis
Distributed web based systems
IBM Data Server Gateway for OData
Introduction to Cloud Computing
Wsdl.
Policy based Cloud Services on a VCL platform
WEB API.
The Re3gistry software and the INSPIRE Registry
Grid Services B.Ramamurthy 12/28/2018 B.Ramamurthy.
KNOWLEDGE MANAGEMENT (KM) Session # 34
LOD reference architecture
The Anatomy and The Physiology of the Grid
The Anatomy and The Physiology of the Grid
Presentation transcript:

The FI-WARE Project – Core Platform for the Future Internet 1 st Webinar Session on Registry, Torsten Leidig, Repository, and Marketplace May 28, 2013; June 5, 2013 FI-WARE Applications and Services Ecosystem SAP Research

The FI-WARE Project – Core Platform for the Future Internet Service Ecosystem  Highly specialized services  Collaborative service value chain  Outsourcing, Cloud Computing We need a platform for the Service Ecosystem!  Core enablers  Open standardized interfaces  Uniform Service Description Language

The FI-WARE Project – Core Platform for the Future Internet Unified Service Description Interface Protocol Parameters Infrastructure Interface Protocol Parameters Infrastructure Functionality Dependencies Interaction Composition Resources Functionality Dependencies Interaction Composition Resources Service Provider Agents Price plans Service levels Availability Licenses Service Provider Agents Price plans Service levels Availability Licenses USDL

The FI-WARE Project – Core Platform for the Future Internet Linked USDL Rationale  Common description language for services and apps is needed  Low entry barrier to allow easy onboarding  Relying on existing standards as much as possible  Extensible according to domain and life-cycle aspect  Link linking information across the service/app life cycle  

The FI-WARE Project – Core Platform for the Future Internet Use Case: Logistics Logistic services problems  No common scheme for transportation services  Planning of routes with many legs is cumbersome  Main criteria are price, reliability and time  Hard to find transport options if plan must be changed on the fly  Vast amount of transport options is inaccessible  Phone calls, paper work A spot market and planning tool based on Linked-USDL logistic service descriptions would have an enormous effect USDL roadmap 5

The FI-WARE Project – Core Platform for the Future Internet

Service Description

The FI-WARE Project – Core Platform for the Future Internet 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!

The FI-WARE Project – Core Platform for the Future Internet Examination of IaaS Offerings  CPU Power, Memory and Storage  IP Addresses and I/O Performance  Data Recovery  Availability and Service Level Agreements  Cedit system  Legal issues  Support services  Third parties involved

The FI-WARE Project – Core Platform for the Future Internet 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

The FI-WARE Project – Core Platform for the Future Internet Example service a usdl:Service ; dcterms:modified " "^^xsd:date ; dcterms:created " "^^xsd:date ; dcterms:title "Iaas demo ; dcterms:abstract "An IaaS demo ; dcterms:description "This a service demo description for an IaaS ; usdl:hasProvider :entity_IaaSDemoProvider ; usdl:hasLegalCondition ; usdl:hasPartMandatory ; 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

The FI-WARE Project – Core Platform for the Future Internet High Level Architecture

The FI-WARE Project – Core Platform for the Future Internet Repository Generic Enablers

The FI-WARE Project – Core Platform for the Future Internet Repository: Rationale Storing service descriptions and associated resources Used by other components (marketplace, composition editor, …) Distributed storage (Linked Data) Defined by Open Specification based on HTTP Different implementations possible Authentication (IDMaaS) Etag handling to ensure consistency

The FI-WARE Project – Core Platform for the Future Internet Repository: Data Model The Repository is structured into Resources and Collections Collection: Packing Collection: Transport Collection: Insurance

The FI-WARE Project – Core Platform for the Future Internet Repository Principles „How to publish Linked Data on the Web“ by Chriz Bizer et al Respect Web Architecture principles A resource is identified by its „dereferencable“ URL Information resources (200 ok) Non-information resources (303 see other) HTTP GET should deliver meaningful information Content negotiation (RDF, N3, HTML, JSON, …) Use of resolvers like PURL (30x redirect) Easily crawled by search engines Accessed using generic data browsers Enabling linkes between data from different sources

The FI-WARE Project – Core Platform for the Future Internet Repository: Data Model and Operations Collections Identified by path e.g. /logistics/services/transport/ Resources Indentified by URI! E.g. /logistics/services/transport/service4711 Service descriptions Any kind of media type Operations Read, write, delete, list (Extensions: search)

The FI-WARE Project – Core Platform for the Future Internet Registry Generic Enablers

The FI-WARE Project – Core Platform for the Future Internet Registry: Rationale Used to store information on instance level (entries describing instances and their parameters) Somehow equivalent to directory services (e.g. LDAP) Is just an protocol specification, which is agnostic according the implementation (database, distribution) Our implementation is based on MongoDB

The FI-WARE Project – Core Platform for the Future Internet Registry: Data Model and Operations Register key Identified by (directory) path e.g. /provider/transport/ Register entry Indentified by URI, e.g. /provider/transport/dhl Is represented by a set of key/value pairs (JSON object) Operations Read, write, delete, list Filtering and attribute selection via query parameters

The FI-WARE Project – Core Platform for the Future Internet Marketplace Generic Enablers

The FI-WARE Project – Core Platform for the Future Internet Clerk USDL Repository Enterprise Infrastructure Enterprise Infrastructure Mobile Infrastructure Partner Infrastructure Community  Available as platform services  Matching offering and demand  Negotiation of delivery constraints  Service bundles and compositions  Service configuration  Business model support Marketplace

The FI-WARE Project – Core Platform for the Future Internet Marketplace – Architecture

The FI-WARE Project – Core Platform for the Future Internet Marketplace – Core Components  Registry and Directory  holds information of registered stores, participants and their role  takes care of registering, updating, and deleting information about market relevant entities.  Offering & Demand  responsible for exchanging service offerings with stores and version handling/archiving of out-dated offerings.  Discovery & Matching  is about discovering and matching offering and demand

The FI-WARE Project – Core Platform for the Future Internet Marketplace – Core Components  Recommendation  provides the user service recommendations based on the users’ profile and context  Review & Rating  allows users of the marketplace to give textual and star-rating feedback for services and stores along predefined categories  Reviews of users and their overall rating about applications and services can be used to improve the quality of recommendations