W3C home > Mailing lists > Public > public-linked-json@w3.org > January 2015

Re: JSON-LD context file at schema.org - request for feedback

From: Kingsley Idehen <kidehen@openlinksw.com>
Date: Wed, 21 Jan 2015 12:51:24 -0500
Message-ID: <54BFE71C.7010805@openlinksw.com>
To: public-linked-json@w3.org
On 1/21/15 10:38 AM, ☮ elf Pavlik ☮ wrote:
> On 01/21/2015 04:12 PM, Kingsley Idehen wrote:
>> >On 1/21/15 8:05 AM, Dan Brickley wrote:
>>> >>The context is content negotiable from the site homepage but also
>>> >>available athttp://schema.org/docs/jsonldcontext.json.txt
>> >
>> >What should I be using in regards to cURL against the homepage?
>> >
>> >Note I've tried the following which 405:
>> >
>> >curl -IH "Accept: application/json+ld"http://schema.org/
>> >HTTP/1.1 405 Method Not Allowed
>> >Allow: GET
>> >Content-Type: text/plain; charset=UTF-8
>> >Content-Length: 77
>> >Date: Wed, 21 Jan 2015 15:08:42 GMT
>> >Server: Google Frontend
>> >Alternate-Protocol: 80:quic,p=0.02
> curl -IH "Accept: application/ld+json"http://schema.org
> HTTP/1.1 200 OK
> Access-Control-Allow-Origin: *
> Content-Type: application/ld+json
> Vary: Accept, Accept-Encoding
> Date: Wed, 21 Jan 2015 15:36:57 GMT
> Server: Google Frontend
> Content-Length: 4167
> Cache-Control: public, max-age=43200
> Age: 20
> Alternate-Protocol: 80:quic,p=0.02
>
>
>

Thanks for untangling my tangled mess of content-type names :)

Now when I copy and paste your example above, I get different results:

curl -IH "Accept: application/ld+json" http://schema.org
HTTP/1.1 405 Method Not Allowed
Allow: GET
Content-Type: text/plain; charset=UTF-8
Content-Length: 77
Date: Wed, 21 Jan 2015 17:48:04 GMT
Server: Google Frontend
Alternate-Protocol: 80:quic,p=0.02

Here's what works:

curl -iH "Accept: application/ld+json" http://schema.org
HTTP/1.1 405 Method Not Allowed
Allow: GET
Content-Type: text/plain; charset=UTF-8
Content-Length: 77
Date: Wed, 21 Jan 2015 17:48:04 GMT
Server: Google Frontend
Alternate-Protocol: 80:quic,p=0.02

Dan:

A few items:

1. Is there any chance of -I working alongside -i ?
2. Would it be possible for a .jsonld doc to be published, that set to content-type "application/ld+json" rather than a .txt file that currently returns content-type "text/html" ?


-- 
Regards,

Kingsley Idehen	
Founder & CEO
OpenLink Software
Company Web: http://www.openlinksw.com
Personal Weblog 1: http://kidehen.blogspot.com
Personal Weblog 2: 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
Personal WebID: http://kingsley.idehen.net/dataspace/person/kidehen#this


Received on Wednesday, 21 January 2015 17:51:47 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:18:43 UTC