Linked USDL at the FI-WARE Architects Weeks in Madrid

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

2st Architecture WorkshopJune 04-07, 2012

FI-WARE Applications and Services EcosystemAxel Fasse, SAP Research


Agenda

Overview Motivation for „Apps & Services“ The Idea „Internet of Services“ High-level Architecture Service Marketplace USDL Linked open Data More GE‘s Q & A


Overview

The Apps & Services chapter will provide:A service infrastructure that enables

provision, composition, and consumption of services

Support of this infrastructure via USDL in service descriptions covering technical, operational, and business aspects

Supporting general business, SLA, RSS management associated to the offerings, accounting, and billing

Partners involved in WP3 SAP – Registry, Repository, and Marketplace (Uwe Riss)

TID – RSS (Pablo Arozarena)

EAB – Composition and Push Communication Protocol (Calin Curescu)

DT & ATOS – Composition (Horst Stein & Miguel Huerta) (Andreas Grothe)

UPM – Mashup and Store (Javier Soriano)

TI & THALES – Mediation (Marco Ughetti & Pierre Chatel)

ENG – SLA Management (Keven Kearney)

UDE – Scenario Support (Andreas Froese)


Socio-Economic Background – Tertiary Sector

Gross Domestic Product Distribution in Germany 2011

Distribution of Employees in the different industry sectors in Germany

Quelle: Statistisches Jahrbuch 2010 für die Bundesrepublik Deutschland mit »Internationalen Übersichten«, Statistisches Bundesamt, 2010.


Flexible Value Chains


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


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.

Internet of Services


High-level Architecture


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

USDL Repository

USDL Repository

EnterpriseInfrastructure

EnterpriseInfrastructure

Mobile Infrastructure

Mobile Infrastructure

Partner Infrastructure

Partner Infrastructure

Community

Unified Service DescriptionsGeneric Enabler


Unified Service Description

• Interface• Protocol• Parameters• Infrastructure

• Functionality• Dependencies

• Interaction• Composition

• Resources

• Service Provider• Agents• Price plans• Service levels• Availability• Licenses USD

L


The Role of Service Description

Benefits of USDL


Evolution of USDL

Collaborative and interdisciplinary modeling

› Initiated by SAP Research

› Roughly 2 dozens researchers contribute

› Spread over approx. 10 publicly funded research projects and 5 SAP Research locations

› Expertise from all SAP Research areas integrated

› Includes contributions of many project partners (FhG FOKUS, IAO, …)

› Include feedback and requirements from industrial partners (Siemens, Attensity, …)

› W3C Incubator group

› Linked-USDL community founded for broad and world-wide adoption and further development by the community

2007 2008 2009 2010 2011

v1.0v2.0 v3.0M1 M2M3 M5

XML Schema UML class modelInformal

M4

2012

Linked USDL


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.

Internet of Services


What is Linked Data?

A way of publishing data in the Web (URI, HTTP, HTML,XML/RDF)

It‘s about linked data sets

Web-scale data integration

and building coherence


What is it about?

Exposing data on the Web Enable applications to link data that wasn't previously linked Using Web to lower the barriers to link data (that is currently

linked by other methods)

Web as a single global Database


Linked-USDL Rationale

Lower entry barrier Simplify the process of further development Reuse existing standards Use existing tools Link USDL information with existing information Bring USDL into the realm of Linked Data (leverage synergies) And easily publish it at different locations (The Internet of Data).


Standards Strategy

1. Establish a community for users of USDL (linked-usdl.org)

2. Support community to conduct show case apps and mashups (providing the basic infrastructure for USDL apps such as repository, discovery, editors,...)

3. Build USDL into products/services and solutions at SAP and other partners.

4. Find industrial/commercial users (big companies), which support a standardization.

5. Find the right standardization body or create one and facilitate standardization process


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!


Cloud Vocabulary

• 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


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


USDL-Sec


USDL-SLA


USDL-Price


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


FI-WARE Application and Services Ecosystem and Delivery Framework

This chapter will provide:• A service infrastructure that enables

provision, composition, and consumption of services

• Support of this infrastructure via USDL

in service descriptions covering technical, operational, and business aspects

Supporting general business, SLA, RSS management associated to the offerings, accounting, and billing

Partners involved in WP3

SAP – Registry, Repository, and Marketplace (Uwe Riss)

TID – RSS (Pablo Arozarena)

EAB – Composition and Push Communication Protocol (Calin Curescu)

DT & ATOS – Composition (Horst Stein & Miguel Huerta)

UPM – Mashup and Store (Javier Soriano)

TI & THALES – Mediation (Marco Ughetti & Pierre Chatel)

ENG – SLA Management (Keven Kearney)

UDE – Scenario Support (Andreas Froese)

Linked USDL at the FI-WARE Architects Weeks in Madrid

Technology