Thanks for the heads-up!
I think I will ask for a double-check: the vocabulary URIs like LCSH will now de-refer to data where the statements will use HTTPs URIs?
Using a toy example...
If Europeana receives statements like
ex:book dcterms:subject <http://id.loc.gov/x>
Then when getting the data for <http://id.loc.gov/x> we will get these statements:
<https://id.loc.gov/x> skos:prefLabel "label" .
<https://id.loc.gov/x> owl:sameAs <http://id.loc.gov/x> .
Is that correct?
If yes, it means that data users will have to rely on owl:sameAs machinery or re-write all URIs, otherwise their data will be 'broken' (i.e. they wouldn't directly get statements about the URIs that they look up).
For the record at rightsstatements.org we have considered the issue and opted to still use HTTP URIs as "canonical" identifiers in the data we serve (though there's HTTPs in the service that provides the data and web pages). And we hope that other actors like Creative Commons will *not* make the move of using HTTPs URIs as "canonical" identifiers, because that would force us to make too many changes (also in non-RDF aware part of the software, and documentation!)
All the best,
R&D Manager, Europeana
On 16/06/2020 23:46, Ford, Kevin wrote:
> Most faithful users of ID.LOC.GOV:
> In the next 3-4 weeks, ID will be switching to HTTPS. Until now, ID has operated via HTTP, though for several years now HTTPS has been an option for anyone who wanted to use HTTPS instead.
> A 301 (Permanent Redirect) will be implemented to direct HTTP requests to their HTTPS equivalents. There is no end date at this time for the 301 redirect, but we encourage everyone to start using the HTTPS URIs once the switchover happens. It’ll decrease latency (fewer HTTP calls/redirects) and, of course, ensure your communication with the service is encrypted from the outset.
> Except for the classes and properties of ontologies/vocabularies hosted at ID – Bibframe, MADS/RDF, and PREMIS – the HTTPS URI will become /the/ URI for resources. We will add owl:sameAs properties to those resources to capture the fact that the HTTPS URI is the same as the HTTP URI. To be clear: the URIs for classes and properties of ontologies/vocabularies hosted at ID will still be referenced as HTTP URIs even if the client is redirected to an HTTPS address.
> The URIs in the bulk downloads are one of the trickier aspects of this change. Our thinking presently is to re-issue all the bulk downloads as soon as we can wherein the HTTPS URI is /the/ identifier for resources. What we’re not clear about is how disruptive this will be for those of you who make regular use of the bulk downloads. We’d welcome your feedback either way as this will help us determine if re-issuing the bulk downloads with the new URIs is acceptable or whether we need to explore additional options.
> Do let us know.
> All the best,
> Kevin Ford
> Library of Congress
> Washington, DC