Hi Paul, I believe there will be three categories of use, application based soa, the project based "SOA", and enterprise or multi-enterprise...
I think for an application based SOA, people will be able to continue to use Excel as the registry. For project based SOA I think lightweight approaches will be sufficient. But for federating multiple groups across the lifecycle or even multiple business units or companies, you might need to do some more "heavyweight" standards like ebRIM, JAXR, UDDI, LDAP and others, as well as having some workgroup capabilities and sophisticated access control, policy and governance capabilities. You might also want to look at WS-Policy for coordinating with runtime. I know you're pretty familiar with all this stuff, it's just what we are seeing from our customers. We get hundred plus page RFPs on this stuff... But I suppose it's all about governance and not just regrep. Miko --- In [email protected], "Paul Fremantle" <[EMAIL PROTECTED]> wrote: > > I recently posted an entry on my blog about a new kind of SOA Registry > http://pzf.fremantle.org/2007/12/new-kind-of-soa-registry.html > > In summary, I'm talking about a very lightweight REST and Atom based > Registry that tries to meet the requirements of an SOA registry/repository > in the simplest, easiest, most resource-oriented fashion. > > What do you think? > > Paul > -- > Paul Fremantle > Co-Founder and VP of Technical Sales, WSO2 > OASIS WS-RX TC Co-chair > > blog: http://pzf.fremantle.org > [EMAIL PROTECTED] > > "Oxygenating the Web Service Platform", www.wso2.com >
