[Fiware-apps] Light Semantic Composition features ("Composition, Sync-Call to clarify the next steps")

[Joaquin Iranzo Yuste]

Dear Composition-Partners,

 

This is the features list for the Light Semantic Composition that is
aligned with the Open Specification. I think that this classification
together with the detail of the Open Specification will help the
use-case projects to understand and to decide if they need the GE.

 

*         Model Composition

This GE provides support for service composition modeling, assuming BPMN
2.0 as graphical notation and execution semantics. Through the BPMN
Composition Editor, business modelers can create or open composition
models, modify them (edit) and manage them (save, delete). Composition
models are stored within a Repository.

Composition edition also includes support for create/update/delete
features for composition elements, such as service tasks, gateways
(exclusive, parallel), flows and events (start, end).

Composition editor allows to select the composition itself or concrete
composition elements.

 

*         Prepare DSL/Semantics:

In this GE approach, the business modelers describe composition models
and their elements by annotating them with concepts taken from concrete
domain specific languages DSL (or vocabularies) which provide concrete
semantics. From operational point of view, it is common to use
ontologies as DSL or vocabularies. The Light-weighted Semantic Mediator
enables the business modeler to:

*Register new DSL/Ontologies within it

*Select a concrete DSL/Ontology for a given domain modeling context.
Select a concrete DSL/Ontology concept within the domain ontology. These
concepts are used to annotate and describe a composition model and their
elements.

 

*         Describe Model Composition/Task using DSL/Semantics (Business
modelers):

The Light-weighted Semantic Mediator enables the business modeler to
describe the composition model and its elements using semantic
annotations.

In the scope of a composition task, the annotations constitute a
description of the task. In other words, they describe the goal of the
task. This goal will be used in the service matchmaking process to look
for services whose semantic description will match it. A semantic task
description is constituted by several annotations of certain type
according to the semantic schema used to represent the goal (i.e MSM )

In the scope of the composition itself, the annotations constitute a
description of the global composition requirements, preferences and
contextual information.

 

*         Describe Service using DSL/Semantics (Service Providers):

Light-weighted Semantic-enabled Service Composition GE approach assumes
that composable services are described using light semantics. Those
semantic service descriptions are available within the Semantic
Knowledge Base, and are provided by service providers. A service
composition created by applying this GE approach is a service by its
own, whereby the business modeler, acting as service provider, is
required to provide this semantic description. Same applies to any other
third party service intented to be composed by others.

The Light-weighted Semantic Mediator enables service providers to create
semantic descriptions compliant to the semantic schema used by the
complete GE solution. The concrete schema is left for the
implementation, but it should be consistent along with all components
that use it.

The schema includes links to the business oriented description stored in
the Marketplace, and the technical description stored in the Repository.

 

*         Bind task to service:

One of the main jobs in service composition modeling is to bind every
task the composition is divided out to a matching service that performs
the task. A business modeler can conduct this task binding per task or
for the whole composition. The Light-weighted Semantic Mediator enables
the modeler to discover matching services based on task goal criteria,
rank them according to preferences or non-functional requirements (NFR)
and select one service, which is bound to the task. Those activities are
typically performed by querying the Semantic Knowledge Base.

 

*         Validate, generate, translate executable BPMN composition
model:

After binding task to service, next step in service composition modeling
consists on filling the missing information that the composition model
requires before being shipped for deployment and execution. Examples of
missing information are:

*Task binding technical description. For each BPMN 2.0 service task, a
concrete task binding information has to be included, by inspecting the
technical description (i.e. WSDL).

*Data flow mapping, including IO mappings at task and composition level.

Once the service composition model has been completed with missing
required executable information, the composition model is validated
(BPMN 2.0 compliance validation) and serialized (for storage and
deployment).

Optionally, the composition model can be translated from its original
BPMN 2.0 format to another mappable format, such as BPEL 1.2/2.0 . This
is required when the select target environment for execution is not BPMN
2.0 compatible.

 

*         Deploy composition model:

Full executable validated composition models can be deployed into the
selected target Composition Execution environment, using the Composition
Deployer. Once deployed, the service composition is enabled, being ready
to received incoming requests from service consumers.

Similarly, deployed service compositions can be undeployed anytime.

 

*         Composition Execution:

During the execution time, deployed services can be enabled or disabled
any time through the Composition Execution UI. Besides, running
compositions (enabled) can be continuously monitored and monitoring data
can be collected for given time frames.

 

 

Best regards,

 

Joaquin Iranzo.

------------------------------------------------------------------
This e-mail and the documents attached are confidential and intended 
solely for the addressee; it may also be privileged. If you receive 
this e-mail in error, please notify the sender immediately and destroy it. 
As its integrity cannot be secured on the Internet, the Atos 
group liability cannot be triggered for the message content. Although 
the sender endeavours to maintain a computer virus-free network, 
the sender does not warrant that this transmission is virus-free and 
will not be liable for any damages resulting from any virus transmitted. 

Este mensaje y los ficheros adjuntos pueden contener informacion confidencial 
destinada solamente a la(s) persona(s) mencionadas anteriormente 
pueden estar protegidos por secreto profesional. 
Si usted recibe este correo electronico por error, gracias por informar 
inmediatamente al remitente y destruir el mensaje. 
Al no estar asegurada la integridad de este mensaje sobre la red, Atos 
no se hace responsable por su contenido. Su contenido no constituye ningun 
compromiso para el grupo Atos, salvo ratificacion escrita por ambas partes. 
Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor 
no puede garantizar nada al respecto y no sera responsable de cualesquiera 
danos que puedan resultar de una transmision de virus. 
------------------------------------------------------------------
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/old-fiware-apps/attachments/20130110/1059bb0a/attachment.html>