Yep. I agree.  We currently have this topology: `com/rackspacecloud/service-registry-client`.  I don't think it makes sense to also create `com/rackspacecloud/service-registry-client-curator-bindings`.  Instead I think we should introduce a another level to the hierarchy (curator is an example of this):  `com/rackspacecloud/service-registry/service-registry-client` and `com/rackspacecloud/service-registry/curator-bindings`.

wdyt?