RE: [xdi] Proposed additional X3 representation format, or a replacement for X3 Whitespace

["Barnhill, William [USA]" <barnhill_william@bah.com>]

Hi Drummond,

What do you think of adding a fourth serialization that I think may be important for XDI adoption: RDF/N3 (due to its installed base and for compatibility reasons) ?

Kind regards,

Bill Barnhill
Booz Allen Hamilton - Rome, NY
315-330-7386  | william.barnhill.ctr@rl.af.mil | barnhill_william@bah.com
________________________________________
From: drummond.reed@gmail.com [drummond.reed@gmail.com] On Behalf Of Drummond Reed [drummond.reed@xdi.org]
Sent: Wednesday, December 30, 2009 2:56 AM
To: Nika Jones
Cc: Barnhill, William [USA]; Markus Sabadello; OASIS - XDI TC
Subject: Re: [xdi] Proposed additional X3 representation format, or a   replacement for X3 Whitespace

Nika, I'm not a JSON expert so I'll defer to Markus and Bill (and any others on this list). But I appreciate your suggestions. I assume you like the idea of using JSON as one of the primary XDI serialization formats.

I discussed this with Markus a little today and I see strong cases for three serialization formats:

1) XML - due to its installed base
2) JSON - due to its installed base
3) X3 - due to its simplicity and readability/writability especially in X3 Simple format.

In my opinion the scope of the XDI Serialization spec should be limited to these three formats to keep interoperability as high as possible (it's already hard to justify three serialization formats but there is a strong case for each.)

=Drummond

On Tue, Dec 29, 2009 at 11:40 PM, Nika Jones <njones@ouno.com<mailto:njones@ouno.com>> wrote:
I'm pretty new to the XDI stuff (but I do want to get more involved)
...Could the X3J escape a string like the X3Whitespace?

So Cross References would look like:

{
    "=markus":
    {
        "+friend":    "\"=bill.barnhill\""
    }
}

or even:

{
    "=markus":
    {
        "+friend":    "'=bill.barnhill'"
    }
}

as the quote surrounding the text doesn't matter in JSON?

Nika

> Both good questions, I'll address them both in full  soon as possible but
> that won't be for a couple days as I'm really under the gun right now.
> Markus, the short answer to your question for was that I was using 'x' to
> mean ref, and "x" to mean string, but that's a language specific artifact.
> My initial thought is that
> {"+friend": "=Bill.Barnhill"} means value is a String (which could be an
> XRI if it validates as one), and
> {"+friend": {"=Bill.Barnhill": undefined}}
>
> Seems closest to my initial thinking but alas does not work in
> JSON.stringify, so perhaps
> {"+friend": {"=Bill.Barnhill": nulll}}
> or
> {"=markus": {"+friend": {"=Bill.barnhill": {} } } } <-- Despite lispish
> feel I probably like this one best of the ones that work.
>
>
> Kind regards,
>
> Bill Barnhill
> Booz Allen Hamilton - Rome, NY
> 315-330-7386  | william.barnhill.ctr@rl.af.mil<mailto:william.barnhill.ctr@rl.af.mil> | barnhill_william@bah.com<mailto:barnhill_william@bah.com>
> ________________________________________
> From: drummond.reed@gmail.com<mailto:drummond.reed@gmail.com> [drummond.reed@gmail.com<mailto:drummond.reed@gmail.com>] On Behalf Of
> Drummond Reed [drummond.reed@xdi.org<mailto:drummond.reed@xdi.org>]
> Sent: Monday, December 28, 2009 5:39 PM
> To: Markus Sabadello
> Cc: Barnhill, William [USA]; OASIS - XDI TC
> Subject: Re: [xdi] Proposed additional X3 representation format, or a
> replacement for X3 Whitespace
>
> Good question, Markus. I was looking over Bill's example and had a second
> question. The example shows that subcontexts begin with the string
> "_context". That, too, is a valid XRI string. I think it would be a
> mistake to start reserving XRIs to have special semantics unless they are
> $ words defined for this purpose.
>
> So that's a second issue we need to address if we are going to make X3J
> part of the XDI Serialization spec.
>
> =Drummond
>
> On Mon, Dec 28, 2009 at 8:20 AM, Markus Sabadello
> <markus.sabadello@xdi.org<mailto:markus.sabadello@xdi.org><mailto:markus.sabadello@xdi.org<mailto:markus.sabadello@xdi.org>>> wrote:
> Hi Bill,
>
> I tried implementing your X3J format, but I have a question:
> How would one distinguish between a literal and a reference?
>
> E.g. if I have this X3J data:
>
> {
>     "=markus":
>         {
>             "+friend":    "=bill.barnhill"
>         }
> }
>
> How would I know if it translates to this graph:
>
> =markus
>         +friend
>                 =bill.barnhill
>
> or to this graph:
>
> =markus
>         +friend
>                 "=bill.barnhill"
>
> ??
>
> Markus
>
> On Fri, Jul 3, 2009 at 12:27 AM, Barnhill, William [USA]
> <barnhill_william@bah.com<mailto:barnhill_william@bah.com><mailto:barnhill_william@bah.com<mailto:barnhill_william@bah.com>>> wrote:
>
> I've edited http://wiki.oasis-open.org/xdi/X3Format to add text proposing
> an X3 representation that is directly in JSON as opposed to similar to
> JSON.  Given the broad adoption of JSON and the usefulness of this I'm
> seeing in my work I wanted to share it with the TC.  JSON format is still
> rough but works. I will add formatting rules section this weekend.
> ---------------------------------------------------------------------
> To unsubscribe from this mail list, you must leave the OASIS TC that
> generates this mail.  Follow this link to all your TCs in OASIS at:
> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this mail list, you must leave the OASIS TC that
> generates this mail.  Follow this link to all your TCs in OASIS at:
> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
>
>