Hydra Vocab and Content Negotiation

Markus,

The following sequence still leads to JSON-LD that is unreadable by 100% 
of the browsers on the Web, due to the fact that they have no idea what 
JSON-LD (content-tye: application/ld+json) content is etc..

All you have to do is setup the resolution of 
<http://www.w3.org/ns/hydra/core#> (using a dynamic content negotiation 
QoS algorithm) such that in the very worst case text/plain is served to 
browsers. Fundamentally, you should offer text/plain, text/turtle, and 
application/ld+json.

Today, when people work with Linked Data the following pattern is quite 
common:

1. encounter a namspeace
2. use prefix.cc to lookup the namespace .


Today, the sequence above results in a download of a file, rather than a 
display of content in the browser. Even a hardcore JSON enthusiast will 
be confused by the current experience.

Just relay this request to the W3C server admins and they can sort this 
out for you.

-- 

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