Re: change in site behavior

We expect to replace the HTTP content negotiation with the use of a Link
header as specified in the latest JSON-LD specs

 i.e.

Link: </docs/jsonldcontext.jsonld
<https://schema.org/docs/jsonldcontext.jsonld>>; rel="alternate";
type="application/ld+json"

...with a corresponding to CORS too

I'm told there are at least 5 JSON-LD implementations that pass the test
for this feature, see
https://w3c.github.io/json-ld-api/tests/remote-doc-manifest#tla03

Dan


On Thu, 21 May 2020, 15:52 Guha, <guha@google.com> wrote:

> It is an intentional consequence of the DOS attack from earlier in the
> week.
>
> On Thu, May 21, 2020 at 6:57 AM Dave Vieglais <dave.vieglais@gmail.com>
> wrote:
>
>> Hi,
>>
>> Previously a HTTP request to "http://schema.org/" or "https://schema.org/"
>> with Accept header "application/ld+json, application/json" would redirect
>> to the schema.org context located at
>> https://schema.org/docs/jsonldcontext.jsonld and so provided a
>> convenient way to specify a remote reference the schema.org context.
>>
>> This behavior appears to be changed now, and instead the HTML page is
>> returned.
>>
>> Just curious if the new behavior is intentional or an inadvertent
>> consequence of the connectivity issues earlier this week?
>>
>> thanks
>>
>>
>> ----
>> Dave Vieglais
>> WebID: https://orcid.org/0000-0002-6513-4996
>> Institution: https://ror.org/001tmjg57
>>
>>
>>
>>
>>