W3C home > Mailing lists > Public > public-linked-json@w3.org > June 2011

RE: experiences promoting a JSON format for RDF

From: Brian Peterson <publicayers@verizon.net>
Date: Tue, 31 May 2011 22:40:19 -0400
To: "'Ed Summers'" <ehs@pobox.com>, <public-linked-json@w3.org>
Message-id: <008201cc2005$3fa44fc0$beecef40$@net>
Hi Ed,

Thanks for the feedback! It's been a pretty successful way of getting RDF
into our resources without requiring developers to learn and understand RDF
specifically.

I agree that the link structure is wordy. The idea was for the link keyword
to play the role that the link element does in XHTML. So if there was a
"next" link, then it would be in there as well. It maps from the rel value
to another structure to allow for easy lookup on JS. If you want the
"profile" link, then just dereference the "profile" keyword. The value is a
structure representing the link along the lines of what the Web Linking RFC
describes ([1]).

Thanks for the references to JSON schema and Google discovery. In hindsight,
I think I do prefer what section 6.1 in JSON Schema describes. In fact, I
might go ahead and incorporate the change.

BP

[1] http://tools.ietf.org/html/rfc5988


-----Original Message-----
From: public-linked-json-request@w3.org
[mailto:public-linked-json-request@w3.org] On Behalf Of Ed Summers
Sent: Tuesday, May 31, 2011 9:57 AM
To: public-linked-json@w3.org
Subject: Re: experiences promoting a JSON format for RDF

Thanks for posting this Brian. I really liked your summary of how you
got folks in your enterprise to think more in terms of REST, URIs and
resource descriptions. I've had a very similar experience where I
work, but haven't been able to summarize it as neatly as you just did
:-) A frew questions came to mind while reading your post.

The way that profiles are expressed does look a little wordy, with
'profile' being repeated:

   link : {
     profile : {
       rel : "profile",
       anchor : "http://ex.org/vocabs/hr/profile"
     }
   }

Is the idea that you would have other types of links in there? What
would it look like if you happened to mix together two profiles? Or is
the idea that there would be a resource would only be associated with
one profile, and would like to other resources that have a different
profile?

In your implementation have you decided to allow GETs to
http://ex.org/vocabs/hr/profile, and if you do, what do you return?

Have you looked at all at JSON Schema [1] which has some guidance on
creating links [2]. I'd heard about it a bit in a few places, but
recently ran across a reference to it in the documentation for
Google's new API Discovery Service [3].

//Ed

[1] http://tools.ietf.org/html/draft-zyp-json-schema
[2] http://tools.ietf.org/html/draft-zyp-json-schema#section-6.1
[3] http://code.google.com/apis/discovery/
Received on Wednesday, 1 June 2011 02:40:48 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 16:25:34 GMT