A note on setting worker-loader’s publicPath with webpack 5

Webpack 5 introduced a mechanism to detect the publicPath that should be used automatically

[...]

Webpack 5 exposes a global variable called __webpack_public_path__ that allows you to do that.

// Updates the `publicPath` at runtime, overriding whatever was set in the
// webpack's `output` section.
__webpack_public_path__ = "/workers/";

const myWorker = new Worker(
  new URL("/workers/worker.js");
);

// Eventually, restore the `publicPath` to whatever was set in output.
__webpack_public_path__ = "https://my-static-cdn/";

{
 "@context": {
  "doap": "http://usefulinc.com/ns/doap#",
  "url": "@id",
  "name": "doap:name",
  "description": "doap:description",
  "author": "doap:maintainter",
  "license": "doap:license", // can we map values to https://spdx.org/licenses/ ?
  ...
  },
  "homepage": {"@id": "doap:homepage", "@type": "@id"}
}

Here’s an even more magical trick. Download that PDF to your file system, load it into a third tab, and annotate again. Now you’ll see all three annotations in all three tabs!

Since Hypothesis doesn’t know that the local copy of the PDF came from http://journals.plos.org/plosone/article/file?id=10.1371/journal.pone.0168597&type=printable, or that it’s related to http://journals.plos.org/plosone/article?id=10.1371/journal.pone.0168597, how is that possible?

The answer is that the PDF standard defines a unique identifier, or “fingerprint,” that authoring tools encode into the PDFs they create. When you use the Hypothesis client to annotate web-hosted PDF, it captures the fingerprint and sends it to the server.

It was already the case that you could search Hypothesis for the DOI, like so:

• https://hypothes.is/search?q=uri:doi:10.1523/JNEUROSCI.5212-13.2014 (interactive)

• https://hypothes.is/api/search?uri=doi:10.1523/JNEUROSCI.5212-13.2014 (api)

First, here’s a magic trick you might not realize Hypothesis has up its sleeve. Consider this PLOS One article. Annotate it in one tab, then open a second tab and annotate the PDF version there. You’ll see both annotations in both tabs. How is that possible?

The answer is that when scholarly publishers provide HTML versions of articles, they typically include metadata that points to PDF versions of the same articles. Here’s one way that happens:

<meta name=”citation_pdf_url” content=”http://journals.plos.org/plosone/article/file?id=10.1371/journal.pone.0168597&type=printable”>

Hypothesis remembers the correspondence between the HTML and PDF versions, and coalesces annotations across them.

GET links/resource1 HTTP/1.1
Host: example.org
Accept: application/linkset+json

HTTP/1.1 200 OK
Date: Mon, 12 Aug 2019 10:46:22 GMT
Server: Apache-Coyote/1.1
Content-Type: application/linkset+json
Link: <https://example.org/links/resource1>
      ; rel="alternate"
      ; type="application/linkset"
Content-Length: 1349

{ "linkset":
  [
    { "anchor": "https://example.org/resource1",
      "author": [
        { "href": "https://authors.example.net/johndoe",
          "type": "application/rdf+xml"
        }
      ],
      "memento": [
        { "href": "https://example.org/resource1?version=1",
          "type": "text/html",
          "datetime": "Thu, 13 Jun 2019 09:34:33 GMT"
        },
        { "href": "https://example.org/resource1?version=2",
          "type": "text/html",
          "datetime": "Sun, 21 Jul 2019 12:22:04 GMT"
        }
      ],
      "latest-version": [
        { "href": "https://example.org/resource1?version=3",
          "type": "text/html"
        }
      ]
    },
    { "anchor": "https://example.org/resource1?version=3",
      "predecessor-version": [
        { "href": "https://example.org/resource1?version=2",
          "type": "text/html"
        }
      ]
    },
    { "anchor": "https://example.org/resource1?version=2",
      "predecessor-version": [
        { "href": "https://example.org/resource1?version=1",
          "type": "text/html"
        }
      ]
    },
    { "anchor": "https://example.org/resource1#comment=1",
      "author": [
        { "href": "https://authors.example.net/alice"}
      ]
    }
  ]
}

