Comments on: REST, Hypermedia, and JSON http://www.semergence.com/2008/03/23/rest-hypermedia-and-json/ Semantic Web, Ruby on Rails, and Massive Data Sat, 05 Jul 2008 01:40:16 +0000 http://wordpress.org/?v=2.2.3 By: Nodalities » Blog Archive » This Week’s Semantic Web http://www.semergence.com/2008/03/23/rest-hypermedia-and-json/#comment-596 Nodalities » Blog Archive » This Week’s Semantic Web Thu, 17 Apr 2008 16:52:54 +0000 http://www.semergence.com/2008/03/23/rest-hypermedia-and-json/#comment-596 [...] On software architecture, Connecting, REST, Hypermedia, and JSON [...] […] On software architecture, Connecting, REST, Hypermedia, and JSON […]

]]> By: igwan http://www.semergence.com/2008/03/23/rest-hypermedia-and-json/#comment-575 igwan Thu, 03 Apr 2008 17:28:28 +0000 http://www.semergence.com/2008/03/23/rest-hypermedia-and-json/#comment-575 More than just tagging your URIs in your JSON format, you have to define somewhere (in your format spec) what the client can do with them or your representations fail to be self-describing. There's no generic way for including hypermedia in JSON to my knowledge, so you'd need to define your own "application/myformat+json" media-type. In HTML it is perfectly defined what a client can do with the HREF value in an anchor tag or with the URIref in the ACTION attribute of a FORM. It's not so in plain RDF, unless you define that resources having certain types can be GET, PUT or POSTed to. There's an attempt at this called RDF Forms http://www.markbaker.ca/2003/05/RDF-Forms/ . More than just tagging your URIs in your JSON format, you have to define somewhere (in your format spec) what the client can do with them or your representations fail to be self-describing. There’s no generic way for including hypermedia in JSON to my knowledge, so you’d need to define your own “application/myformat+json” media-type.
In HTML it is perfectly defined what a client can do with the HREF value in an anchor tag or with the URIref in the ACTION attribute of a FORM. It’s not so in plain RDF, unless you define that resources having certain types can be GET, PUT or POSTed to. There’s an attempt at this called RDF Forms http://www.markbaker.ca/2003/05/RDF-Forms/ .

]]> By: admin http://www.semergence.com/2008/03/23/rest-hypermedia-and-json/#comment-552 admin Mon, 24 Mar 2008 21:35:01 +0000 http://www.semergence.com/2008/03/23/rest-hypermedia-and-json/#comment-552 Agreed, you don't want to guess if the string is a URI. The simple hash is a good option there. And while formats like N3 have identified URI as a first class type, JSON has so many tools and is integrated directly into the language of the Web (Javascript) that it's going to take a lot to replace JSON with N3. I definitely intend to return HTML, JSON, RDF/XML, and <a href="http://www.dajobe.org/2004/01/turtle/" rel="nofollow">Turtle</a>. Agreed, you don’t want to guess if the string is a URI. The simple hash is a good option there.

And while formats like N3 have identified URI as a first class type, JSON has so many tools and is integrated directly into the language of the Web (Javascript) that it’s going to take a lot to replace JSON with N3.

I definitely intend to return HTML, JSON, RDF/XML, and Turtle.

]]> By: ix http://www.semergence.com/2008/03/23/rest-hypermedia-and-json/#comment-551 ix Mon, 24 Mar 2008 21:30:30 +0000 http://www.semergence.com/2008/03/23/rest-hypermedia-and-json/#comment-551 doing regex on a bunch of strings to guess if theyre URIs really smells. i use {uri: 'http://someuri"} instead of a string. but i think URIs are realy important as a first class element of the syntax, and N3 is already invented, so the clock is ticking on JSON doing regex on a bunch of strings to guess if theyre URIs really smells.

i use {uri: ‘http://someuri”} instead of a string.

but i think URIs are realy important as a first class element of the syntax, and N3 is already invented, so the clock is ticking on JSON

]]> By: admin http://www.semergence.com/2008/03/23/rest-hypermedia-and-json/#comment-548 admin Mon, 24 Mar 2008 18:15:11 +0000 http://www.semergence.com/2008/03/23/rest-hypermedia-and-json/#comment-548 I looked at the SPARQL JSON mapping, but it's too verbose for my use case. I don't want to have to set the type and value for every attribute. For now, I'm simply using a fully qualified URI as the value for an attribute. It's up to the client to read the docs or specs to learn which attributes in the JSON are URIs. I'm happy I'm including URIs (links) in my JSON. Feels much more webby. I looked at the SPARQL JSON mapping, but it’s too verbose for my use case. I don’t want to have to set the type and value for every attribute.

For now, I’m simply using a fully qualified URI as the value for an attribute. It’s up to the client to read the docs or specs to learn which attributes in the JSON are URIs.

I’m happy I’m including URIs (links) in my JSON. Feels much more webby.

]]> By: Bruce D'Arcus http://www.semergence.com/2008/03/23/rest-hypermedia-and-json/#comment-541 Bruce D'Arcus Mon, 24 Mar 2008 10:18:47 +0000 http://www.semergence.com/2008/03/23/rest-hypermedia-and-json/#comment-541 Why not borrow the approach used in the <a href="http://www.w3.org/TR/rdf-sparql-json-res/" rel="nofollow">SPARQL JSON results format</a>? E.g. <code> "account": { "type": "uri" , "value": "http://example.org/accounts/23242342" } , </code> Why not borrow the approach used in the SPARQL JSON results format? E.g.


"account": { "type": "uri" , "value": "http://example.org/accounts/23242342" } ,

]]> By: Colm Sean Kennedy http://www.semergence.com/2008/03/23/rest-hypermedia-and-json/#comment-539 Colm Sean Kennedy Mon, 24 Mar 2008 09:23:08 +0000 http://www.semergence.com/2008/03/23/rest-hypermedia-and-json/#comment-539 I worked on a "tourist system" in 1989-1990 direction using HyperCard. We ended up putting all the hyperlinks in a database. I worked on a “tourist system” in 1989-1990 direction using HyperCard. We ended up putting all the hyperlinks in a database.

]]>