Good point. I will dig into that as well! Thanks for the advice.
Paul On Dec 13, 2007 8:37 PM, mikomatsumura <[EMAIL PROTECTED]> wrote: > well if you go by the burton group (Anne) view, there's three pieces, > metadata repository, service registry and policy repository, so you're > not really looking into many use cases here wrt policy... > > Miko > > > --- In [email protected], "Paul > Fremantle" <[EMAIL PROTECTED]> wrote: > > > > Miko > > > > I agree that there are different usage patterns. If you look at an > > enterprise reg/rep in particular, I also see five common actual usage > > patterns of a given registry/repository: > > > > 1. A domain owner creating a space and managing permissions for that > domain > > - e.g. I'm the accounting manager and /domains/finance/accounts is where > > accounting services live > > 2. A developer or administrator publishing an entry - e.g. creating > a new > > service entry > > 3. A system automatically publishing a service - e.g. the ESB > publishing the > > WSDL for this service > > 4. A workflow system moving a service from test to production once tests > > have been completed > > 5. A runtime system reading an entry from the registry > > > > In my opinion various standard APIs are really only strongly useful for > > points 3 and 4. The first two are perfectly easily done through a > web UI, > > and the last one is most likely simply an HTTP GET. So to me the real > > question of the value of these APIs is - how do they benefit the > enterprise > > over the use of other more simple document oriented APIs like WebDAV and > > AtomPub? > > > > Also have I missed any significant use cases? > > > > Paul > > > > On Dec 10, 2007 1:21 PM, mikomatsumura <[EMAIL PROTECTED]> wrote: > > > > > 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" <pzfreo@> 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 > > > > paul@ > > > > > > > > "Oxygenating the Web Service Platform", www.wso2.com > > > > > > > > > > > > > > > > > > > > > > Yahoo! Groups Links > > > > > > > > > > > > > > > > > > -- > > 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 > > > > > > > > Yahoo! Groups Links > > > > -- 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