4. Robustifying a link when linking to a specific version

If the main intent is to link to a specific state of an original resource, for example a snapshot of the original resource in a web archive or one of its version in a version control system, then Robust Link information is conveyed as follows:

• href for the URI that provides the specific state i.e., the snapshot or resource version;
• data-originalurl for the URI of the original resource;
• data-versiondate for the datetime of the snapshot or resource version.

[...]

<a href="http://en.wikipedia.org/w/index.php?title=Web_archiving&oldid=485347845"
   data-originalurl="http://en.wikipedia.org/wiki/Web_archiving"
   data-versiondate="2012-03-20">Robust Link to this specific version of the Wikipedia page</a>

3. Robustifying a link when linking to the original resource

If the main intent is to link to an original resource but also allow future users of that link to see the state of the original resource around the time the link was put in place, then Robust Link information is conveyed as follows:

• href for the URI of the original resource for which the snapshot was taken;
• data-versionurl for the URI of the snapshot;
• data-versiondate for the datetime of linking, of taking the snapshot.

[...]

<a href="http://www.w3.org/"
   data-versionurl="https://archive.today/r7cov"
   data-versiondate="2015-01-21">Robust Link to the W3C home page</a>

The approach proposed here is to convey this information on a link by leveraging HTML5's attribute extensibility mechanism. It introduces the following data- attributes for the anchor (<a>) element:

• data-originalurl for the URI of the original resource;
• data-versionurl for the URI of the snapshot;
• data-versiondate for the datetime of linking, of taking the snapshot.

String.split() can also accept a regular expression:

input.split(/[ ,]+/);

b) rgb(), rgba(), hsl() and hsla():

^(rgb|hsl)(a?)[(]\s*([\d.]+\s*%?)\s*,\s*([\d.]+\s*%?)\s*,\s*([\d.]+\s*%?)\s*(?:,\s*([\d.]+)\s*)?[)]$

<link rel="prefetch" href="/style.css" as="style" />
<link rel="preload" href="/style.css" as="style" />
<link rel="preconnect" href="https://example.com" />
<link rel="dns-prefetch" href="https://example.com" />
<link rel="prerender" href="https://example.com/about.html" />
<link rel="modulepreload" href="/script.js" />

```mermaid
graph TD;
    A-->B;
    A-->C;
    B-->D;
    C-->D;

```

Example:

{
  "@context": “http://www.w3.org/ns/anno.jsonld”
  "id": "http://data.europeana.eu/annotations/1",
  "type": "Annotation",
  "created": "2015-03-10T14:08:07Z",
  "creator": {
    "type": "Person",
    "name": "John Smith"
  },
  "generated": "2015-04-01T09:00:00Z",
  "generator": {
      "type": "Software",
      "name": "HistoryPin",
      "homepage": "https://www.historypin.org/"
  },
  "motivation": "tagging",
  "bodyValue": "MyBeautifulTag",
  "target": "http://data.europeana.eu/item/92062/BibliographicResource_1000126189360"
}

This is the profile for Mark Hughes (0000-0002-2168-0514). Up until now I've been generating my own linked data version of ORCID records that look very similar to this, but going forward this will simplify life.

Note that I've truncated the above example, it's actually this:

