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] new proposal: JSONXDIMapping


Awesome work. Instead of our JSONSerializationRules, which define how to do full lossless conversion of the XDI graph model into JSON, you have defined the inverse.

I find it fascinating to see how the basic concepts of the XDI graph model can be applied to describing any JSON data. I think the use of content addressing is brilliant (of course in the full proposal the actual content addressing algorithm needs defining).

I think I found a bug in the example -- in the JSON it says:

     "age": 25,
...but in the XDI translation it says:
Am I missing something?

This also dovetails perfectly with what I have been thinking about how to convert any RDF graph into an XDI graph. That, too, would have to use content addressing.

I haven't made any formal proposal yet because it hasn't been a high enough priority, but your proposal helps pave the way for it.


On Sat, Dec 29, 2012 at 3:25 PM, Markus Sabadello <markus.sabadello@xdi.org> wrote:
I created this proposal: https://wiki.oasis-open.org/xdi/JSONXDIMapping

It reflects some experimental implementation work I've done here (you have to select "RAW JSON" in the left drop-down box):

"This proposal defines a non-normative mapping from any arbitrary JSON data to the XDI graph model. Note that this proposal fulfills an entirely different purpose than JSONSerializationRules, which is an important JSON-based serialization format for the XDI graph model. One envisioned application of this mapping is to be able to make non-XDI, JSON-based web APIs compatible with XDI, through the development of XDI connectors."

I marked it as low priority, and I would consider it an informal, non-normative proposal.
Maybe it would not even be part of the core spec, rather an appendix or comment or something like that.


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