Dennis Sosnoski wrote: > > On registries, I've yet to see a compelling use case for UDDI. The > problem I see with UDDI is mainly that it's designed for use by programs > - but there's nothing useful you can do automatically with the retrieved > information in a program. AFAIKS a web page-based human-readable and > searchable directory of services would be more effective than UDDI > without requiring any special interfaces. I'm hoping someone can point > out something I'm missing here. > How about the scenario where you are trying to build a Service that satisfies complies with a SLA. The Service is built from registered service elements (could be thousands, hundreds of thousands). The Service Architect needs someway to identify which of the registered service elements can best be aggregated to provide a service with will perform at the specified SLA. So you need to build a marketplace where Element Providers can register service elements and Service Architects can build services from these service elements.
cheers </jima> ------------------------ Yahoo! Groups Sponsor --------------------~--> Check out the new improvements in Yahoo! Groups email. http://us.click.yahoo.com/6pRQfA/fOaOAA/yQLSAA/NhFolB/TM --------------------------------------------------------------------~-> Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/service-orientated-architecture/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
