Sorry Rex – 1
Registry stores those things, while mediator uses them
From: Rex Brooks [mailto:firstname.lastname@example.org]
Sent: Thursday, December 09, 2010 9:48 AM
To: Ken Laskey
Cc: 'Peter F Brown at work'; 'Lublinsky, Boris';
Subject: Re: [soa-rm-ra] Strawman of outstanding issues
I think that a Registry is actually a mediator according to
the Webster definition, and by my thinking since it acts as an intermediary.
Also there is no a priori restriction or constraint that prevents or precludes
a Registry from offering subsidiary services such as a publish-subscription
service for policies to provide public access with sufficient security, so I
think a registry service, especially a full-spectrum service including policies
and other relevant documentation related to the services in the registry is
indeed a first class mediator.
On 12/8/10 12:26 PM, Ken Laskey wrote:
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?Â
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.
the way of definitions:
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
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).
mediation is "assisted communications for agreement."
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Â Â Â Â Â Â Â Â Â Â Â Â Â
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
Sent from my Windows Phone - Apologies for typos, levity and brevity - it's
hard to type on a moving planet
Sent: Wednesday, 08
December, 2010 6:48
To: email@example.com; firstname.lastname@example.org
Subject: RE: [soa-rm-ra]
Strawman of outstanding issues
> This is a good deck.
> A couple of comments:
> -? is a registry a good example? Do we have better ones? Is it more than
> 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
> 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:email@example.com]
> Sent: Tuesday, December 07, 2010 8:09 PM
> To: firstname.lastname@example.org
> Subject: [soa-rm-ra] Strawman of outstanding issues
> 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'
> Peter F Brown
> Independent Consultant
> Transforming our Relationships with Information Technologies
> 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.
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
Starbourne Communications Design
GeoAddress: 1361-A Addison
Berkeley, CA 94702