tag:blogger.com,1999:blog-6003063374827736283.post8459605948094079840..comments2008-01-07T12:09:16.891-08:00Comments on Paul Fremantle's Blog: A new kind of (SOA) RegistryPaul Fremantlehttp://www.blogger.com/profile/15326219720808613358noreply@blogger.comBlogger9125tag:blogger.com,1999:blog-6003063374827736283.post-81175058172127038882008-01-07T12:09:00.000-08:002008-01-07T12:09:00.000-08:00I like that your RSS approach isn't coming from a ...I like that your RSS approach isn't coming from a fundamentalist anti uddi perspective but a very pragmatic one...kudos for a fresh view and it seems you thought of it already a while ago!<BR/><BR/>MikoMiko Matsumurahttp://www.blogger.com/profile/06104074479680832271noreply@blogger.comtag:blogger.com,1999:blog-6003063374827736283.post-38240187207469720092008-01-07T11:42:00.000-08:002008-01-07T11:42:00.000-08:00Here is what I wrote a couple of years ago:http://...Here is what I wrote a couple of years ago:<BR/>http://www.ipbabble.com/2006/01/rss_for_soa_based_services_reg.html<BR/><BR/>I had some follow-up with some code here:<BR/>http://www.ipbabble.com/2006/01/rss_demo_code.html<BR/><BR/>Cheers,<BR/>Williamwilliam_henryhttp://www.blogger.com/profile/10603348495975763459noreply@blogger.comtag:blogger.com,1999:blog-6003063374827736283.post-88743173156527708572007-12-22T00:42:00.000-08:002007-12-22T00:42:00.000-08:00The first release of this code is now available: c...The first release of this code is now available: check out http://wso2.org/downloads/registry<BR/><BR/>PaulPaul Fremantlehttp://www.blogger.com/profile/15326219720808613358noreply@blogger.comtag:blogger.com,1999:blog-6003063374827736283.post-45592758369870629422007-12-22T00:10:00.000-08:002007-12-22T00:10:00.000-08:00William Henry of IONA (http://www.ipbabble.com/ po...William Henry of IONA (http://www.ipbabble.com/ posted a note on doing this quite some time ago. I cannot find it right now, but will look further when I have time.<BR/>I do like the 'simple' nature of this, something just about everyone should be able to understand and use.<BR/>Cheers, JohnJ. Apps, B. Cameron, S. Sieboldhttp://www.blogger.com/profile/13009296879505481064noreply@blogger.comtag:blogger.com,1999:blog-6003063374827736283.post-52835474941030533132007-12-07T11:52:00.000-08:002007-12-07T11:52:00.000-08:00We are seeing more and more appreciation of the eb...We are seeing more and more appreciation of the ebRIM/JAXR metamodel these days. It's not so much that there's interop inherent in it (although there is), it's more that this end-user driven standard really encodes for a lot of use cases that happen to come in handy. I agree that UDDI is far from universal but a lot of vendor interop uses it today...Miko Matsumurahttp://www.blogger.com/profile/06104074479680832271noreply@blogger.comtag:blogger.com,1999:blog-6003063374827736283.post-48879060517375887932007-12-07T08:34:00.000-08:002007-12-07T08:34:00.000-08:00Paul,I like your regrep implementation and the who...Paul,<BR/><BR/>I like your regrep implementation and the whole REST vs ebRIM catalog has been generating a lot of discussion in the geospatial software world.<BR/><BR/>A couple of questions though;<BR/><BR/>ebRIM allows object associations which is really powerful (e.g. service->dataset, dataset->owner) - I don't see how this is possible with REST apart from using xlink:href or a path such as /owner/dataset which isn't very intuitive (I can't see explicit associations with a REST registry)<BR/><BR/>JEE spec mandates a JAXR client, so that components can access an XML registry - how do you envisage this in a case of a REST registry and being spec compliant?<BR/><BR/>Registry looks really good though and I am going to start to look into it!Normhttp://www.blogger.com/profile/04761161899743823748noreply@blogger.comtag:blogger.com,1999:blog-6003063374827736283.post-16809460724608522002007-12-04T08:58:00.000-08:002007-12-04T08:58:00.000-08:00MikoI think the idea of a standardized model for a...Miko<BR/><BR/>I think the idea of a standardized model for a Registry/Repository is very appealing - and I'd even like to see an open source project to build out a framework for validation and governance too. I completely agree about the value of this.<BR/><BR/>PaulPaul Fremantlehttp://www.blogger.com/profile/15326219720808613358noreply@blogger.comtag:blogger.com,1999:blog-6003063374827736283.post-21043084925884537332007-12-04T08:46:00.000-08:002007-12-04T08:46:00.000-08:00I think that registry repository will be a fairly ...I think that registry repository will be a fairly easy component to develop in an open source way.<BR/><BR/>Hopefully a project like this would eventually become the core of all registry repositories, given that it is sufficiently standards-compliant that it can meet organizational needs.<BR/><BR/>I would certainly be open to discussing federation with such a registry repository and Software AG Centrasite (a product with both Infravio and Software AG roots).<BR/><BR/>This would be like many enterprises and their use of Eclipse as a platform for creating all kinds of tooling.<BR/><BR/>The reason why I propose such a thing is because there's registry repository validation which is a facet of governance, but we have found that building governance applications on top of a standards-based (in our case JAXR provider 1, UDDI and ebXML Registry Repository) is what most large organizations need, not just the core registry repository functions.<BR/><BR/>This would include workflows, approvals and ways to federate disparate IT constituencies. RSS, REST and other lightweight content models are excellent of course. <BR/><BR/>The economic value of the registry repository platform so far has been in enabling enterprises to govern not just design time validation, but the whole lifecycle. I'm sure that makes a ton of sense to you as I know you have very strong runtime understanding...<BR/><BR/>MikoMiko Matsumurahttp://www.blogger.com/profile/06104074479680832271noreply@blogger.comtag:blogger.com,1999:blog-6003063374827736283.post-10468677274649460232007-12-03T11:30:00.000-08:002007-12-03T11:30:00.000-08:00Paul,Agree with your UDDI analysis and I don't thi...Paul,<BR/><BR/>Agree with your UDDI analysis and I don't think there is ever going to be huge support for UDDI specification. I'm working for a telco standards group at the moment that is debating the merits of recommending a public/shared UDDI repository. I'm definitely interested in taking a look at the REST based registry/repository.Jimhttp://www.blogger.com/profile/09668998452398136785noreply@blogger.com