Re: [jats-list] Why is archiving JATS with a DOI not common?

["Castedo Ellerman castedo@xxxxxxxxxxx" <jats-list-service@xxxxxxxxxxxxxxxxxxxxxx>]

On 4/29/22 16:24, Alf Eaton wrote:
> Fetching the metadata for that DOI, via the DOI registrar Crossref, 
> finds a bunch of useful URLs in the response Link header (and in the 
> JSON, if you remove the -I flag from the request):
>
> curl -L -I -H 'Accept: application/json' 
> https://doi.org/10.1098/rsif.2017.0387
>
> <http://dx.doi.org/10.1098/rsif.2017.0387>; rel="canonical", 
> <https://royalsocietypublishing.org/doi/pdf/10.1098/rsif.2017.0387>; 
> version="vor"; type="application/pdf"; rel="item",
> <https://royalsocietypublishing.org/doi/full-xml/10.1098/rsif.2017.0387>; 
> version="vor"; type="application/xml"; rel="item", 
> <https://royalsocietypublishing.org/doi/pdf/10.1098/rsif.2017.0387>; 
> version="vor"; rel="item",
> <https://royalsociety.org/journals/ethics-policies/data-sharing-mining/>; 
> version="tdm"; rel="license"
>
> One of those is, indeed, the full text "version of record" JATS XML:
>
> https://royalsocietypublishing.org/doi/full-xml/10.1098/rsif.2017.0387

Thank you Alf! That really answers so many of my questions!

So indeed the Royal Society does resolve the DOI to JATS XML with the 
right API request via Crossref.

I will read more about this API from Crossref. What a great non-profit!

Cheers,
 B B  Castedo