OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

soa-rm message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: RE: [soa-rm] Groups - Rough notes taken during the last ebSOA meeting. (ebSOA-Elements.pdf) uploaded


Title: Re: [soa-rm] Groups - Rough notes taken during the last ebSOA meeting. (ebSOA-Elements.pdf) uploaded
<Quote>
For example, the question of how do you know the resources exist implies (I think) the need for a catalog mechanism
</Quote>

Great point - I believe that asking these questions now can also help us come up with our definition of SOA. I also agree with Duane's view - it's sort of a chicken-and-egg problem here.

Kind Regards,

Joseph Chiusano

Booz Allen Hamilton

Visit us online@ http://www.boozallen.com

 


From: Ken Laskey [mailto:klaskey@mitre.org]
Sent: Tue 3/22/2005 5:34 PM
To: Duane Nickull
Cc: soa-rm@lists.oasis-open.org
Subject: Re: [soa-rm] Groups - Rough notes taken during the last ebSOA meeting. (ebSOA-Elements.pdf) uploaded

Duane,

The questions were meant as a way to step back from preconceived
assumptions of the answers and note some of the questions we will either
need to answer or identify as out of scope.  For example, the question of
how do you know the resources exist implies (I think) the need for a
catalog mechanism but it does not a priori require what we can easily make
look like a UDDI registry.  Yes, I know a reference model does not
normatively define implementations, but our reflex assumptions can lead us
to describing things we know about in more detail than is necessary.

Ken

At 05:24 PM 3/22/2005, Duane Nickull wrote:
>Ken:
>
>Until we know the "what" of what SOA is, it may be hard to answer some of
>these questions.  These are all questions that will depend on a normative
>reference model to answer, hence our work.
>
>Duane
>
>Ken Laskey wrote:
>
>>Might it not be good to start by listing the capabilities an SOA
>>enables?  For example, an SOA enables a set of distributed resources
>>(both data and processing resources) to be assembled to accomplish a task
>>defined independently from the SOA or its implementation.
>>Questions that follow are
>>- how do you know the resources exist? (seems to imply some catalog
>>mechanism)
>>- how do you know what the resources provide?
>>- how do you understand the resource, assuming it may use a vocabulary
>>that differs with (although it may overlap) yours?
>>- how do you ascertain the quality of the resource?
>>- how do you decide if the resource is useful in satisfying your task?
>>- if the resource may be useful, how do you access/invoke it?
>>- how do you use a given resource consistently with other resources?
>>- how do you capture what resources you used, in what order, and the
>>rationale for their choice and use?
>>
>>Now, what do our answers to these imply about the architecture?
>>Everything tends to be described in tiers of functionality, e.g. (my
>>favorites) user interface layer, service composition/meditation layer,
>>resource layer, and then there is the question of are there certain types
>>of services, e.g. discovery, that are so intrinsically part of the
>>concept that these need to be specifically called out?
>>
>>Let the fun begin!
>>
>>Ken
>>
>>
>>At 01:0       1PM3222005,mattm@adobe.zl6wrote
>>
>>>The document named Rough notes taken during the last ebSOA meeting.
>>>(ebSOA-Elements.pdf) has been submitted by Mr Matthew MacKenzie to the
>>>OASIS SOA Reference Model TC document repository. Document Description:
>>>View Document Details:
>>>http://www.oasis-open.org/apps/org/workgroup/soa-rm/document.php?document_id=11966
>>>Download Document:
>>>http://www.oasis-open.org/apps/org/workgroup/soa-rm/download.php/11966/ebSOA-Elements.pdf
>>>PLEASE NOTE:  If the above links do not work for you, your email
>>>application may be breaking the link into two pieces.  You may be able
>>>to copy and paste the entire link address into the address field of your
>>>web browser. -OASIS Open Administration s
>>
>>
>>--
>>
>>---------------------------------------------------------------------------------
>>
>>   /   Ken
>> Laskey                                                                \
>>  |    MITRE Corporation, M/S H305    phone:  703-883-7934   |
>>  |    7515 Colshire Drive                    fax:      703-883-1379   |
>>   \   McLean VA 22102-7508                                              /
>>
>>----------------------------------------------------------------------------------
>>
>>
>
>--
>***********
>Senior Standards Strategist - Adobe Systems, Inc. - http://www.adobe.com
>Vice Chair - UN/CEFACT Bureau Plenary - http://www.unece.org/cefact/
>Adobe Enterprise Developer Resources  -
>http://www.adobe.com/enterprise/developer/main.html
>***********
>

--
      ---------------------------------------------------------------------------------
   /   Ken
Laskey                                                                \
  |    MITRE Corporation, M/S H305    phone:  703-883-7934   |
  |    7515 Colshire Drive                    fax:      703-883-1379   |
   \   McLean VA 22102-7508                                              /
     ----------------------------------------------------------------------------------





[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]