Re: [xdi] oxServer for FreeXRI / FullXRI ?

On Thu, Jun 16, 2011 at 2:35 PM, Markus Sabadello <markus.sabadello@xdi.org> wrote:

Mike, Yuri,

Great to hear about the progress with your XDI server on today's call..

+1.

Once you have a first release, I am wondering what it would take to deploy it for FreeXRI's and FullXRI's I-Names/I-Numbers.

Today there is an XDI4j endpoint for each I-Name/I-Number, e.g. at https://xdi.fullxri.com/=markus/

Can a single oxServer provide XDI contexts/graphs/documents (sorry don't know the right term) for multiple XRIs?

All those terms are right, but I'm moving towards "XDI graphs" since it seems to be the most clear. My suggestion is that we use "XDI graph" to talk about any XDI graph rooted in the XDI root context (hollow circle in the graph notation), and "subgraph" to talk about any subset of an XDI graph that is rooted below the XDI root context. Then, for service providers, 1 XDI graph = 1 XDI account (whether for an individual or a business).

Or do there have to be separate instances of the server?

I hope not. Much better that it be like XDI4J, i.e., one OX server can serve as many XDI graphs (XDI accounts) as needed.

Also I am wondering, what XRD rel type would we use to point to an XDI endpoint?

Yes, great question, I was thinking about that too.

Previously we had been using:
xri://$xdi!($v!1)

My best guess for the "new" XDI would be:
($xdi$v$1)

Are you talking about a full XRI 3.0 compatible URI to use for the rel type? If so, I think it needs a URI binding (and best be an https: binding for security reasons). The only other change is that, according to our recent examples, the version number would be $v!1 because it is a persistent instance. So that would be:

https://xri.net/($xdi$v!1)

Thoughts?

=Drummond

xdi message