A unified description language for human to automated services

Semantic Web Service Search: A Brief Survey

“…Prominent languages and formats for semantic service description are OWL-S (Web Ontology Language for Web Services) [45], WSML (Web Service Modeling Language) [13], the W3C standard SAWSDL (Semantic Annotations for WSDL and XML Schema) [12], USDL (Unified Service Description Language) [36,48], Linked USDL [49], as well as the microformats hRESTS [37], SA-REST [16], and MicroWSMO. These description models mainly differ in their formal logic-based foundation and the possible extent of service annotation [26,50].…”

A Methodology for the Integration of Service Repositories

“…Nevertheless, the situation is evolving, and it is worth noting that some of the most recent methodologies for the so called Service oriented software engineering life cycle compared in (Gu & Lago 2011), consider two levels of services, that, according to the approach followed, are called respectively business/technological, or abstract/concrete. So, it is now consolidating a view in the service life cycle that distinguishes among abstract services, providing the template for concrete realization in a particular setting (Oberle et al, 2013); whereas production and management phases consider concrete services as actually realized and implemented in a particular setting, being them manual, semi-automated, or else fully automated.…”

Applying Enterprise Architecture to Business Networks

“…Service aggregators are prominent business entities that combine existing services and deliver these through new markets. Accordingly, service methods and languages support different forms of service aggregation and different types of service entities are prominent in a service network [Oberle et al, 2013].…”

“…These dependencies manifest the constraints and boundaries of consuming and combining services. In Figure 2.6 (taken from [Oberle et al, 2013]), several dependencies have been illustrated through composition and bundling of services; for example Traffic Monitoring as a composite service requires Maps and Route Planning and Analysis. The…”

“…tools or organizational roles which are used for performing) and affected Resources (e.g. business objects which are manipulated) [Oberle et al, 2013]. This shows how services, as organizational systems/sub-systems concern organizational artifacts 2.7.…”