So does a
Participant take on the role of
Mediator if they are providing a
mediation function? How does this
differ from a mediation service, or
does the mediating Participant act
as the mediation provider?
No, I
don’t think a registry is a
mediator. It may provide any of a
number of business functions, e.g.
endpoint resolution, retrieval of
business entity information,
pointers to WSDLs, but I
don’t consider these
mediation.
In the way
of definitions:
Merriam-Webster:
the act or
process of [acting as intermediary
agent in bringing, effecting, or
communicating; interposing between
parties in order to reconcile them};
especially intervention between
conflicting parties to promote
reconciliation, settlement, or
compromise
Wikipedia:
Mediation,
as used in law, is a form of
alternative dispute resolution
(ADR), is a way of resolving
disputes between two or more
parties. A third party, the
mediator, assists the parties to
negotiate their own settlement
(facilitative mediation). In some
cases, mediators may express a view
on what might be a fair or
reasonable settlement, generally
where all the parties agree that the
mediator may do so (evaluative
mediation).
Hence,
mediation is "assisted
communications for agreement."
Central to
mediation is the concept of
"informed consent." So long as
participants understand the nature
of a contemplated mediation process
and effectively consent to
participate in the described
process, virtually any mediation
process is possible and appropriate.
---------------------------------------------------------------------------
Dr.
Kenneth Laskey
MITRE
Corporation, M/S H305
phone: 703-983-7934
7515
Colshire
Drive
fax: 703-983-1379
McLean VA
22102-7508
So
registry is also a service but not
part of 'the' service that is
playing the role of provider? Is
it a service performing a
different role? It's capability
offering being rather specialized
(eg service discovery)? Going back
to the model, is it simply another
(of potentially many) role played
by a participant in the ecosystem?
Peter F Brown
Independent Consultant
www.peterfbrown.com
@pensivepeter
+1.310.694.2278
Sent from my Windows Phone -
Apologies for typos, levity and
brevity - it's hard to type on a
moving planet
> Peter,
> This is a good deck.
> A couple of comments:
>
>
>
> Mediator
>
>
>
> -? is a registry a good example?
Do we have better ones? Is it more
than mediator?
> I do not consider a registry to
be a mediator. A registry is a
specialized entity in his own right
with its own set of goals.
> Typically a mediator is an entity
that is invoking service on behalf as
a consumer and is seen by consumer as
a service (compare to proxy in a
distributed system). The difference
between mediator and a simple proxy is
significant - mediator is more like an
interpreter in a conversation between
people speaking different languages.
Typical mediators do the following -
transport transformation (for example
MOM to HTTP), semantic alignment (data
transformation), dynamic routing,
often leveraging registry
(version-based routing, etc)
>
> I am not sure how Skill is
relevant for SOA
>
> I have a real issue with
introducing resources into SOA. The
problem is Resources are orthogonal to
services - it is a completely
different model of the world - see
REST vs SOA. A service implementation
internally does depend on resources,
but this is opaque to the service
consumer.
> The issue here is that SOA is
based on the functional decomposition,
where functions can cross resource
boundaries, where Resource
decomposition is based on identifying
resources, regardless of services they
provide. A system can be build either
way, but those will be 2 different
systems. The relationship is similar
to entity beans (resource) vs session
beans (services).
>
> Semantics is a really hard one.
The issue is that in SOA semantics is
defined by service provider. It is NOT
specific to a consumer/provider pair.
A service consumer can have his own
semantics, but he typically has to use
a mediator for resolving semantic
differences
>
>
> From: Peter F Brown [
mailto:peter@peterfbrown.com]
> Sent: Tuesday, December 07, 2010
8:09 PM
> To:
soa-rm-ra@lists.oasis-open.org
> Subject: [soa-rm-ra] Strawman of
outstanding issues
>
> Hi:
> We have worked through the
entirety of outstanding issues,
questions and concerns for section 3
(along the way, examining also
sections 1 & 2). We have,
inevitably many, many, edits to
propose!
>
> However, and as promised on last
week's call, we now present a
"Strawman", in the form of the
attached slide deck which we think
touches on all the main issues and
provides a narrative for addressing
them.
>
> We stress this is not an editing
exercise but an attempt to gain
consensus on the main issues,
definitions and relationships between
terms before the proceeding with
presenting detailed dispositions of
textual changes, in line with said
consensus.
>
> As previously announced, I will
not be able to join the call tomorrow
as I'll be some 30,000 feet over
Kansas at the time of the call. Chris
Bashioum will lead off as your
Maître d'
>
> Regards,
> Peter
>
> Peter F Brown
> Independent Consultant
> [cid:
image001.png@01CB96AC.EA7AD190]
> Transforming our Relationships
with Information Technologies
>
www.peterfbrown.com
> @pensivepeter<
http://twitter.com/#!/@pensivepeter>;
> P.O. Box 49719, Los Angeles, CA
90049, USA
> Tel: +1.310.694.2278
>
>
>
> The information contained in this
communication may be CONFIDENTIAL and
is intended only for the use of the
recipient(s) named above. If you are
not the intended recipient, you are
hereby notified that any
dissemination, distribution, or
copying of this communication, or any
of its contents, is strictly
prohibited. If you have received this
communication in error, please notify
the sender and delete/destroy the
original message and any copy of it
from your computer or paper files.
---------------------------------------------------------------------
To unsubscribe from this mail list,
you must leave the OASIS TC that
generates this mail. Follow this link
to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