{
  "@context": "http://schema.org",
  "@type": "Person",
  "@id": "https://orcid.org/0000-0002-2168-0514",
  "mainEntityOfPage": "https://orcid.org/0000-0002-2168-0514",
  "givenName": "Mark",
  "familyName": "Hughes",
  "affiliation": {
    "@type": "Organization",
    "name": "Royal Botanic Garden Edinburgh",
    "identifier": {
      "@type": "PropertyValue",
      "propertyID": "RINGGOLD",
      "value": "41803"
    }
  },
  "@reverse": {
    "creator": [
      {
        "@type": "CreativeWork",
        "@id": "https://doi.org/10.1017/s0960428619000283",
        "name": "BEGONIA MAGUNIANA (BEGONIACEAE, BEGONIA SECT. OLIGANDRAE), A NEW SPECIES FROM NEW GUINEA",
        "identifier": {
          "@type": "PropertyValue",
          "propertyID": "doi",
          "value": "10.1017/s0960428619000283"
        }
      },
      {
        "@type": "CreativeWork",
        "@id": "https://doi.org/10.11646/phytotaxa.407.1.11",
        "name": "A revision of Begonia sect. Petermannia on Sumatra, Indonesia",
        "identifier": {
          "@type": "PropertyValue",
          "propertyID": "doi",
          "value": "10.11646/phytotaxa.407.1.11"
        }
      },
      {
        "@type": "CreativeWork",
        "@id": "https://doi.org/10.11646/phytotaxa.407.1.4",
        "name": "Two new species of Begonia (Begoniaceae) from Borneo",
        "identifier": {
          "@type": "PropertyValue",
          "propertyID": "doi",
          "value": "10.11646/phytotaxa.407.1.4"
        }
      },
      {
        "@type": "CreativeWork",
        "@id": "https://doi.org/10.1017/s0960428619000052",
        "name": "AN UPDATED CHECKLIST AND A NEW SPECIES OF BEGONIA (B. RHEOPHYTICA) FROM MYANMAR",
        "identifier": {
          "@type": "PropertyValue",
          "propertyID": "doi",
          "value": "10.1017/s0960428619000052"
        }
      },
      {
        "@type": "CreativeWork",
        "@id": "https://doi.org/10.1371/journal.pone.0194877",
        "name": "Chloroplast and nuclear DNA exchanges among Begonia sect. Baryandra species (Begoniaceae) from Palawan Island, Philippines, and descriptions of five new species.",
        "identifier": [
          {
            "@type": "PropertyValue",
            "propertyID": "doi",
            "value": "10.1371/journal.pone.0194877"
          },
          {
            "@type": "PropertyValue",
            "propertyID": "pmc",
            "value": "PMC5931476"
          },
          {
            "@type": "PropertyValue",
            "propertyID": "pmid",
            "value": "29718922"
          }
        ],
        "sameAs": [
          "https://europepmc.org/articles/PMC5931476",
          "https://www.ncbi.nlm.nih.gov/pubmed/29718922"
        ]
      },
      {
        "@type": "CreativeWork",
        "@id": "https://doi.org/10.1017/s0960428618000136",
        "name": "TWO NEW SPECIES OF BEGONIA FROM SUMATRA",
        "identifier": {
          "@type": "PropertyValue",
          "propertyID": "doi",
          "value": "10.1017/s0960428618000136"
        }
      },
      {
        "@type": "CreativeWork",
        "@id": "https://doi.org/10.1017/s096042861800001x",
        "name": "A REVISION OF BEGONIA SECT. SYMBEGONIA ON NEW GUINEA",
        "identifier": {
          "@type": "PropertyValue",
          "propertyID": "doi",
          "value": "10.1017/s096042861800001x"
        }
      },
      {
        "@type": "CreativeWork",
        "@id": "https://doi.org/10.5852/ejt.2018.396",
        "name": "A revision and one new species of Begonia L. (Begoniaceae, Cucurbitales) in Northeast India",
        "identifier": {
          "@type": "PropertyValue",
          "propertyID": "doi",
          "value": "10.5852/ejt.2018.396"
        }
      },
      {
        "@type": "CreativeWork",
        "@id": "https://doi.org/10.1002/tax.606013",
        "name": "Pliocene intercontinental dispersal from Africa to Southeast Asia highlighted by the new species Begonia afromigrata (Begoniaceae)",
        "identifier": {
          "@type": "PropertyValue",
          "propertyID": "doi",
          "value": "10.1002/tax.606013"
        }
      },
      {
        "@type": "CreativeWork",
        "@id": "https://doi.org/10.11646/phytotaxa.381.1.16",
        "name": "Taxonomic notes on the Philippine endemic Begonia colorata (Begoniaceae, section Petermannia)",
        "identifier": {
          "@type": "PropertyValue",
          "propertyID": "doi",
          "value": "10.11646/phytotaxa.381.1.16"
        }
      },
      {
        "@type": "CreativeWork",
        "@id": "https://doi.org/10.1186/s40529-017-0182-x",
        "name": "Three new species of Begonia sect. Baryandra from Panay Island, Philippines.",
        "identifier": [
          {
            "@type": "PropertyValue",
            "propertyID": "pmid",
            "value": "28664395"
          },
          {
            "@type": "PropertyValue",
            "propertyID": "doi",
            "value": "10.1186/s40529-017-0182-x"
          },
          {
            "@type": "PropertyValue",
            "propertyID": "pmc",
            "value": "PMC5491425"
          }
        ],
        "sameAs": [
          "https://www.ncbi.nlm.nih.gov/pubmed/28664395",
          "https://europepmc.org/articles/PMC5491425"
        ]
      },
      {
        "@type": "CreativeWork",
        "@id": "https://doi.org/10.3767/000651917x695083",
        "name": "A new species of Begonia section Parvibegonia (Begoniaceae) from Thailand and Myanmar",
        "identifier": {
          "@type": "PropertyValue",
          "propertyID": "doi",
          "value": "10.3767/000651917x695083"
        }
      },
      {
        "@type": "CreativeWork",
        "@id": "https://doi.org/10.1017/s0960428617000075",
        "name": "TAXONOMY OF BEGONIA ALBOMACULATA AND DESCRIPTION OF TWO NEW SPECIES ENDEMIC TO PERU",
        "identifier": {
          "@type": "PropertyValue",
          "propertyID": "doi",
          "value": "10.1017/s0960428617000075"
        }
      },
      {
        "@type": "CreativeWork",
        "@id": "https://doi.org/10.1017/s0960428617000051",
        "name": "FOUR NEW SPECIES OF BEGONIA (BEGONIACEAE) FROM THAILAND",
        "identifier": {
          "@type": "PropertyValue",
          "propertyID": "doi",
          "value": "10.1017/s0960428617000051"
        }
      },
      {
        "@type": "CreativeWork",
        "@id": "https://doi.org/10.3850/s2382581216000077",
        "name": "A new species and a new record in Begonia sect. Platycentrum (Begoniaceae) from Thailand",
        "identifier": {
          "@type": "PropertyValue",
          "propertyID": "doi",
          "value": "10.3850/s2382581216000077"
        }
      },
      {
        "@type": "CreativeWork",
        "@id": "https://doi.org/10.5852/ejt.2015.119",
        "name": "Begonia yapenensis (sect. Symbegonia, Begoniaceae), a new species from Papua, Indonesia",
        "identifier": {
          "@type": "PropertyValue",
          "propertyID": "doi",
          "value": "10.5852/ejt.2015.119"
        }
      },
      {
        "@type": "CreativeWork",
        "@id": "https://doi.org/10.11646/phytotaxa.197.1.4",
        "name": "A new section (Begonia sect. Oligandrae sect. nov.) and a new species (Begonia pentandra sp. nov.) in Begoniaceae from New Guinea",
        "identifier": {
          "@type": "PropertyValue",
          "propertyID": "doi",
          "value": "10.11646/phytotaxa.197.1.4"
        }
      },
      {
        "@type": "CreativeWork",
        "@id": "https://doi.org/10.5852/ejt.2015.167",
        "name": "Further discoveries in the ever-expanding genus Begonia (Begoniaceae): fifteen new species from Sumatra",
        "identifier": {
          "@type": "PropertyValue",
          "propertyID": "doi",
          "value": "10.5852/ejt.2015.167"
        }
      },
      {
        "@type": "CreativeWork",
        "@id": "https://doi.org/10.1186/s40529-015-0099-1",
        "name": "Three New Species of Begonia Endemic to the Puerto Princesa Subterranean River National Park, Palawan",
        "identifier": [
          {
            "@type": "PropertyValue",
            "propertyID": "other-id",
            "value": "al:1817406x-201507-201507290029-201507290029-c1-14"
          },
          {
            "@type": "PropertyValue",
            "propertyID": "doi",
            "value": "10.1186/s40529-015-0099-1"
          }
        ],
        "sameAs": "http://www.airitilibrary.com/Publication/alDetailedMesh?DocID=1817406X-201507-201507290029-201507290029-c1-14"
      },
      {
        "@type": "CreativeWork",
        "@id": "https://doi.org/10.5852/ejt.2013.56",
        "name": "Memecylon pseudomegacarpum M.Hughes (Melastomataceae), a new species of tree from Peninsular Malaysia",
        "identifier": {
          "@type": "PropertyValue",
          "propertyID": "doi",
          "value": "10.5852/ejt.2013.56"
        }
      },
      {
        "@type": "CreativeWork",
        "@id": "https://doi.org/10.1186/1999-3110-54-38",
        "name": "Recircumscription of Begonia sect. Baryandra (Begoniaceae): evidence from molecular data",
        "identifier": [
          {
            "@type": "PropertyValue",
            "propertyID": "other-id",
            "value": "al:1817406x-201309-201401170003-201401170003-70-74"
          },
          {
            "@type": "PropertyValue",
            "propertyID": "doi",
            "value": "10.1186/1999-3110-54-38"
          }
        ],
        "sameAs": "http://www.airitilibrary.com/Publication/alDetailedMesh?DocID=1817406X-201309-201401170003-201401170003-70-74"
      },
      {
        "@type": "CreativeWork",
        "@id": "https://doi.org/10.11646/phytotaxa.66.1.2",
        "name": "A new species and new combinations of Memecylon in Thailand and Peninsular Malaysia",
        "identifier": {
          "@type": "PropertyValue",
          "propertyID": "doi",
          "value": "10.11646/phytotaxa.66.1.2"
        }
      },
      {
        "@type": "CreativeWork",
        "@id": "https://doi.org/10.1017/s0960428612000078",
        "name": "A NEW SPECIES OF BEGONIA (BEGONIACEAE) FROM PENINSULAR THAILAND",
        "identifier": {
          "@type": "PropertyValue",
          "propertyID": "doi",
          "value": "10.1017/s0960428612000078"
        }
      },
      {
        "@type": "CreativeWork",
        "@id": "https://doi.org/10.3329/bjpt.v19i2.13134",
        "name": "Pollen morphology of Begonia L. (Begoniaceae) in Nepal",
        "identifier": {
          "@type": "PropertyValue",
          "propertyID": "doi",
          "value": "10.3329/bjpt.v19i2.13134"
        }
      },
      {
        "@type": "CreativeWork",
        "@id": "https://doi.org/10.1111/j.1365-2699.2011.02596.x",
        "name": "West to east dispersal and subsequent rapid diversification of the mega-diverse genus Begonia (Begoniaceae) in the Malesian archipelago",
        "identifier": {
          "@type": "PropertyValue",
          "propertyID": "doi",
          "value": "10.1111/j.1365-2699.2011.02596.x"
        }
      },
      {
        "@type": "CreativeWork",
        "@id": "https://doi.org/10.1017/s0960428611000072",
        "name": "NINE NEW SPECIES OF BEGONIA (BEGONIACEAE) FROM SOUTH AND WEST SULAWESI, INDONESIA",
        "identifier": {
          "@type": "PropertyValue",
          "propertyID": "doi",
          "value": "10.1017/s0960428611000072"
        }
      },
      {
        "@type": "CreativeWork",
        "name": "Begonia blancii (sect. Diploclinium, Begoniaceae), A New Species Endemic to the Philippine Island of Palawan",
        "identifier": {
          "@type": "PropertyValue",
          "propertyID": "other-id",
          "value": "al:1817406x-201104-201106150032-201106150032-203-209"
        },
        "sameAs": "http://www.airitilibrary.com/Publication/alDetailedMesh?DocID=1817406X-201104-201106150032-201106150032-203-209"
      },
      {
        "@type": "CreativeWork",
        "@id": "https://doi.org/10.1017/s0960428609005307",
        "name": "BEGONIA SECTION PETERMANNIA (BEGONIACEAE) ON PALAWAN (PHILIPPINES), INCLUDING TWO NEW SPECIES",
        "identifier": {
          "@type": "PropertyValue",
          "propertyID": "doi",
          "value": "10.1017/s0960428609005307"
        }
      },
      {
        "@type": "CreativeWork",
        "@id": "https://doi.org/10.1017/s0960428609005484",
        "name": "TWO NEW SPECIES OF BEGONIA (BEGONIACEAE) FROM SOUTH SULAWESI, INDONESIA",
        "identifier": {
          "@type": "PropertyValue",
          "propertyID": "doi",
          "value": "10.1017/s0960428609005484"
        }
      },
      {
        "@type": "CreativeWork",
        "@id": "https://doi.org/10.1017/s0960428609005320",
        "name": "TWO NEW SPECIES OF BEGONIA (BEGONIACEAE) FROM CENTRAL SULAWESI, INDONESIA",
        "identifier": {
          "@type": "PropertyValue",
          "propertyID": "doi",
          "value": "10.1017/s0960428609005320"
        }
      },
      {
        "@type": "CreativeWork",
        "@id": "https://doi.org/10.1017/s096042860800509x",
        "name": "BEGONIA VARIPELTATA(BEGONIACEAE): A NEW PELTATE SPECIES FROM SULAWESI, INDONESIA",
        "identifier": {
          "@type": "PropertyValue",
          "propertyID": "doi",
          "value": "10.1017/s096042860800509x"
        }
      },
      {
        "@type": "CreativeWork",
        "@id": "https://doi.org/10.1017/s0960428607000777",
        "name": "BEGONIA CLADOTRICHA (BEGONIACEAE): A NEW SPECIES FROM LAOS",
        "identifier": {
          "@type": "PropertyValue",
          "propertyID": "doi",
          "value": "10.1017/s0960428607000777"
        }
      },
      {
        "@type": "CreativeWork",
        "@id": "https://doi.org/10.1017/s0960428606000588",
        "name": "FOUR NEW SPECIES OF BEGONIA (BEGONIACEAE) FROM SULAWESI",
        "identifier": {
          "@type": "PropertyValue",
          "propertyID": "doi",
          "value": "10.1017/s0960428606000588"
        }
      },
      {
        "@type": "CreativeWork",
        "@id": "https://doi.org/10.1600/0363644054782297",
        "name": "A Phylogeny of Begonia Using Nuclear Ribosomal Sequence Data and Morphological Characters",
        "identifier": {
          "@type": "PropertyValue",
          "propertyID": "doi",
          "value": "10.1600/0363644054782297"
        }
      },
      {
        "@type": "CreativeWork",
        "@id": "https://doi.org/10.1016/s0006-3207(02)00375-0",
        "name": "Population genetic structure in the endemic Begonia of the Socotra archipelago",
        "identifier": {
          "@type": "PropertyValue",
          "propertyID": "doi",
          "value": "10.1016/s0006-3207(02)00375-0"
        }
      },
      {
        "@type": "CreativeWork",
        "@id": "https://doi.org/10.1017/s0960428602000082",
        "name": "A NEW ENDEMIC SPECIES OF BEGONIA (BEGONIACEAE) FROM THE SOCOTRA ARCHIPELAGO",
        "identifier": {
          "@type": "PropertyValue",
          "propertyID": "doi",
          "value": "10.1017/s0960428602000082"
        }
      },
      {
        "@type": "CreativeWork",
        "@id": "https://doi.org/10.1046/j.1471-8286.2002.00201.x",
        "name": "Isolation of polymorphic microsatellite markers for Begonia sutherlandii Hook. f.",
        "identifier": {
          "@type": "PropertyValue",
          "propertyID": "doi",
          "value": "10.1046/j.1471-8286.2002.00201.x"
        }
      },
      {
        "@type": "CreativeWork",
        "@id": "https://doi.org/10.1046/j.1471-8286.2002.00185.x",
        "name": "Polymorphic microsatellite markers for the Socotran endemic herb Begonia socotrana",
        "identifier": {
          "@type": "PropertyValue",
          "propertyID": "doi",
          "value": "10.1046/j.1471-8286.2002.00185.x"
        }
      },
      {
        "@type": "CreativeWork",
        "@id": "https://doi.org/10.3126/botor.v7i0.4386",
        "name": "Distribution Patterns of Begonia species in the Nepal Himalaya",
        "identifier": {
          "@type": "PropertyValue",
          "propertyID": "doi",
          "value": "10.3126/botor.v7i0.4386"
        }
      }
    ]
  },
  "url": [
    "https://www.rbge.org.uk/about-us/organisational-structure/staff/tropical-diversity/dr-mark-hughes/",
    "https://www.mendeley.com/profiles/mark-hughes/"
  ],
  "identifier": [
    {
      "@type": "PropertyValue",
      "propertyID": "Loop profile",
      "value": "845425"
    },
    {
      "@type": "PropertyValue",
      "propertyID": "Loop profile",
      "value": "826408"
    }
  ]
}

