The first steps into the use of Descriptions in a
SOA-based ecosystem give rise to the problem of how
groups (federations) are formed. I would like to see
a direct representation of the ability to participate
in groups in the description. To my knowledge, the
most common terminlogy for this in the industry right
now is federations.
I would also like to hear other opinions on the
subject.
There is also an alternate approach to annotations
that follows an extension objects pattern:
Danny
While admitting it forms something of a catch-all, I
thought of
certifications (and I guess federation info) would
fall under
annotations. Those governing a federation would
prescribe what they
felt was adequate federation description and the
description of an
entity would point to it.
So, should annotations point to likely types such as
certifications,
use/federation, contracts here(?), ... ?
Ken
On Nov 4, 2007, at 11:09 AM, Danny Thornton wrote:
The diagram is helpful, I am working on a web app
that
will allow entry of this information and then
update
an ebXML/UDDI registry.
In doing this, one of the things I think we are
missing in the general description is a hook for
federations. Is this description part of one or
more
federations? For the implementation I am putting
together, each description has a certificate
associated with it and can be used for things like
forming groups (federations), description
revocation,
etc.
Danny
Good first pass. Yes, we have always talked
about
the service
description as an artifact, so this makes sense.
I still need to sort out the writing to make sure
all the salient
points end up some place. The diagram will guide
the writing and
will itself evolve as the writing tightens up.
Ken
On Nov 3, 2007, at 12:31 PM, Jeffrey A. Estefan
wrote:
Ken,
I've created a component diagram for the Service
Description
artifact. This is a candidate visual model to
replace the class
diagram in the Service Description section that
you are updating.
It's not perfect, but it's a pretty good start.
I
think it's more
appropriate to show the Service Description as
an
artifact that is
made up of (or links to) a number of supporting
artifacts that
capture the meta level aspects of SOA-based
systems, particularly,
for the Reference Architecture.
Here's a direct link to a PNG copy of the visual
model on our Kavi
collection at:
25982/Service_Description_Model.png
I've added a couple of notes to the visual
model.
These are
intended to be our working notes and ultimately
should be removed
from the final version of the visual model.
Cheers...
- Jeff E.
----------------------------------------------------------------------
--
-----
Ken Laskey
MITRE Corporation, M/S H305 phone:
703-983-7934
7151 Colshire Drive fax:
703-983-1379
McLean VA 22102-7508
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam
protection around
------------------------------------------------------------------------
-----
Ken Laskey
MITRE Corporation, M/S H305 phone: 703-983-7934
7151 Colshire Drive fax:
703-983-1379
McLean VA 22102-7508
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around