Re: Browsers and JSON-LD Re: Context Questions

Hi Kingsley,

That's my point -- we don't have control of the entire stack, and thus need
extensions and custom code to make things work.  I understand the rationale
behind a new media type, but in the interim period of it being official but
not widely supported, there will be a lot of systems just sending
application/json for convenience.

R



On Tue, Feb 4, 2014 at 8:41 AM, Kingsley Idehen <kidehen@openlinksw.com>wrote:

> On 2/4/14 12:15 AM, Andreas Kuckartz wrote:
>
>> Robert Sanderson:
>>
>>> * web browsers don't understand application/ld+json, meaning that for a
>>> developer it gets downloaded rather than rendered.  Not a big deal but
>>> ...
>>>
>> What should browsers do, simply display the JSON-LD document as it is ?
>>
>> Has anyone already created issues in the Firefox / Chromium issue
>> trackers ?
>>
>> Cheers,
>> Andreas
>>
>>
>>
>>  This is where browser extensions come into play. For instance, we've
> added support for JSON-LD, since inception, to our URIBurner service [1],
> ODE browser extensions [2], and the Virtuoso sponger middleware [3].
>
> [1] http://linkeddata.uriburner.com -- URIBurner
> [2] http://ode.openlinksw.com -- OpenLink Data Explorer extensions for
> all major browsers
> [3] http://bit.ly/1ev3jHr -- Virtuoso Sponger Middlewe
> Cartridges/Providers/Drivers (all of which also output JSON-LD optionally) .
>
> --
>
> 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
>
>
>
>
>
>