We use proprietary and third party's cookies to improve your experience and our services, identifying your Internet Browsing preferences on our website; develop analytic activities and display advertising based on your preferences. If you keep browsing, you accept its use. You can get more information on our Cookie Policy
Cookies Policy
USDL 3.0 Specifications M5 - FIWARE Forge Wiki

USDL 3.0 Specifications M5

From FIWARE Forge Wiki

Jump to: navigation, search

Brief description

The Unified Service Description Language (USDL) is a platform-neutral language for describing services. It was consolidated from SAP Research projects concerning services-related research as an enabler for wide leverage of services on the Internet. SAP Research believes that with the rise of commoditized, on-demand services, the stage is set for the acceleration of and access to services on an Internet scale. It is provided by major investments through public co-funded projects, under the Internet of Services theme, where services from various domains including cloud computing, service marketplaces and business networks, have been investigated for access, repurposing and trading in large settings.

The kinds of services targeted for coverage through USDL include: purely human/professional (e.g. project management and consultancy), transactional (e.g. purchase order requisition), informational (e.g. spatial and demography look-ups), software component (e.g. software widgets for download), digital media (e.g. video & audio clips), platform (e.g. middleware services such as message store-forward) and infrastructure (e.g. CPU and storage services). A generic service description language – like USDL – acting as a “one size fits all” for domains as diverse and complex as banking/financials, healthcare, manufacturing and supply chains, is difficult to use and therefore not sufficient. First of all, not all aspects of USDL apply to all domains. Rather, USDL needs to be configured for the particular needs of applications where some concepts are removed or adapted while new and unforeseen ones are introduced. A particular consideration of this is allowing specialized, domain-specific classifications such as those available through vertical industry standards to be leveraged through USDL. In addition to this, the way in which USDL is applied for deployment considerations, e.g., the way lifecycle versioning applies, needs to be managed without compromising the fundamental concepts of USDL. In other words, USDL needs to be applied through a framework which allows separation of concerns for how it is applied and tailored to concrete applications. This need has led to the USDL framework where the concepts of the USDL meta-model as a core are specialized through the USDL Application meta-model. A non-normative specialization of the USDL meta-model with the USDL framework is provided to illustrate how a service directory of a specific Service Delivery Framework (proposed by SAP Research) can be conceptualized through USDL. In this way, an insight is available for an application of USDL and its USDL Application meta-model.

In FI-Ware we will rely on the expressiveness of USDL version M5. Instead of using the specialized XML serialization of USDL M5 we will switch over to a Linked Data Representation of USDL. By maintaining the expressiveness of USDL we will ...

A wide variety of use cases and perspectives were investigated across the different publicly funded research projects to develop service descriptions for forms of services and an alignment of business and technical aspects not available through previous R&D and standards efforts.

Use cases from the corporate world shed insights into commercial management and arrangements of services such as cost centre ownership and provisioning, releasing and dependencies in complex IT and business landscapes. Use cases involving service marketplaces procuring services as complex as those from SAP’s portfolio and ecosystem provided new insights into structures for service bundling including price-competitive of both professional and automated forms of services. Use cases from cloud computing/IT virtualization helped frame platform and infrastructure services into USDL and extended service dependency graph with hosting requirements for services. Use cases from business networks have shown that service versioning/provisioning capabilities need to extend beyond service providers to intermediaries and outsourced players such as brokers, aggregators and channel partners – to drive up “network effect” of services.


The M5 specifications of USDL contain a dedicated terms of use section, where the IPR are defined.

Publicly available documentation

The projects have included: the TEXO project within the THESEUS pogram initiated by the German Federal Ministry of Economics and Technology (BMWi), German Federal Ministry of Education and Research projects (BMBF) Premium Services, EU European Commission, DG INFSO projects FAST, RESERVOIR, MASTER, SERVFACE, SHAPE, SLO@SOI, and SOA4ALL and finally the Australian Smart Services GRC.

Further description and specifications for USDL can be found on [1].

Personal tools
Create a book