Is it http://schema.org or https://schema.org?
Schema.org is the web’s most widely adopted vocabulary for structured data, supported by Google, Bing, and countless data platforms.
It defines types like CreativeWork, Person, and Organization, giving machines a common language to understand content.
This is exactly why the NDE application profile is built on Schema.org.
Getting it right is what makes cultural heritage data findable and reusable across institutions.
But if you’ve worked with Schema.org in RDF, you’ve run into this: there’s http://schema.org and then there’s https://schema.org.
That one-letter difference can cause real problems:
SPARQL queries that silently return nothing, SHACL validation that rejects good data or ignores bad data, or datasets that should link up but don’t – especially when combining data from multiple sources, as in NDE.
This post originally recommended http://schema.org/ (HTTP) based on reasons outlined below. It sparked exactly the discussion we hoped for: a structured conversation with stakeholders from NDE, CLARIAH, ODISSEI, and heritage institutions. On 2 April 2026, participants reached consensus on https://schema.org/ (HTTPS). This post has been updated to reflect that decision – see the recommendation.