RE: [soa-rm-ra] Updated Visual Model for Service Description

["Poulin, Michael" <Michael.Poulin@uk.fid-intl.com>]

Another thing - according to the diagram, Service Description includes
information about its consumers (via the Contract). I think it is too
complex and assume that Service Contracts know which Service Description
they relate to, not opposite. 

Service Description is a public thing. While it might be appropriate for
consumers to know who uses the service, it is not a common rule. If some
consumers would require to exclude them from the list, it will create a
level of inconsistency.

My proposal  - keep Service Descriptions w/o knowledge of service
consumers, in two different repositories (for Descriptions and for
Contracts) but refer to the Description from the Service Contracts.

If you are saying it is a Best Practice, not the RA, I agree. However,
the RA should not demonstrate a precedent of not that best practice
(explicitly including Service Contracts into Service Description; it is
not a service inventory where all information about the service gets
collected)

- Michael
 

Important: Fidelity Investments International (Reg. No.1448245),
Fidelity Investment Services Limited (Reg. No. 2016555), Fidelity
Pensions Management (Reg. No. 2015142) and Financial Administration
Services Limited (Reg. No. 1629709, a Fidelity Group company) are all
registered in England and Wales, are authorised and regulated in the UK
by the Financial Services Authority and have their registered offices at
Oakhill House, 130 Tonbridge Road, Hildenborough, Tonbridge, Kent TN11
9DZ. Tel 01732 361144. Fidelity only gives information on products and
does not give investment advice to private clients based on individual
circumstances. Any comments or statements made are not necessarily those
of Fidelity. The information transmitted is intended only for the person
or entity to which it is addressed and may contain confidential and/or
privileged material. If you received this in error, please contact the
sender and delete the material from any computer. All e-mails sent from
or to Fidelity may be subject to our monitoring procedures. Direct link
to Fidelity's website -
http://www.fidelity-international.com/world/index.html 

-----Original Message-----
From: Jeffrey A. Estefan [mailto:jeffrey.a.estefan@jpl.nasa.gov] 
Sent: 05 November 2007 16:14
To: soa-rm-ra@lists.oasis-open.org
Subject: Re: [soa-rm-ra] Updated Visual Model for Service Description

Danny,

Where are you going with this federation business???

Are you proposing something along the lines of the Federated Enterprise 
Reference Architecture (FERA) model?

http://xml.coverpages.org/SemantionSOA-Runtime200509.pdf

(See Section 3.0)

There was a big play in the ebXML world on this (see, e.g., 
http://www.ebxmlsoft.com/papers/ebxml-fera.pdf) and I saw it go nowhere
when 
I attended the OASIS Symposium up in San Francisco a few years ago.
There 
were briefings from the ebSOA TC folks and, again, it has gone
absolutely 
nowhere.  In fact, I have not seen it referenced anywhere outside this 
community or even the analyst community.

I'm really worried that once again, we're getting distracted and we NEED
TO 
FINISH THE RA!!!!!!  Our work has gone one far too long in my opinion.
We 
need to stay focused as a razor.

If you're looking to build out a tool for your registry/repository, then
you 
should leverage the various service metadata information models (IMs)
out 
there.  The IM described in JSR 93 (JAXR) is one of the best I've seen.
And 
it supports both UDDI and ebXML standards.  I've attached a copy of the 
original spec.  Check out Section 4 and in particular, Fig. 11, which 
provides a UML class diagram depicting the IM.

Cheers...

 - Jeff E.