Information Technology Reference
In-Depth Information
that applies semantics on the request trans-
forming it to a semantic goal by adding,
discovering or using existing suitable se-
mantic inputs. The mediating framework
then forwards the semantic goal to the WS
directory and applies the matchmaking
process (Agarwal & Studer, 2006) between
the goals and capabilities in order to return
firstly the appropriate cloud and conse-
quently to invoke one of its Web Services
(which are registered by the provider).
as XML schema documents (Brehm &
Marx Gómez, 2007).
To solve the problem of the standards in FERP
system, semantics will be introduced and Semantic
Web Services will be involved within the new sys-
tem that will be responsible of the matchmaking,
filtering results processes and applying dynamic
Web Service composition.
Web serVice VALidAtion Within
seMAntic soA-bAsed ModeL
•
It might happen that more than one WS
fulfills the semantic goal, and at this point,
a dynamic workflow is generated in order
to compose the desired WS (if possible
and depending on having such functional-
ity in the Web Services advertised in the
directory). In this case, a composite service
may outsource operations that have dif-
ferent domains of interest and since these
operations belong to two or more different
clouds, the new composite service has to
be registered in all of them.
Web service compliance
One goal of the semantic SOA-based model is to
annotate information with semantic metadata. In
contrast to other concepts, the annotation (Hand-
schuh & Staab, 2003) here is not a part of the
adopted Web Service itself. There is an isolated
service, which is used to perform this annotation
task. It is a precondition to validate the adopted
WS against the external domain ontologies. The
reason behind that resides in the issue that the
user of an ontology expects that the service will
work as the ontology describes, and the only way
to insure this is to apply service validation.
We can classify the compliance of Web Services
in four main different types:
•
Each invocation of a cloud operation is
translated into the invocation of one of its
Web Services.
The proposed architecture will be ap-
plied on FERP system that consists of
components that are distributed within
a computer network (Brehm & Marx
Gómez, 2005) (Brehm, Marx Gómez
& Strack, 2007). FERP reference archi-
tecture is based on the concepts of SOA,
and it is an execution environment for
discovery and invocation of enterprise
Web Services, it offers also a complete
support for interacting with Web Ser-
vices within the enterprise space or
among enterprises. Because one of the
main objectives of the FERP system
is to integrate business components
of different vendors, all components
have to comply with standards. In this
approach, these standards are described
•
Exact: WS is able to comply with the re-
quirements (WS properties).
•
Over-Exact: WS has higher compliance
than the requirements.
•
Partial: WS is able to comply with the re-
quirements fractionally.
•
Failure: WS is not able to comply with the
requirements.
An exact compliance is the ideal situation.
In this case, a WS fulfills the expectations. An
over-exact compliance is happening when the
WS provides a higher level of quality more than
Search WWH ::
Custom Search