Database Reference
In-Depth Information
Implementation tech-
nique
Service models
Selected Design rules (out of 185)
Register message-related
metadata elements in ser-
vice repository
[R 13] A ROOT SCHEMA MUST BE CREATED FOR EACH UNIQUE BUSINESS
INFORMATION EXCHANGE.
[R 23] A QUALIFIED DATA TYPE SCHEMA MODULE MUST BE CREATED
The figure explaining the table is as follows:
Needless to say, these rules also must be applied wisely with proper understanding of all
consequences. For example, following the rule
[R 60]
, that is,
THE XSD: ANY ELEMENT
MUST NOT BE USED
, we would not be able to implement an agnostic composition con-
troller using the message container concept. However, this rule is highly important for se-
curity reasons and must be strictly followed for ABCSs and in Perimeter Gateways imple-
mentations.
For now, we have identified three frameworks that are responsible for shaping and creat-
ing a service, establishing communication, and resolving interchange disparities. The Hy-
pothetical Business Service Composition area remains untouched, but now it is the time to
find out what is it, really. From the
standards roadmap
diagram, we realized that complex
compositions could be synchronous with elements of atomic transaction coordination and
asynchronous with running chains of complex communications, lasting for very extended
period of time. Different technical standards and operational requirements delineate two
new frameworks, each dedicated to its own type of service interactions, mostly based on
time metrics. We will start with asynchronous service compositions, as they are more
technically demanding.
Search WWH ::
Custom Search