[
https://issues.apache.org/jira/browse/JENA-2066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17298737#comment-17298737
]
Andy Seaborne commented on JENA-2066:
-------------------------------------
For information:
While the long-term plan is for schema.org to be https, the switch to returning
the https version when requesting over http was not intended by schema.org just
at the moment. This has been reverted. It will happen, with suitable warning
and migration, sometime.
For the long-term, it is better to use the preferred \{{https://schema.org/}}.
> Build breaks because schema.org has changed.
> --------------------------------------------
>
> Key: JENA-2066
> URL: https://issues.apache.org/jira/browse/JENA-2066
> Project: Apache Jena
> Issue Type: Improvement
> Reporter: Andy Seaborne
> Assignee: Andy Seaborne
> Priority: Major
> Fix For: Jena 4.0.0
>
>
> Today (20210-03-08) the build started breaking in
> {{TestJsonLDReader.simpleReadTest}}.
> It worked until about 16:00 UTC. Then it didn't.
> Schema.org 12.0 was released today.
> The test uses
> {noformat}
> "@context": "http://schema.org/"
> {noformat}
> and now (via "301 Moved Permanently" and a Link header):
> {noformat}
> wget --header 'Accept: application/ld+json'
> http://schema.org/docs/jsonldcontext.jsonld
> {noformat}
> returns a doc with {{"@vocab": "https://schema.org/"}}.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)