Re: Service Description Update

The diagram is a good fundamental capture of the RM.

I'm also interested to see if we need something else to capture

The service description represents the information needed in order to use a service. In most cases, there is no one “right” description but rather the elements of description required depend on the context and the needs of the parties using the associated entity.

I have not thought of anything that doesn't fall under the 5 listed boxes (or it would have been added to the RM) and am not inclined to add a "other" but I'm still chewing on that.

Mainly, I am looking at other points of our discussion and considering how to incorporate.

On Oct 23, 2006, at 3:32 AM, Danny Thornton wrote:

I added a projection of the Service Description from
the Reference Architecture to an implementation.

http://wiki.oasis-open.org/soa-rm/TheArchitecture/ServiceDescription

It is for example purposes only. Service Description
was one of the models up for discussion/debate this
week so please feel free to have at it.

Ken, the Service Description implementation flow is
similar to an interpretation I made on a previous
project. I've seen another company make a similar
interpretation of the Reference Model Service
Description as well.

Danny

__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com

------------------------------------------------------------------------------------------

Ken Laskey

MITRE Corporation, M/S H305 phone: 703-983-7934

7515 Colshire Drive fax: 703-983-1379

McLean VA 22102-7508

soa-rm-ra message