Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Update SDO DefinedNamespace to HTTPS and latests schema.org
- Loading branch information
1 parent
a24d534
commit 910e831
910e831There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The change of the schema.org prefix from
http://schema.orgtohttps://schema.org/obviously introduces some backwards compatibility issues.The schema.org people seem to waffle somewhat on this; see schemaorg/schemaorg#2886. It would seem preferable that the namespace remain constant.
910e831There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think the issue here is that schema.org has dual use of its namespace: as an RDF namespace and also as a website address. This isn't true of all other RDF namespaces, even when they resolve as they often redirect to things whereas schema.org just resolves directly. The website nature of their namespace essentially forces it to be HTTPS given that's most visitors/browsers expectations these days.
So we are going to be 'constant' by sticking with HTTPS! We changed to HTTPS last year some time and it was a mistake when it was reverted to HTTP. We've corrected back to HTTPS now and that's what we'll maintain. I'll mention this over on schema.org too.
910e831There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@nicholascar thanks for the additional info, I appreciate it.
910e831There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@nicholascar I really wish this was noted in the changelog! I've wasted several days trying to figure out why queries were mysteriously failing on some data. The switch from
http://schema.org/tohttps://schema.org/turned out to be the cause.