- From: Kingsley Idehen <kidehen@openlinksw.com>
- Date: Wed, 21 Jan 2015 10:12:28 -0500
- To: public-linked-json@w3.org
- Message-ID: <54BFC1DC.8040005@openlinksw.com>
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/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:46 GMT Server: Google Frontend Alternate-Protocol: 80:quic,p=0.02 curl -IH "Accept: application/json+ld" http://schema.org/Action 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:09:49 GMT Server: Google Frontend Alternate-Protocol: 80:quic,p=0.02 -- 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
Attachments
- application/pkcs7-signature attachment: S/MIME Cryptographic Signature
Received on Wednesday, 21 January 2015 15:12:51 UTC