OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

xdi message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: RE: [xdi] Introducing XDI² (XDI-Squared)

Great work Markus!


Do we have a standar XDI data set and queries to run on the different server implementations in order to compare/benchmark them?


One thought in terms of real life data...Joe Johnston tweeted about a 5m user data set. If we converted that into XDI, after anonymizing by hashing names and twitter ids. then that could be our test data set.  It has the benefit of having real world characteristics. 


Alternatively there is research performed which produced test social network datasets that were realistic based on Social Network Analysis - maybe we could find one of those packages and adapt it to XDI.


Kind regards,
Bill Barnhill

From: xdi@lists.oasis-open.org [xdi@lists.oasis-open.org] on behalf of Michael Schwartz [mike@gluu.org]
Sent: Thursday, February 16, 2012 9:47 AM
Cc: xdi@lists.planetwork.net
Subject: Re: [xdi] Introducing XDI² (XDI-Squared)

This is awesome!  Nicely done Markus!


Michael Schwartz
Founder / CEO
+1 646-810-8761

On Thu, 16 Feb 2012, Markus Sabadello wrote:

> Hi all,
> Here's the fresh XDI codebase I mentioned a few times..
> I've been working on this for a while and now packaged it up:
> http://xdi2.projectdanube.org/ (main page and sample deployment)
> https://github.com/peacekeeper/xdi2 (code and wiki)
> So far it has the following:
> - Basic implementation of the XDI graph model
> - In-memory store, text file based store, and Berkeley DB based store
> - XDI client and server
> - (De-)Serialization in two formats: XDI/JSON,  and plain list of XDI
> statements
> - Some of the good old tools are also back, e.g. XDI Converter, XDI
> Messenger
> It should be very easy to download and run (just do "mvn clean install").
> It has no complicated dependencies and is designed to be general-purpose
> and modular, to support a wide range of use cases.
> It's called XDI², because the idea is to have code both for traditional
> client/server communication, and to also include some of the peer-to-peer
> functionality I have been working on for a while.
> E.g. you could deploy it on Freedom Boxes and have them communicate with
> each other via serverless XDI.
> But this needs some more work and cleaning up..
> It would be great to work on this some more (and to migrate Project Danube
> from XDI4j to XDI²), but this depends a little bit on time, on the
> stability of the specs, and on whether there is even need for another
> library (considering there is already OpenXDI)... It'd be great to get some
> advice on this.
> Markus

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]