Schema.org http/https alignment

rubensworks commented 2 years ago

Pitch

As shown in https://github.com/w3c/sparql-12/issues/156, some websites use the HTTP versions of the Schema.org ontology, while others use the HTTPS version. Semantically, they indicate the same thing, but since they use a different scheme, they are strictly different in RDF.

Desired solution

Query engines should have a way to automatically align the HTTP/HTTPS variants of the Schema.org ontology, so that users can query over datasets that uses a mix of them, and issue queries that uses a mix of them.

Acceptance criteria

An query-driven application that displays profiles of different people.
These profiles should be build using a mix of HTTP/HTTPS of the Schema.org ontology.
The queries should work in both HTTP and HTTPS of the Schema.org ontology.

Optional:

We may want to enable users to choose for themselves which inferences are applied when they are querying. For this, we should make it possible for users to include links to N3 documents that contain rules that must be applied when reasoning. When the user uses a query engine, the query engine should detect these N3 documents from the user's profile, and apply them at query time.