Re: Process of "following your nose"

Interesting! So we could send an Accept header like this:

application/ld+json;q=0.9,application/rdf+xml,application/x-turtle,text/rdf+n3,text/turtle,text/n3;q=0.8,application/json,text/csv,text/plain;q=0.7,*/*

If we get back application/ld+json, we can immediately transclude the response. Otherwise:
* for q=0.9 content types, convert to JSON-LD and transclude
* for q=0.8 or 0.7 content types, test for whether response represents RDF statements and convert/transclude if possible.

----- Original Message -----
> From: "Kingsley Idehen" <kidehen@openlinksw.com>
> To: public-linked-json@w3.org
> Sent: Saturday, May 31, 2014 5:10:46 PM
> Subject: Re: Process of "following your nose"
> 
> On 5/31/14 11:47 AM, Anders Riutta wrote:
> > Hi Alex,
> >
> > Thanks for the response.
> >
> > If we know the IRI is dereferenceable, don't we still have to check the
> > content type? For example,  if
> > dereferencing<http://dbpedia.org/resource/Cynthia_Lennon>  only returned
> > HTML, we couldn't use it to directly transclude additional JSON-LD.
> >
> > But if we could get different content types, including JSON-LD,
> > from<http://dbpedia.org/resource/Cynthia_Lennon>, we could transclude the
> > JSON-LD. Unfortunately, we wouldn't know without testing how to get the
> > JSON-LD. It could be any of these:
> > 1)<http://dbpedia.org/resource/Cynthia_Lennon>  with an Accept
> > request-header field value of "application/json"
> > 2)<http://dbpedia.org/resource/Cynthia_Lennon>  with an Accept
> > request-header field value of "application/ld+json"
> > 3)<http://dbpedia.org/resource/Cynthia_Lennon/.json>  without an Accept
> > request-header
> > 4)<http://dbpedia.org/resource/Cynthia_Lennon/.jsonld>  without an Accept
> > request-header
> > 5)<http://dbpedia.org/resource/Cynthia_Lennon?format=json>  without an
> > Accept request-header
> >
> > The documentLoaders
> > code<https://github.com/digitalbazaar/jsonld.js/blob/master/js/jsonld.js#L1522>
> > would work for 1) and 2), but not for 3) - 5).
> >
> > Thanks,
> > Anders
> 
> Here is a vapor [1] report that should illustrate this matter.
> Fundamentally, in the context of Linked Data, JSON-LD (like Turtle,
> N-Triples, HTML+Microdata, RDF/XML etc..) is just another notation for
> representing RDF statements that describe entities (e.g., from DBpedia).
> 
> Links:
> 
> [1] http://bit.ly/1ty5FZW -- Vapor Report where the User Agent (Vapour)
> uses RDF to make sense of what
> <http://dbpedia.org/resource/Cynthia_Lennon> denotes.
> 
> --
> 
> Regards,
> 
> Kingsley Idehen
> Founder & CEO
> OpenLink Software
> Company Web: http://www.openlinksw.com
> Personal Weblog: http://www.openlinksw.com/blog/~kidehen
> Twitter Profile: https://twitter.com/kidehen
> Google+ Profile: https://plus.google.com/+KingsleyIdehen/about
> LinkedIn Profile: http://www.linkedin.com/in/kidehen
> 
> 
> 
> 
> 
>

Received on Sunday, 1 June 2014 15:41:30 UTC