Re: Playground error or schema.org error?

Ivan, all

Investigating this issue has identified several individual things that led
to the presumption of an error.

*Background operation*
When the Schema.org application detects it is being asked for the jsonld
context file, it returns a http 302 redirect to '/docs/jsonldcontext.json'
which builds and returns the context file.  As an aside, an easily readable
version of that file is available at /docs/jsonldcontext.json.txt
<https://schema.org/docs/jsonldcontext.json.txt>

*Use of curl for testing*
As the response is a 302 redirect, the -L option is needed enabling it to
follow redirects.
Also as Tim points out, the correct Accept value should be
application/ld+json

*Behaviour of example provided (*https://tinyurl.com/y45ycru2)
In the example is the following line and the reported error:

 "@context": "http://schema.org/",

Potentially the context URI could be rewritten in the following ways with
at least some expectation that it would result in valid operation:

 "@context": "https://schema.org/",

 "@context": "https://schema.org",

 "@context": "http://schema.org",


In the Playground, only the last of these does not report an error.

Testing all four combinations using curl (with -L option and
application/ld+json as the Accept value) results in the correct format
being returned in every case.

This suggests to me that is an issue with the Playground, when encountering
https and/or trailing slashes in @context URIs.   My tests indicate that
the Schema.org application is functioning correctly in this area.


~Richard.




Richard Wallis
Founder, Data Liberate
http://dataliberate.com
Linkedin: http://www.linkedin.com/in/richardwallis
Twitter: @rjw



On Thu, 4 Apr 2019 at 15:57, Cole, Timothy W <t-cole3@illinois.edu> wrote:

> Ivan
>
>
>
> I set the Accept header to application/ld+json and get the correct result
> as of 2 minutes ago.  I also got the correct result with this header last
> week.
>
>
>
> I don't think Accept: application/json has ever worked to get the context
> document.
>
>
>
> Of course this may have no bearing on playground issue.
>
>
>
> -Tim Cole
>
>
>
> *From:* Ivan Herman <ivan@w3.org>
> *Sent:* Thursday, April 4, 2019 8:56 AM
> *To:* Richard Wallis <richard.wallis@dataliberate.com>
> *Cc:* Dan Brickley <danbri@google.com>; Gregg Kellogg <
> gregg@greggkellogg.net>; David I. Lehn <dil@lehn.org>; W3C JSON-LD
> Working Group <public-json-ld-wg@w3.org>
> *Subject:* Re: Playground error or schema.org error?
>
>
>
> Richard, Dan,
>
>
>
> thanks for the quick reactions!
>
>
>
> Ivan
>
>
>
> On 4 Apr 2019, at 15:07, Richard Wallis <richard.wallis@dataliberate.com>
> wrote:
>
>
>
> Ivan,
>
>
>
> Your expectation is correct - looking in to it now.
>
>
>
>
>
> ~Richard.
>
> Richard Wallis
>
> Founder, Data Liberate
>
> http://dataliberate.com
> <https://urldefense.proofpoint.com/v2/url?u=http-3A__dataliberate.com_&d=DwMFaQ&c=OCIEmEwdEq_aNlsP4fF3gFqSN-E3mlr2t9JcDdfOZag&r=1SG5aXop0rkp_O1wnbIf7XweTLUSe9Z3aj8AqEIzm8c&m=yMDQ1-tDX9IVpw-TlXQfMkw7wtmEw1QZj7Yc7wqaSFY&s=_NPcYIAMzhF5rhAnaKgzsTMu4aZsBQ9ii3Cal230Akk&e=>
>
> Linkedin: http://www.linkedin.com/in/richardwallis
> <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.linkedin.com_in_richardwallis&d=DwMFaQ&c=OCIEmEwdEq_aNlsP4fF3gFqSN-E3mlr2t9JcDdfOZag&r=1SG5aXop0rkp_O1wnbIf7XweTLUSe9Z3aj8AqEIzm8c&m=yMDQ1-tDX9IVpw-TlXQfMkw7wtmEw1QZj7Yc7wqaSFY&s=dJrhSCpNQDDkIcRf2Zya4pr13LC8AzeSz95BtzwJDIo&e=>
>
> Twitter: @rjw
>
> [image: Image removed by sender.]
>
>
>
>
>
> On Thu, 4 Apr 2019 at 13:59, Dan Brickley <danbri@google.com> wrote:
>
> + Richard Wallis
>
>
>
> We switched to a new version of site codebase on Monday. Richard, any
> ideas?
>
>
>
> On Thu, 4 Apr 2019, 05:24 Ivan Herman, <ivan@w3.org> wrote:
>
> Just wondering:
>
>
>
> https://tinyurl.com/y45ycru2
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__tinyurl.com_y45ycru2&d=DwMFaQ&c=OCIEmEwdEq_aNlsP4fF3gFqSN-E3mlr2t9JcDdfOZag&r=1SG5aXop0rkp_O1wnbIf7XweTLUSe9Z3aj8AqEIzm8c&m=yMDQ1-tDX9IVpw-TlXQfMkw7wtmEw1QZj7Yc7wqaSFY&s=TqBbuVwVy41lFvdGh2Z40ZbVJNd87p3TMCWnRhWKGNU&e=>
>
>
>
> reports an error on playground on the context line referring to '
> schema.org
> <https://urldefense.proofpoint.com/v2/url?u=http-3A__schema.org_&d=DwMFaQ&c=OCIEmEwdEq_aNlsP4fF3gFqSN-E3mlr2t9JcDdfOZag&r=1SG5aXop0rkp_O1wnbIf7XweTLUSe9Z3aj8AqEIzm8c&m=yMDQ1-tDX9IVpw-TlXQfMkw7wtmEw1QZj7Yc7wqaSFY&s=UVfEhs-zzTHkGkGbnB2aWuOcMO4hzSSQzDH5BxvCUEU&e=>'
> (the JSON-LD snippet comes from the draft).
>
>
>
> I *suspect* this a schema.org
> <https://urldefense.proofpoint.com/v2/url?u=http-3A__schema.org_&d=DwMFaQ&c=OCIEmEwdEq_aNlsP4fF3gFqSN-E3mlr2t9JcDdfOZag&r=1SG5aXop0rkp_O1wnbIf7XweTLUSe9Z3aj8AqEIzm8c&m=yMDQ1-tDX9IVpw-TlXQfMkw7wtmEw1QZj7Yc7wqaSFY&s=UVfEhs-zzTHkGkGbnB2aWuOcMO4hzSSQzDH5BxvCUEU&e=>
> error; if I say:
>
>
>
> curl --header "Accept: application/json" https://schema.org
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__schema.org_&d=DwMFaQ&c=OCIEmEwdEq_aNlsP4fF3gFqSN-E3mlr2t9JcDdfOZag&r=1SG5aXop0rkp_O1wnbIf7XweTLUSe9Z3aj8AqEIzm8c&m=yMDQ1-tDX9IVpw-TlXQfMkw7wtmEw1QZj7Yc7wqaSFY&s=yMtuKXAfiRO82u9D4b7MTw6t6C5fo74KHPgwx3B3zdE&e=>
>
>
>
> I would expect to receive a json-ld file, but I get an HTML instead…
>
>
>
> Am I misreading something? Maybe something went wrong when the new version
> of schema.org
> <https://urldefense.proofpoint.com/v2/url?u=http-3A__schema.org_&d=DwMFaQ&c=OCIEmEwdEq_aNlsP4fF3gFqSN-E3mlr2t9JcDdfOZag&r=1SG5aXop0rkp_O1wnbIf7XweTLUSe9Z3aj8AqEIzm8c&m=yMDQ1-tDX9IVpw-TlXQfMkw7wtmEw1QZj7Yc7wqaSFY&s=UVfEhs-zzTHkGkGbnB2aWuOcMO4hzSSQzDH5BxvCUEU&e=>
> was installed a few days ago?
>
>
>
> Ivan
>
>
> ----
> Ivan Herman, W3C
> Publishing@W3C Technical Lead
>
> Home: http://www.w3.org/People/Ivan/
> <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.w3.org_People_Ivan_&d=DwMFaQ&c=OCIEmEwdEq_aNlsP4fF3gFqSN-E3mlr2t9JcDdfOZag&r=1SG5aXop0rkp_O1wnbIf7XweTLUSe9Z3aj8AqEIzm8c&m=yMDQ1-tDX9IVpw-TlXQfMkw7wtmEw1QZj7Yc7wqaSFY&s=4L2VWxHfBXWTPv6pgX7S-ewjoiqkZupVimvxiGqDZ5Q&e=>
> mobile: +31-641044153
>
> ORCID ID: https://orcid.org/0000-0003-0782-2704
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__orcid.org_0000-2D0003-2D0782-2D2704&d=DwMFaQ&c=OCIEmEwdEq_aNlsP4fF3gFqSN-E3mlr2t9JcDdfOZag&r=1SG5aXop0rkp_O1wnbIf7XweTLUSe9Z3aj8AqEIzm8c&m=yMDQ1-tDX9IVpw-TlXQfMkw7wtmEw1QZj7Yc7wqaSFY&s=YGHcru1_EM3EQJTCNyBqpRT0qzeFRJF_hkwGof9nyho&e=>
>
>
>
>
>
>
> ----
> Ivan Herman, W3C
> Publishing@W3C Technical Lead
>
> Home: http://www.w3.org/People/Ivan/
> <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.w3.org_People_Ivan_&d=DwMFaQ&c=OCIEmEwdEq_aNlsP4fF3gFqSN-E3mlr2t9JcDdfOZag&r=1SG5aXop0rkp_O1wnbIf7XweTLUSe9Z3aj8AqEIzm8c&m=yMDQ1-tDX9IVpw-TlXQfMkw7wtmEw1QZj7Yc7wqaSFY&s=4L2VWxHfBXWTPv6pgX7S-ewjoiqkZupVimvxiGqDZ5Q&e=>
> mobile: +31-641044153
>
> ORCID ID: https://orcid.org/0000-0003-0782-2704
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__orcid.org_0000-2D0003-2D0782-2D2704&d=DwMFaQ&c=OCIEmEwdEq_aNlsP4fF3gFqSN-E3mlr2t9JcDdfOZag&r=1SG5aXop0rkp_O1wnbIf7XweTLUSe9Z3aj8AqEIzm8c&m=yMDQ1-tDX9IVpw-TlXQfMkw7wtmEw1QZj7Yc7wqaSFY&s=YGHcru1_EM3EQJTCNyBqpRT0qzeFRJF_hkwGof9nyho&e=>
>
>
>