The registry graph

The so-called "registry" graph represents the graph of the cloud service provider (CSP) itself. It contains an XDI peer root for every "user" graph that should be exposed at an XDI endpoint.

"User" graphs can therefore be created and deleted by adding/removing XDI peer roots (and some additional information) to/from the "registry" graph, using standard XDI operations.

Assumptions

• The CSP's cloud name and cloud number are +testcsp / [+]!:uuid:9999.
• The user's cloud name and cloud number are =alice / [=]!:uuid:1111.

Cloud Number

The "registry" graph must at a minimum contain an XDI peer root for the user's cloud number:

//([=]!:uuid:1111)

Cloud Name

The "registry" graph should contain $ref and $is$ref statements that establish and link the user's cloud name and cloud number:

(=alice)/$ref/([=]!:uuid:1111)
([=]!:uuid:1111)/$is$ref/(=alice)

## Secret Token

The "registry" graph may also contain the user's hashed secret token, which will be used by the AuthenticationSecretTokenInterceptor to authenticate the user:

([=]!:uuid:1111)<$digest><$secret><$token>/&/"xdi2-digest:XXXX"