csv2rdf4lod-automation is licensed under the [Apache License, Version 2.0](https://github.com/timrdf/csv2rdf4lod-automation/wiki/License)

https://inkdroid.org/journal/2011/04/25/dois-as-linked-data/

FYI, the whole "DOIs as linked data" discussion was in kicked off (in part) Feb 2010 by a pair of blog postings me [1, 2], which got people from doi.org, CrossRef and CNRI (and elsewhere) engaged, which led to implementation by CrossRef with the help of CNRI.

[1] "The DOI, DataCite and Linked Data: Made for each other!" https://bit.ly/aHCRWc [2] "DOIs, URIs and Cool Resolution" https://bit.ly/a7S5qD

https://www.crossref.org/CrossTech/2011/04/content_negotiation_for_crossr.html

Geoff is ORCID's interim technical director (https://www.orcid.org/board-of-directors) and is involved in the VIVO-ORCID work on a coordination / managing sort of level. The DOI / Linked Data service which he's been in charge of setting up at CrossRef is entirely separate from the ORCID activities.

The LD service is quite new and documentation is probably scant at this point. Geoff et al are quiet keen to get feedback from the SemWeb community on the use of vocabularies and other aspects of the service.

curl --location --header "Accept: text/turtle" https://dx.doi.org/10.2204/iodp.sd.2.01.2006

doi:10.1000/182 into https://dx.doi.org/10.1000/182 (per firefox issue)

Real example: DOI 10.1109/TVCG.2011.255 on ieeexplore.ieee.org, stitch together: curl --location --header "Accept: text/turtle" https://dx.doi.org/10.1109/TVCG.2011.255

https://www.doi2bib.org/

https://www.crosscite.org/cn/