anonymous wrote : At the moment we're really looking at the first steps though: more like a basic naming service. So I wouldn't expect we're looking at anything more complex than an EPR. Would you? No, I agree for now EPR is what we should be going after, I just brought this up as an analogy. anonymous wrote : Is this not where the Logical Name comes in? From the outset we've talked about two types of names: | | (i) the "physical" name, which is the EPR and needed to address the service. This name may be obtained from the Registry or from elsewhere. But the Registry is the preferred approach. | | (ii) the "logical" name, which is a convenient short-hand, like "Kurt's Travel Agency". Obviously in order to interact with a service you need a real address, so if all you've got is a logical name you need some way of mapping one to the other. That's where the Registry comes in again. The Registry maintains a tuple space of <logical name, physical name>. | | We could set the logical name as the URI. As you say, something like: epr:jbossesb:version:1.0:logicalname:KurtsTravelAgency Every Service and ServiceBinding can have a name. This name is used when querying for a service. The physical and logic names you refer to are more 'addresses' to me. But I agree with what you say. OK so I guess we now have: -ServiceBinding.name = "Kurt's Travel Angency" -ServiceBinding.URI = "epr:jbossesb:version:1.0:logicalname:KurtsTravelAgency" I'm going to see how we should be using the 'tModel' to store the EPR. I think it will be something like this: -ServiceBinding.Concept = the EPR-XML -ServiceBinding.Classification = "jbossesb-aware" but let me look into this a little. I pretty sure we gain searchability from classifying things. So the way we organize things may help us when searching for a Service. --Kurt View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3979398#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...