Re: Defining a common convention for marking up JSON

Thanks for the comments Rob.



Yes, I'll grant that my hopes of making this extensible for custom keywords requires either a registry mechanism or a way to associate with a namespace.



Or both -- the two are actually not mutually exclusive. We can reserve a few "common" prefixes (like "jsonld" and "odata") and allow others to be associated with namespaces through a general mechanism.



OData actually already has the ability to associate a namespace with a prefix, but it doesn't (yet) prepend the "@" symbol to differentiate the "keywords" from other properties that might contain a period. It would be great if JSON-LD had a way to do the same thing, but for now I'm happy with just prefixing the JSON-LD keywords with a well-known prefix. :)

As far as convincing the rest of the JSON developers, if OData and JSON-LD can agree on a convention, then I think that will help drive others to adopt the same convention. And even if it doesn't become a ubiquitous convention, at least we have better compatibility/interoperability between OData and JSON-LD.



From: Robert Sanderson <azaroth42@gmail.com<mailto:azaroth42@gmail.com?Subject=Re%3A%20Defining%20a%20common%20convention%20for%20marking%20up%20JSON&In-Reply-To=%3CCABevsUEvat_JCP1ih%2By%2BRiWqL8DhEQ5t%2BUNy-NgRCAnTETq2iw%40mail.gmail.com%3E&References=%3CCABevsUEvat_JCP1ih%2By%2BRiWqL8DhEQ5t%2BUNy-NgRCAnTETq2iw%40mail.gmail.com%3E>>
Date: Tue, 24 Sep 2013 15:57:48 -0600
Message-ID: <CABevsUEvat_JCP1ih+y+RiWqL8DhEQ5t+UNy-NgRCAnTETq2iw@mail.gmail.com>
Cc: "public-linked-json@w3.org<mailto:public-linked-json@w3.org?Subject=Re%3A%20Defining%20a%20common%20convention%20for%20marking%20up%20JSON&In-Reply-To=%3CCABevsUEvat_JCP1ih%2By%2BRiWqL8DhEQ5t%2BUNy-NgRCAnTETq2iw%40mail.gmail.com%3E&References=%3CCABevsUEvat_JCP1ih%2By%2BRiWqL8DhEQ5t%2BUNy-NgRCAnTETq2iw%40mail.gmail.com%3E>" <public-linked-json@w3.org<mailto:public-linked-json@w3.org?Subject=Re%3A%20Defining%20a%20common%20convention%20for%20marking%20up%20JSON&In-Reply-To=%3CCABevsUEvat_JCP1ih%2By%2BRiWqL8DhEQ5t%2BUNy-NgRCAnTETq2iw%40mail.gmail.com%3E&References=%3CCABevsUEvat_JCP1ih%2By%2BRiWqL8DhEQ5t%2BUNy-NgRCAnTETq2iw%40mail.gmail.com%3E>>

It's a little more than that I think...



You also need the other part of XML namespaces ... the URI for the

namespace, rather than the prefix, to distinguish my "@jsonld." from

someone else's "@jsonld."  And then you need a way to link them, and thus a

magic equivalent to xmlns.

Alternatively you need to maintain a registry of "@(namespace)."

descriptions.

And finally you need a way to convince JSON developers that this is at all

useful to anyone.



I think the last of those is the most challenging, especially when it's not

built into the JSON specification.



Best of luck! :)



Rob