[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [xdi] RE: [External] [xdi] How to parse XDI DISPLAY format
I dont think that has changed, but I still believe the syntax of a statement should be properly defined, for those who do want to use XDI DISPLAY format. And statements are used in other contexts as well, e.g. in messaging.
Markus
I thought the TC had agreed that the only on the wire protocol to be supported in the core spec would be XDI JSON, that XDI Display was only for displaying XDI data on screen and/or on the page.
Is the consensus now that we will support both protocols on the wire?
Kind regards,
Bill Barnhill
Booz Allen Hamilton - Belcamp,MD
Cell: 1-443-924-0824
Desk: 1-443-861-9102
From: xdi@lists.oasis-open.org [mailto:xdi@lists.oasis-open.org] On Behalf Of Markus Sabadello
Sent: Tuesday, November 13, 2012 4:08 PM
To: OASIS - XDI TC
Cc: Michael Andronov
Subject: [External] [xdi] How to parse XDI DISPLAY format
Hi XDI TC,
Today on the XDI Implementer's Call I had a longer discussion with Michael Andronov, who has successfully stored XDI data in Affinity..
One of the things we talked about was the proper way to parse XDI DISPLAY format.
This proposal only says that there is one XDI statement per line, but it doesn't specify the syntax of an XDI statement.
And then page 8 of the XDI Graph Model document has some information about XDI Addressing that is relevant.
So I think the XDI DISPLAY proposal should say that an XDI statement is this (based on the rules on page 8 of the XDI Graph Model).
xdi-subject "/" xdi-predicate "/" xdi-object
Does this sound right?
I also think there should be an explanation why an XDI statement cannot be defined with XRI 3.0 syntax alone, i.e.
xri-segment-nz "/" xri-segment-nz "/" xri-segment-nz
Markus
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]