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

Re: experiences promoting a JSON format for RDF

From: Ed Summers <ehs@pobox.com>
Date: Tue, 31 May 2011 09:57:13 -0400
Message-ID: <BANLkTinZUQZ_PTim5zL34DcKH1WYUW-M5Q@mail.gmail.com>
To: public-linked-json@w3.org
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 Tuesday, 31 May 2011 13:57:43 GMT

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