Comments on Seth Ladd's Blog: REST, Hypermedia, and JSON

More than just tagging your URIs in your JSON form...

2011-03-21T21:13:28.618-07:00

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/ .

doing regex on a bunch of strings to guess if they...

2011-03-21T21:13:28.139-07:00

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

[...] public links >> hypermedia REST, Hyp...

2011-03-21T21:13:27.816-07:00

[...] public links >> hypermedia REST, Hypermedia, and JSON Saved by RexUK on Tue 07-10-2008 Hypermedia umieszczone na liście “Forrester Research” Saved [...]

[...] public links >> hypermedia REST, Hyp...

2008-10-08T09:34:30.000-07:00

[...] public links >> hypermedia REST, Hypermedia, and JSON Saved by RexUK on Tue 07-10-2008 Hypermedia umieszczone na liście “Forrester Research” Saved [...]

[...] On software architecture, Connecting, REST, ...

2008-04-16T23:52:54.000-07:00

[...] On software architecture, Connecting, REST, Hypermedia, and JSON [...]

More than just tagging your URIs in your JSON form...

2008-04-03T00:28:28.000-07:00

Agreed, you don't want to guess if the string ...

2008-03-24T04:35:01.000-07:00

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.

doing regex on a bunch of strings to guess if they...

2008-03-24T04:30:30.000-07:00

I looked at the SPARQL JSON mapping, but it's ...

2008-03-24T01:15:11.000-07:00

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 worked on a "tourist system" in 1989-1...

2008-03-23T16:23:08.000-07:00

I worked on a "tourist system" in 1989-1990 direction using HyperCard. We ended up putting all the hyperlinks in a database.