Registration and Discovery

Note that simply hosting your own instance of an XDI2 server for your own XDI graph does NOT add your cloud name and cloud number to an XDI registry. In other words, your XDI endpoint is perfectly able to receive and respond to incoming XDI messages, but it cannot be discovered by an XDI client that does not know the location of your XDI endpoint.

The purpose of registries is to answer XDI discovery requests for finding the XDI endpoint associated with a cloud name, cloud number, or discovery key (see also the Performing XDI discovery page for more details). Cloud names and cloud numbers may be registered in multiple registries.

Depending on the exact use case, it may be appropriate to run a registry for one's own community. A registry may not even be needed at all, if the involved XDI endpoints for a particular application or service are already known or can be found through an out-of-band mechanism.

Which registry to use and how exactly to register cloud names and cloud numbers is out of scope of this documentation page.