I'm reporting an issue with the CSL JSON returned by DOI Content Negotiation for Crossref DOIs. This issue was originally reported by a Manubot user at manubot/manubot#158.

The following command requests CSL JSON metadata for https://doi.org/10.1038/ng.3834:

curl --silent --location \
  --header "Accept: application/vnd.citationstyles.csl+json" \
  https://doi.org/10.1038/ng.3834 \
  | python -m json.tool

One weird thing, but not the issue that I'm reporting, is that on the Nature website "GTEx Consortium" is listed as the 10th author, but is second in the Crossref metadata. Assuming this is a publisher error, but wanted to point it out to avoid confusion.

In the JSON returned by the DOI Content Negotiation command, you'll find the following:

    "author": [
        {
            "given": "Colby",
            "family": "Chiang",
            "sequence": "first",
            "affiliation": []
        },
        {
            "name": "GTEx Consortium",
            "sequence": "first",
            "affiliation": []
        },

The mistake is that "name": "GTEx Consortium", should be "literal": "GTEx Consortium",, since literal is the field according to the CSL JSON specification.

Also note that sequence and affiliation are not part of the CSL specification. Crossref DOIs return a large number of fields that are not part of CSL JSON. This is a longstanding but separate issue.

So where is the source code where name need to be replaced with literal? Is this the right repo for reporting issues with CSL JSON returned by DOI Content Negotiation for Crossref DOIs?