Markus, this is another awesome utility. Automatic JSON --> XDI mapping.
In looking through the examples I realize it works because:
All JSON object key values are valid XRIs.
In collections with multiple members, the members can be identified with UUIDs.
On that latter point, the mapping isn't persistent, i.e., each time you do the conversion you'll get a different UUID. So I think you might want to put this UUID value into a special context such as $temp or $rand to each of them so that an XDI processor knows it is not an i-number that it can expect to produce a persistent mapping.
This same approach, BTW, is what I was thinking for how to map RDF into XDI. That should be pretty easy for the same reason. It's going the other way (XDI --> RDF) that will be more challenging (but should be doable once we map out all the rules).
=Drummond
On Fri, Dec 14, 2012 at 8:20 AM, Markus Sabadello <> wrote:
In order to be able to map non-XDI data sources such as Facebook, Google Calendar, etc. to XDI, I am thinking it would be useful to have a generic JSON->XDI mapping ability, because that's the format that most of these APIs are based on.
So I played with this a bit, you can go to
http://xdi2.projectdanube.org/XDIConverter
Select "RAW JSON" as the input format, and try sample 5 or sample 6 or any other JSON format.
Markus
--
You received this message because you are subscribed to the Google Groups "XDI2" group.
To post to this group, send email to .
To unsubscribe from this group, send email to .
For more options, visit https://groups.google.com/groups/opt_out.
