ORCID URIs in Linked Data response use HTTP instead of HTTPS

Metadata Retrieval
, ,
1

I hit a snag using the Linked Data DOI dereferencing service to Crossref metadata. Where available, the Crossref metadata represents ORCID URIs as HTTP uris instead of HTTPS. This breaks Linked Data browsing as retrieving the ORCID Linked Data metadata using that URI will return a graph centered around the HTTPS response.

Encoding the protocol in the identifier is a problem with Linked Data in general, but given that HTTP URIs are out of favor, it would be great if the Crossref Linked Data metadata service were to return HTTPS URIs for everything.

2

Hi @RinkeHoekstra ,

Thanks for your message. You’re absolutely right. We’re returning HTTP uris instead of HTTPS for the ORCID iDs in our APIs:

Screenshot 2024-06-26 at 2.39.22 PM
Screenshot 2024-06-26 at 2.39.22 PM1492×582 66.3 KB

I’ve opened a ticket with our product and technical teams about updating those to use HTTPS instead.

-Isaac

1 Like
3

Hi Isaac, thank you so much! Looking forward to the fix.

1 Like
4

Hello @RinkeHoekstra ,

We’ve discussed this internally and have decided against updating all ORCID iD URIs to https. This decision is in line with other decisions about altering member-registered metadata. For other URIs that we - Crossref - construct or assert on the record we have updated them to https in the past, but given that this is deposited metadata and http is not technically wrong, we will be maintaining the typical approach we take with the REST API, which is to faithfully represent deposited metadata.

My best,
Isaac

5

Hi @ifarley,

Thank you very much for following up on this. I agree with the approach that you shouldn’t be altering deposited data. I assumed you had generated the URIs from a non-URI identifier.
I will try to make sure that we deposit the correct URIs in the future.

Thanks again!

Best,
Rinke

1 Like