Closed typhoon2099 closed 4 years ago
Schema vocabulary terms using https are invalid, but if it’s something out in the wild, we should provide a solution.
*We could create a reasoner operation to generate “proper” http terms for those encountered, which you would need to run over the dataset prior to query. (Support for entailment regimes would help too)
owl:sameProperty/Class
or something similar. We’d need to com up with a naming scheme, and there would be no automatic equivalence.The reasoner approach might be the most elegant. Thoughts?
Well, perhaps a more elegant solution for me right now would be to do a big old search and replace to convert the https to http before passing into the reader. It's possibly better than my current solution of a parallel query for both schemas.
RDF::Vocab::SCHEMA
seems to be failing to pick anything up from sites like eBay due to the fact that they use https in their itemtypes. Can this be overridden/configured to work correctly? Note that the schema.org website now redirects to https by default.EDIT: The FAQ has a section on http/https (https://schema.org/docs/faq.html#19).