LISTSERV mailing list manager LISTSERV 16.0

Help for ID Archives


ID Archives

ID Archives


ID@C4VLPLISTSERV01.LOC.GOV


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

ID Home

ID Home

ID  June 2020

ID June 2020

Subject:

Re: ID switching to HTTPS

From:

Antoine Isaac <[log in to unmask]>

Reply-To:

LC Linked Data Service Discussion List <[log in to unmask]>

Date:

Wed, 17 Jun 2020 10:54:41 +0200

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (54 lines)

Hello Kevin,

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,

Antoine
---
Antoine Isaac
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. Itll 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 were not clear about is how disruptive this will be for those of you who make regular use of the bulk downloads.  Wed 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
> 
> --
> 
> Kevin Ford
> 
> Library of Congress
> 
> Washington, DC
> 

Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Search Archives

Search Archives


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

July 2020
June 2020
March 2020
February 2020
November 2019
October 2019
September 2019
August 2019
July 2019
June 2019
April 2019
February 2019
January 2019
December 2018
November 2018
October 2018
September 2017
July 2016
February 2016
January 2016
December 2015
November 2015
September 2015
August 2015
June 2015
March 2015
February 2015
October 2014
August 2014
July 2014
June 2014
March 2014
January 2014
November 2013
September 2013
August 2013
June 2013
May 2013
April 2013
March 2013
December 2012
November 2012
October 2012
September 2012
August 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
April 2011
March 2011
February 2011
January 2011
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
November 2009
June 2009
May 2009

ATOM RSS1 RSS2



LISTSERV.LOC.GOV

CataList Email List Search Powered by the LISTSERV Email List Manager