Subject: RE: [soa-rm] Re: Autonomous Services?
Sameer - - Let me practice being Matt <g>: The term " 'central' metadata" presumes a specific implementation strategy and should not be in the RM. Perhaps "metadata associated with the service should be available in the environment." Now in my example SOA for Appendix B, I'll probably show a UDDI services directory, or maybe a combo registry/repository that can in fact store all the description metadata. Martin -----Original Message----- From: Sharma, Sameer [mailto:firstname.lastname@example.org] Sent: Friday, April 29, 2005 2:16 PM To: Smith, Martin; Duane Nickull; email@example.com Cc: ebSOA OASIS TC; firstname.lastname@example.org Subject: RE: [soa-rm] Re: Autonomous Services? My feeling is that some of what you are alluding to might be covered by UDDI, however as is happening in an instance of SOA deployment that I am involved in - UDDI by itself is not going to be sufficient to express all the metadata that is needed for a client to successfully and contextually interpret all that a Web Service does. My attempted solution is to capture this additional metadata by leveraging central metadata services of my enterprise. I guess what I am saying is that the concept of "central metadata" might be a valid candidate as a component of the Reference Architecture we are considering. Since I was unable to participate in the F2F, (due to some last minute commitments that I got called into), if this topic was discussed, please accept my apologies for bringing it up again. Thanks! L Sameer Sharma Principal Applications Architect Lockheed Martin Corporation Chief Technology Office (CTO) 12506 Lake Underhill Road - MP 166 Orlando, FL-32825 Tel: (407) 306 5640 Fax:(407) 306 1392 -----Original Message----- From: Smith, Martin [mailto:Martin.Smith@DHS.GOV] Sent: Friday, April 29, 2005 1:38 PM To: Duane Nickull; email@example.com Cc: ebSOA OASIS TC; firstname.lastname@example.org Subject: RE: [soa-rm] Re: Autonomous Services? Folks - - On my way home from N'awlins Wed night, I had a thought on this discussion. I think we expect services in an SOA to be independent of the kind of shared contextual knowledge we usually presume within a local computing environment. We expect that the requesting service will be able to obtain all the info it needs to use the responding service successfully by processing the responding service's description metadata. I do think this is a core characteristic of SOA services. I'm not suggesting we reinstate the use of the word "autonomous" as a handle for this concept since it demonstrably caused confusion at the f2f. If we need a handle, perhaps "self-sufficient" or "self-documenting" or "introspective" (naaah - forget that one.) Martin -----Original Message----- From: Duane Nickull [mailto:email@example.com] Sent: Friday, April 29, 2005 12:43 PM To: firstname.lastname@example.org Cc: ebSOA OASIS TC; email@example.com Subject: [soa-rm] Re: Autonomous Services? We discussed and the submitter withdrew the submission pending clarification on exactly what is meant by Autonomous nature WRT services. It may be re-submitted and probably will however we do not have consensus on it at present. Duane john c hardin wrote: > Duane and SOA-RM group - > Can someone enlighten the members of the eb-soa group regarding a > description of Autonomous Services? Any resulting conversations from > the meetings this week, on the subject of Autonomous Services would be > good also. > > thanks > john > -- *********** 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 ***********