How to handle HTTPS for schema.org? · Issue #118 · RDFLib/pySHACL (original) (raw)

Skip to content

Navigation Menu

• • GitHub Copilot Write better code with AI
  • GitHub Advanced Security Find and fix vulnerabilities
  • Actions Automate any workflow
  • Codespaces Instant dev environments
  • Issues Plan and track work
  • Code Review Manage code changes
  • Discussions Collaborate outside of code
  • Code Search Find more, search less
• Explore
  • Learning Pathways
  • Events & Webinars
  • Ebooks & Whitepapers
  • Customer Stories
  • Partners
  • Executive Insights
• • GitHub Sponsors Fund open source developers
  • The ReadME Project GitHub community articles
• • Enterprise platform AI-powered developer platform
• Pricing

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Sign up

Description

Hi there

Using pyshacl for my schema.org resources, I recently encountered a change in the reported errors. Instead of schema I now see schema1 as a prefix. Because I experienced the same behaviour when building the docs from my SHACL shapes using https://github.com/lambdamusic/Ontospy I thought this could be related to https://github.com/RDFLib. This turned out to be the reason since they recently switched from http://schema.org/ to https://schema.org/ (TLS). schema now seems to refer to https://schema.org/ and schema1 to the non TLS version of it.

I am aware that this is not a pyshacl issue. However, I wonder whether http://schema.org/Thing is different from https://schema.org/Thing. In a technical sense it's clearly two different things but I think everyone would agree that they refer to the same concept, as stated here.

Are there any best practices to handle this? Should one switch to HTTPs for schema.org asap?