The Burgeoning Openly Owned Web

What would be good to do with Soapod is to combine
the notion of a message router and application server - then u can do great stuff like URI based service lookup - essentially the node routes traffic a la IP but deals with the application request should the service exist on the node.

But what about the case of many services of the same type existing? In this case the node reporting the many services returns the list to the client which chooses wither manually or using a recommender based on the original client’s local knowledge/preferences. This could be negated by the selection of appropriate URI naming schemes if tagged based invocation requests did not suffice.
Perhaps a good vehicle to explore this idea would be Mule - an OSS ESB. What would be required is a dynamic registry of registered services (did somebody say OSGi? :-D) and their corresponding URIs. This OSGi service registry would ideal back end on to a folksonomic DHT service registry - a service already implemented in Soapod.

Expand: Enterprise mashups - resource oriented computing - services are queryable by RSS
e.g. a registry service:

http://host/registryService?listServices

returns a list of services available in the repository in RSS format

http://host/registryService?listServices&Tag=Photo

returns a list of photo services available in the repository in RSS format

Tokyo Black Star - Blade Dancer (Dixon Edit) from the album “Fabric 25 Carl Craig” by Carl Craig