This gives us a list of Mark's publications from ORCID. If there aren't any publications listed, the @reverse property is empty. Note that @reverse is a JSON-LD trick that enables the JSON-LD document to include not only things linked from Mark's ORCID id (e.g., his name and affiliation) but also things his ORCID id is linked to (e.g., that he is the author of works such as https://doi.org/10.1017/s0960428619000283).

You can get linked data in JSON-LD using content negotiation. If we send a request to https://orcid.org/0000-0002-2168-0514 with "Accept: application/ld+json" we get back something like this:

{
    "@context": "http://schema.org",
    "@type": "Person",
    "@id": "https://orcid.org/0000-0002-2168-0514",
    "mainEntityOfPage": "https://orcid.org/0000-0002-2168-0514",
    "givenName": "Mark",
    "familyName": "Hughes",
    "affiliation": {
        "@type": "Organization",
        "name": "Royal Botanic Garden Edinburgh",
        "identifier": {
            "@type": "PropertyValue",
            "propertyID": "RINGGOLD",
            "value": "41803"
        }
    },
    "@reverse": {},
    "url": [
        "https://www.rbge.org.uk/about-us/organisational-structure/staff/tropical-diversity/dr-mark-hughes/",
        "https://www.mendeley.com/profiles/mark-hughes/"
    ],
    "identifier": [
        {
            "@type": "PropertyValue",
            "propertyID": "Loop profile",
            "value": "845425"
        },
        {
            "@type": "PropertyValue",
            "propertyID": "Loop profile",
            "value": "826408"
        }
    ]
}

[...] In short, pinning dependencies means the exact version specified will be installed, rather than a dependency matching the range criteria. Here's an example:

{
  "dependencies": {
    "react": "17.0.2", // installs react@17.0.2 exactly. I recommend this.
    "react": "^17.0.2", // installs the latest minor version after .0 (so 17.*.*)
    "react": "~17.0.2" // installs the latest patch after .2 (so 17.0.*)
  }
}

To automatically accomplish this in your projects, you can add save-exact=true to a .npmrc file, or use --save-exact when adding the dependency via npm (or --exact via yarn).