As a graph

graph LR
  Bf89e54622707("Context updates require reissuing documents")
  https___vocab_methodandstructure_com_ibis_Argument("Argument")
  click https___vocab_methodandstructure_com_ibis_Argument "https://vocab.methodandstructure.com/ibis#Argument"
  Bdb67a4225c37("Aggressively cache contexts")
  B96de9af5e5f1("Cached entries may expire or differ by deployment")
  Bb357c0431c4b("Repeat processing can survive temporary outages")
  B9ed80b1e656d("Vetted copies need an update process")
  B40121b421666("Shared vocabularies are cross-origin by design")
  Ba9eb731a9e30("The origin model is widely implemented")
  B1a8ef6296b42("JSON-LD @sri")
  B383231988dd4("Hash travels with the context reference")
  B1469a9e8f1bb("Content-addressed context URIs")
  B20007dcd409e("Content-addressed context schemes have weak adoption")
  B4fd68375a00e("Use a vetted context allowlist")
  B13e130a2e5fc("Fits controlled processing environments")
  Literal-3372d781aa1f[["The integrity hash is carried by the reference itself, with no separate lockfile."]]
  B0685f72fa6fc("Shared contexts are repeated in every document")
  Literal-7b9524c5e3d6[["Real JSON-LD documents commonly rely on shared cross-origin vocabularies such as schema.org and w3id.org."]]
  Literal-05af7767aa1f[["Same-origin policy is already implemented by browsers."]]
  Literal-5be342a13b79[["Updating an inline context requires reissuing every document that embeds it."]]
  B0a87a718bdec("Fits Linked Data trust literature")
  Bc97ecab0f65d("Imported contexts are not covered")
  Baab43a5bccd1("Hash fragment in application/ld+json")
  B80eae73a5d4b("The referencing document does not bind the hash")
  Bf0c7423c62bc("Reduces repeated fetches")
  B99073f8d9343("No external allowlist is needed")
  B06013c31b5c2("How should JSON-LD documents avoid remote context risks?")
  Bc2a89a0c737d("Inline contexts")
  B9d94180f3b3a("Context servers must cooperate")
  Bf4ba3ff94fd8("Structured context references are heavier")
  Literal-ca2071652e15[["Remote JSON-LD contexts make document meaning depend on mutable network resources, which creates risks around changed, spoofed, unavailable, privacy-leaking, or overloaded context servers."]]
  Literal-533bf2a00042[["The hash is supplied by the response server, not by the document that references the context."]]
  https___vocab_methodandstructure_com_ibis_Position("Position")
  click https___vocab_methodandstructure_com_ibis_Position "https://vocab.methodandstructure.com/ibis#Position"
  Literal-ce0d1238a65a[["Origin policy can be described without a separate deployment-specific allowlist."]]
  Literal-3143840d7b9c[["The proposal does not yet cover @import chains."]]
  B4a2f871f02f7("Origin-based policy")
  B8c909c337620("Origin checks do not validate context content")
  Bef30dbfcc950("Already available in JSON-LD 1.1")
  Literal-b5e33717debf[["Protected terms require no new JSON-LD syntax or future revision."]]
  B6e13a6911ba1("JSON-LD @protected")
  B01b74e8b2b40("Direct analogy to browser SRI")
  Literal-04bfa4db6676[["The model is familiar because it mirrors a proven browser standard."]]
  Literal-e73d1ece70a7[["Cache entries can expire, be evicted, or vary between processors."]]
  Literal-080d92843927[["Caching reduces repeated requests against shared public context servers."]]
  https___vocab_methodandstructure_com_ibis_Issue("Issue")
  click https___vocab_methodandstructure_com_ibis_Issue "https://vocab.methodandstructure.com/ibis#Issue"
  B0c0e7e06fea2("Does not authenticate fetched bytes")
  Ba107a6b9cb7e("Existing context URLs must be replaced or aliased")
  Literal-6557de704284[["Location-based context URLs such as schema.org and w3id.org would need a migration path."]]
  B5f0353317545("No author syntax change is required")
  Literal-3781c3ef0e98[["Hash fragments in HTTP responses are transparent to document authors."]]
  Bbdb7d70b077c("Correct processing does not depend on loader policy")
  Literal-80f95a5bc3f9[["Content-addressed context URIs align with approaches such as Trusty URIs and nanopublications."]]
  B7f560c7f7519("The first fetch is still trusted")
  Literal-4f2842ae8586[["Organizations must update and re-vet cached context copies."]]
  Literal-5f061e5905ee[["A vetted allowlist works well for archival, reproducible, air-gapped, and privacy-sensitive processing."]]
  Literal-3734fc262561[["Protected terms prevent some redefinitions but do not authenticate the remote context or pin its content."]]
  Literal-59f1d4b7b507[["Existing context servers would need to emit the relevant hash information."]]
  Literal-c9504c3f0069[["A plain context URL becomes an object with metadata, making simple @context usage less readable."]]
  Literal-124d00f9b9b4[["Inline contexts avoid depending on cache or document-loader configuration."]]
  B641f043d8de7("Unknown context URLs are refused")
  Bc780551a69d3("The document carries its own term definitions")
  Literal-203ce8a7fdc7[["Origin policy restricts who can serve a context, not what bytes the context contains or whether it remains available."]]
  Bcf3631293047("The URI itself checks integrity")
  Literal-77a04c8cbb4f[["Mutation produces a different content-addressed URI by construction."]]
  B26a7c81b7170("Meaningful protection requires inline setup")
  Literal-6d8ea9bbe404[["Key terms must be declared inline before loading later contexts, reducing the value of loading them remotely."]]
  Literal-a3d9acc223f3[["Large shared contexts such as schema.org become verbose when embedded repeatedly."]]
  Literal-b31eaf149dee[["Caching does not authenticate the first response or make spoofed bytes trustworthy."]]
  B12a470ae96f5("Trust policy does not travel with the document")
  Literal-e66f98cdcb65[["Another deployment may resolve the same context URLs differently."]]
  Literal-489c7cc3ef52[["The ni scheme has no mainstream adoption, and IPFS adds infrastructure dependency."]]
  Literal-c6024b6ce405[["A vetted allowlist can refuse unknown context URLs instead of fetching them."]]
  Literal-6ee14fa825c0[["Inline contexts make the document fully carry the term definitions it depends on."]]
  Literal-9a1a7a1280c5[["A warm cache can tolerate temporary server or network failures."]]
  Bf89e54622707 --- 196d43cbdf11(["type"])--> https___vocab_methodandstructure_com_ibis_Argument
  click 196d43cbdf11 "http://www.w3.org/1999/02/22-rdf-syntax-ns#type"
  Bdb67a4225c37 --- e84baee6286c(["opposed by"])--> B96de9af5e5f1
  click e84baee6286c "https://vocab.methodandstructure.com/ibis#opposed-by"
  Bb357c0431c4b --- 55795af7d924(["type"])--> https___vocab_methodandstructure_com_ibis_Argument
  click 55795af7d924 "http://www.w3.org/1999/02/22-rdf-syntax-ns#type"
  B9ed80b1e656d --- e13d2533100c(["type"])--> https___vocab_methodandstructure_com_ibis_Argument
  click e13d2533100c "http://www.w3.org/1999/02/22-rdf-syntax-ns#type"
  B40121b421666 --- f857ebc6e504(["type"])--> https___vocab_methodandstructure_com_ibis_Argument
  click f857ebc6e504 "http://www.w3.org/1999/02/22-rdf-syntax-ns#type"
  Ba9eb731a9e30 --- 83c24ca887aa(["type"])--> https___vocab_methodandstructure_com_ibis_Argument
  click 83c24ca887aa "http://www.w3.org/1999/02/22-rdf-syntax-ns#type"
  B1a8ef6296b42 --- 49e96341cb63(["supported by"])--> B383231988dd4
  click 49e96341cb63 "https://vocab.methodandstructure.com/ibis#supported-by"
  B1469a9e8f1bb --- d361934ba253(["opposed by"])--> B20007dcd409e
  click d361934ba253 "https://vocab.methodandstructure.com/ibis#opposed-by"
  B4fd68375a00e --- ee0fd7b9aa5f(["supported by"])--> B13e130a2e5fc
  click ee0fd7b9aa5f "https://vocab.methodandstructure.com/ibis#supported-by"
  B383231988dd4 --- cad56228a64c(["comment"])--> Literal-3372d781aa1f
  click cad56228a64c "http://www.w3.org/2000/01/rdf-schema#comment"
  B0685f72fa6fc --- c5b2b643ee48(["type"])--> https___vocab_methodandstructure_com_ibis_Argument
  click c5b2b643ee48 "http://www.w3.org/1999/02/22-rdf-syntax-ns#type"
  B4fd68375a00e --- 09f4a8451739(["opposed by"])--> B9ed80b1e656d
  click 09f4a8451739 "https://vocab.methodandstructure.com/ibis#opposed-by"
  B96de9af5e5f1 --- e120522b7054(["type"])--> https___vocab_methodandstructure_com_ibis_Argument
  click e120522b7054 "http://www.w3.org/1999/02/22-rdf-syntax-ns#type"
  B40121b421666 --- 210abd129985(["comment"])--> Literal-7b9524c5e3d6
  click 210abd129985 "http://www.w3.org/2000/01/rdf-schema#comment"
  Ba9eb731a9e30 --- e0bb3dc849ed(["comment"])--> Literal-05af7767aa1f
  click e0bb3dc849ed "http://www.w3.org/2000/01/rdf-schema#comment"
  Bf89e54622707 --- 00aa94c1f449(["comment"])--> Literal-5be342a13b79
  click 00aa94c1f449 "http://www.w3.org/2000/01/rdf-schema#comment"
  B1469a9e8f1bb --- 5074d83f2973(["supported by"])--> B0a87a718bdec
  click 5074d83f2973 "https://vocab.methodandstructure.com/ibis#supported-by"
  Bc97ecab0f65d --- 0f763fd8cded(["type"])--> https___vocab_methodandstructure_com_ibis_Argument
  click 0f763fd8cded "http://www.w3.org/1999/02/22-rdf-syntax-ns#type"
  Baab43a5bccd1 --- e1baa1baad17(["opposed by"])--> B80eae73a5d4b
  click e1baa1baad17 "https://vocab.methodandstructure.com/ibis#opposed-by"
  Bf0c7423c62bc --- 822dabe6be8f(["type"])--> https___vocab_methodandstructure_com_ibis_Argument
  click 822dabe6be8f "http://www.w3.org/1999/02/22-rdf-syntax-ns#type"
  B99073f8d9343 --- 95d1d031894e(["type"])--> https___vocab_methodandstructure_com_ibis_Argument
  click 95d1d031894e "http://www.w3.org/1999/02/22-rdf-syntax-ns#type"
  B06013c31b5c2 --- 49bfb3cf0009(["response"])--> Bc2a89a0c737d
  click 49bfb3cf0009 "https://vocab.methodandstructure.com/ibis#response"
  B06013c31b5c2 --- 044ec00c58b6(["response"])--> B1a8ef6296b42
  click 044ec00c58b6 "https://vocab.methodandstructure.com/ibis#response"
  Baab43a5bccd1 --- 756f74004ad9(["opposed by"])--> B9d94180f3b3a
  click 756f74004ad9 "https://vocab.methodandstructure.com/ibis#opposed-by"
  Bf4ba3ff94fd8 --- 7fd88708111f(["type"])--> https___vocab_methodandstructure_com_ibis_Argument
  click 7fd88708111f "http://www.w3.org/1999/02/22-rdf-syntax-ns#type"
  B06013c31b5c2 --- 1453f187b416(["comment"])--> Literal-ca2071652e15
  click 1453f187b416 "http://www.w3.org/2000/01/rdf-schema#comment"
  B80eae73a5d4b --- 8abdf00cb2e6(["comment"])--> Literal-533bf2a00042
  click 8abdf00cb2e6 "http://www.w3.org/2000/01/rdf-schema#comment"
  B1469a9e8f1bb --- 33230ee86919(["type"])--> https___vocab_methodandstructure_com_ibis_Position
  click 33230ee86919 "http://www.w3.org/1999/02/22-rdf-syntax-ns#type"
  B99073f8d9343 --- cd7adf56a157(["comment"])--> Literal-ce0d1238a65a
  click cd7adf56a157 "http://www.w3.org/2000/01/rdf-schema#comment"
  Bc97ecab0f65d --- 0b29cecdbdd0(["comment"])--> Literal-3143840d7b9c
  click 0b29cecdbdd0 "http://www.w3.org/2000/01/rdf-schema#comment"
  B4a2f871f02f7 --- 5de946e63e95(["opposed by"])--> B8c909c337620
  click 5de946e63e95 "https://vocab.methodandstructure.com/ibis#opposed-by"
  B06013c31b5c2 --- db2a30ffdc4f(["response"])--> Bdb67a4225c37
  click db2a30ffdc4f "https://vocab.methodandstructure.com/ibis#response"
  B06013c31b5c2 --- cac0e668291f(["response"])--> Baab43a5bccd1
  click cac0e668291f "https://vocab.methodandstructure.com/ibis#response"
  Bef30dbfcc950 --- b1fdc897157e(["comment"])--> Literal-b5e33717debf
  click b1fdc897157e "http://www.w3.org/2000/01/rdf-schema#comment"
  B06013c31b5c2 --- c97ef3640134(["response"])--> B6e13a6911ba1
  click c97ef3640134 "https://vocab.methodandstructure.com/ibis#response"
  B06013c31b5c2 --- 38f7f74acfc0(["response"])--> B1469a9e8f1bb
  click 38f7f74acfc0 "https://vocab.methodandstructure.com/ibis#response"
  B01b74e8b2b40 --- 177beaf72504(["comment"])--> Literal-04bfa4db6676
  click 177beaf72504 "http://www.w3.org/2000/01/rdf-schema#comment"
  B96de9af5e5f1 --- f11d571a490d(["comment"])--> Literal-e73d1ece70a7
  click f11d571a490d "http://www.w3.org/2000/01/rdf-schema#comment"
  B0a87a718bdec --- 47aeff0af1ce(["type"])--> https___vocab_methodandstructure_com_ibis_Argument
  click 47aeff0af1ce "http://www.w3.org/1999/02/22-rdf-syntax-ns#type"
  Bf0c7423c62bc --- a6d0fb7719df(["comment"])--> Literal-080d92843927
  click a6d0fb7719df "http://www.w3.org/2000/01/rdf-schema#comment"
  B06013c31b5c2 --- 3d669a27762f(["type"])--> https___vocab_methodandstructure_com_ibis_Issue
  click 3d669a27762f "http://www.w3.org/1999/02/22-rdf-syntax-ns#type"
  Bc2a89a0c737d --- e5729fc96757(["opposed by"])--> B0685f72fa6fc
  click e5729fc96757 "https://vocab.methodandstructure.com/ibis#opposed-by"
  B0c0e7e06fea2 --- d4694e4cc39c(["type"])--> https___vocab_methodandstructure_com_ibis_Argument
  click d4694e4cc39c "http://www.w3.org/1999/02/22-rdf-syntax-ns#type"
  Ba107a6b9cb7e --- 9f07cb7cb3b9(["comment"])--> Literal-6557de704284
  click 9f07cb7cb3b9 "http://www.w3.org/2000/01/rdf-schema#comment"
  Baab43a5bccd1 --- 6ae8cc7e55a2(["supported by"])--> B5f0353317545
  click 6ae8cc7e55a2 "https://vocab.methodandstructure.com/ibis#supported-by"
  B5f0353317545 --- 3f6c52b352c7(["comment"])--> Literal-3781c3ef0e98
  click 3f6c52b352c7 "http://www.w3.org/2000/01/rdf-schema#comment"
  Bc2a89a0c737d --- 955aee5db295(["supported by"])--> Bbdb7d70b077c
  click 955aee5db295 "https://vocab.methodandstructure.com/ibis#supported-by"
  B0a87a718bdec --- 8603a835a89e(["comment"])--> Literal-80f95a5bc3f9
  click 8603a835a89e "http://www.w3.org/2000/01/rdf-schema#comment"
  B6e13a6911ba1 --- db6e96c0804c(["opposed by"])--> B0c0e7e06fea2
  click db6e96c0804c "https://vocab.methodandstructure.com/ibis#opposed-by"
  B7f560c7f7519 --- cb975e07235a(["type"])--> https___vocab_methodandstructure_com_ibis_Argument
  click cb975e07235a "http://www.w3.org/1999/02/22-rdf-syntax-ns#type"
  B9ed80b1e656d --- 435c30ad4c73(["comment"])--> Literal-4f2842ae8586
  click 435c30ad4c73 "http://www.w3.org/2000/01/rdf-schema#comment"
  B13e130a2e5fc --- c1435028f525(["comment"])--> Literal-5f061e5905ee
  click c1435028f525 "http://www.w3.org/2000/01/rdf-schema#comment"
  B01b74e8b2b40 --- 8ea7e6b500db(["type"])--> https___vocab_methodandstructure_com_ibis_Argument
  click 8ea7e6b500db "http://www.w3.org/1999/02/22-rdf-syntax-ns#type"
  B0c0e7e06fea2 --- 475b21f084ee(["comment"])--> Literal-3734fc262561
  click 475b21f084ee "http://www.w3.org/2000/01/rdf-schema#comment"
  B9d94180f3b3a --- a498c16bf46f(["comment"])--> Literal-59f1d4b7b507
  click a498c16bf46f "http://www.w3.org/2000/01/rdf-schema#comment"
  Bc2a89a0c737d --- ae4b72a65800(["opposed by"])--> Bf89e54622707
  click ae4b72a65800 "https://vocab.methodandstructure.com/ibis#opposed-by"
  Bf4ba3ff94fd8 --- 79f6252823d2(["comment"])--> Literal-c9504c3f0069
  click 79f6252823d2 "http://www.w3.org/2000/01/rdf-schema#comment"
  Bbdb7d70b077c --- 0846499ef8d9(["comment"])--> Literal-124d00f9b9b4
  click 0846499ef8d9 "http://www.w3.org/2000/01/rdf-schema#comment"
  B4fd68375a00e --- 9398de53fd99(["supported by"])--> B641f043d8de7
  click 9398de53fd99 "https://vocab.methodandstructure.com/ibis#supported-by"
  B1a8ef6296b42 --- 6375f82db69d(["type"])--> https___vocab_methodandstructure_com_ibis_Position
  click 6375f82db69d "http://www.w3.org/1999/02/22-rdf-syntax-ns#type"
  Bdb67a4225c37 --- 986bf5762684(["opposed by"])--> B7f560c7f7519
  click 986bf5762684 "https://vocab.methodandstructure.com/ibis#opposed-by"
  Bc2a89a0c737d --- 537c63798d41(["supported by"])--> Bc780551a69d3
  click 537c63798d41 "https://vocab.methodandstructure.com/ibis#supported-by"
  B5f0353317545 --- dc6b6f957910(["type"])--> https___vocab_methodandstructure_com_ibis_Argument
  click dc6b6f957910 "http://www.w3.org/1999/02/22-rdf-syntax-ns#type"
  B8c909c337620 --- 8ab9e3c9dc1a(["comment"])--> Literal-203ce8a7fdc7
  click 8ab9e3c9dc1a "http://www.w3.org/2000/01/rdf-schema#comment"
  Bcf3631293047 --- 180821d808a8(["comment"])--> Literal-77a04c8cbb4f
  click 180821d808a8 "http://www.w3.org/2000/01/rdf-schema#comment"
  B26a7c81b7170 --- 0223c4b18ac3(["comment"])--> Literal-6d8ea9bbe404
  click 0223c4b18ac3 "http://www.w3.org/2000/01/rdf-schema#comment"
  B4fd68375a00e --- 229ea1b163a4(["type"])--> https___vocab_methodandstructure_com_ibis_Position
  click 229ea1b163a4 "http://www.w3.org/1999/02/22-rdf-syntax-ns#type"
  B0685f72fa6fc --- a428808a67b5(["comment"])--> Literal-a3d9acc223f3
  click a428808a67b5 "http://www.w3.org/2000/01/rdf-schema#comment"
  B7f560c7f7519 --- 7be2efb4ff07(["comment"])--> Literal-b31eaf149dee
  click 7be2efb4ff07 "http://www.w3.org/2000/01/rdf-schema#comment"
  Baab43a5bccd1 --- 9ad5e3f78828(["type"])--> https___vocab_methodandstructure_com_ibis_Position
  click 9ad5e3f78828 "http://www.w3.org/1999/02/22-rdf-syntax-ns#type"
  B4fd68375a00e --- 96d654b739be(["opposed by"])--> B12a470ae96f5
  click 96d654b739be "https://vocab.methodandstructure.com/ibis#opposed-by"
  B9d94180f3b3a --- 161c059ea25a(["type"])--> https___vocab_methodandstructure_com_ibis_Argument
  click 161c059ea25a "http://www.w3.org/1999/02/22-rdf-syntax-ns#type"
  B6e13a6911ba1 --- c7a270435d6b(["type"])--> https___vocab_methodandstructure_com_ibis_Position
  click c7a270435d6b "http://www.w3.org/1999/02/22-rdf-syntax-ns#type"
  B12a470ae96f5 --- 80f58e9056fc(["comment"])--> Literal-e66f98cdcb65
  click 80f58e9056fc "http://www.w3.org/2000/01/rdf-schema#comment"
  Bbdb7d70b077c --- 3f0e849beff8(["type"])--> https___vocab_methodandstructure_com_ibis_Argument
  click 3f0e849beff8 "http://www.w3.org/1999/02/22-rdf-syntax-ns#type"
  B1469a9e8f1bb --- a49aff00e74c(["supported by"])--> Bcf3631293047
  click a49aff00e74c "https://vocab.methodandstructure.com/ibis#supported-by"
  B06013c31b5c2 --- 853b23dc18e0(["response"])--> B4a2f871f02f7
  click 853b23dc18e0 "https://vocab.methodandstructure.com/ibis#response"
  B6e13a6911ba1 --- 30a87c2c79ba(["opposed by"])--> B26a7c81b7170
  click 30a87c2c79ba "https://vocab.methodandstructure.com/ibis#opposed-by"
  B26a7c81b7170 --- 0e57f5cee5a8(["type"])--> https___vocab_methodandstructure_com_ibis_Argument
  click 0e57f5cee5a8 "http://www.w3.org/1999/02/22-rdf-syntax-ns#type"
  B4a2f871f02f7 --- ffabfaf3cb08(["opposed by"])--> B40121b421666
  click ffabfaf3cb08 "https://vocab.methodandstructure.com/ibis#opposed-by"
  Bdb67a4225c37 --- df0ae3bbd5d4(["supported by"])--> Bf0c7423c62bc
  click df0ae3bbd5d4 "https://vocab.methodandstructure.com/ibis#supported-by"
  B641f043d8de7 --- dc3b09026ccd(["type"])--> https___vocab_methodandstructure_com_ibis_Argument
  click dc3b09026ccd "http://www.w3.org/1999/02/22-rdf-syntax-ns#type"
  Bef30dbfcc950 --- 245a02c1eef7(["type"])--> https___vocab_methodandstructure_com_ibis_Argument
  click 245a02c1eef7 "http://www.w3.org/1999/02/22-rdf-syntax-ns#type"
  Bc2a89a0c737d --- 6ed5106e1e06(["type"])--> https___vocab_methodandstructure_com_ibis_Position
  click 6ed5106e1e06 "http://www.w3.org/1999/02/22-rdf-syntax-ns#type"
  B80eae73a5d4b --- da6166551cfc(["type"])--> https___vocab_methodandstructure_com_ibis_Argument
  click da6166551cfc "http://www.w3.org/1999/02/22-rdf-syntax-ns#type"
  B20007dcd409e --- 44e4def65edc(["comment"])--> Literal-489c7cc3ef52
  click 44e4def65edc "http://www.w3.org/2000/01/rdf-schema#comment"
  B4a2f871f02f7 --- 468d88666d7a(["supported by"])--> Ba9eb731a9e30
  click 468d88666d7a "https://vocab.methodandstructure.com/ibis#supported-by"
  B13e130a2e5fc --- 1b8ca4bfebb6(["type"])--> https___vocab_methodandstructure_com_ibis_Argument
  click 1b8ca4bfebb6 "http://www.w3.org/1999/02/22-rdf-syntax-ns#type"
  B4a2f871f02f7 --- 261d6a863eab(["type"])--> https___vocab_methodandstructure_com_ibis_Position
  click 261d6a863eab "http://www.w3.org/1999/02/22-rdf-syntax-ns#type"
  B1a8ef6296b42 --- cc54f5d38dfe(["opposed by"])--> Bf4ba3ff94fd8
  click cc54f5d38dfe "https://vocab.methodandstructure.com/ibis#opposed-by"
  B641f043d8de7 --- f4630b32ca77(["comment"])--> Literal-c6024b6ce405
  click f4630b32ca77 "http://www.w3.org/2000/01/rdf-schema#comment"
  B4a2f871f02f7 --- f057729a09b0(["supported by"])--> B99073f8d9343
  click f057729a09b0 "https://vocab.methodandstructure.com/ibis#supported-by"
  B06013c31b5c2 --- aa75c3a8e580(["response"])--> B4fd68375a00e
  click aa75c3a8e580 "https://vocab.methodandstructure.com/ibis#response"
  B1a8ef6296b42 --- fa1d7fd91c69(["opposed by"])--> Bc97ecab0f65d
  click fa1d7fd91c69 "https://vocab.methodandstructure.com/ibis#opposed-by"
  Bc780551a69d3 --- de33ec8a8dc5(["comment"])--> Literal-6ee14fa825c0
  click de33ec8a8dc5 "http://www.w3.org/2000/01/rdf-schema#comment"
  B20007dcd409e --- 5d653d8bcf42(["type"])--> https___vocab_methodandstructure_com_ibis_Argument
  click 5d653d8bcf42 "http://www.w3.org/1999/02/22-rdf-syntax-ns#type"
  B6e13a6911ba1 --- 6df9677aa9a5(["supported by"])--> Bef30dbfcc950
  click 6df9677aa9a5 "https://vocab.methodandstructure.com/ibis#supported-by"
  Ba107a6b9cb7e --- 38b3183c2f81(["type"])--> https___vocab_methodandstructure_com_ibis_Argument
  click 38b3183c2f81 "http://www.w3.org/1999/02/22-rdf-syntax-ns#type"
  Bb357c0431c4b --- 156c726d487b(["comment"])--> Literal-9a1a7a1280c5
  click 156c726d487b "http://www.w3.org/2000/01/rdf-schema#comment"
  B1469a9e8f1bb --- 67103faddc96(["opposed by"])--> Ba107a6b9cb7e
  click 67103faddc96 "https://vocab.methodandstructure.com/ibis#opposed-by"
  Bc780551a69d3 --- c88e0d723a69(["type"])--> https___vocab_methodandstructure_com_ibis_Argument
  click c88e0d723a69 "http://www.w3.org/1999/02/22-rdf-syntax-ns#type"
  B8c909c337620 --- 1503841ff43c(["type"])--> https___vocab_methodandstructure_com_ibis_Argument
  click 1503841ff43c "http://www.w3.org/1999/02/22-rdf-syntax-ns#type"
  B12a470ae96f5 --- d219bc0d0df9(["type"])--> https___vocab_methodandstructure_com_ibis_Argument
  click d219bc0d0df9 "http://www.w3.org/1999/02/22-rdf-syntax-ns#type"
  Bcf3631293047 --- eea42b699c02(["type"])--> https___vocab_methodandstructure_com_ibis_Argument
  click eea42b699c02 "http://www.w3.org/1999/02/22-rdf-syntax-ns#type"
  B383231988dd4 --- dfc42cc15e2f(["type"])--> https___vocab_methodandstructure_com_ibis_Argument
  click dfc42cc15e2f "http://www.w3.org/1999/02/22-rdf-syntax-ns#type"
  Bdb67a4225c37 --- b8cd0aec489a(["supported by"])--> Bb357c0431c4b
  click b8cd0aec489a "https://vocab.methodandstructure.com/ibis#supported-by"
  B1a8ef6296b42 --- 3af99f5ee2fd(["supported by"])--> B01b74e8b2b40
  click 3af99f5ee2fd "https://vocab.methodandstructure.com/ibis#supported-by"
  Bdb67a4225c37 --- 45b36f7ac41e(["type"])--> https___vocab_methodandstructure_com_ibis_Position
  click 45b36f7ac41e "http://www.w3.org/1999/02/22-rdf-syntax-ns#type"
  classDef predicate fill:#1f2233,stroke:transparent,color:#f8fafc,stroke-width:0px;
  classDef hidden fill:transparent,stroke:transparent,color:transparent,stroke-width:0px;
  classDef label fill:transparent,stroke:transparent,color:#e5e7eb,stroke-width:0px;
  classDef nanopubdot fill:#0f172a,stroke:#0f172a,color:transparent,stroke-width:2px;
  classDef transparent fill:transparent,stroke:transparent,color:transparent,stroke-width:0px;
  class 196d43cbdf11,e84baee6286c,55795af7d924,e13d2533100c,f857ebc6e504,83c24ca887aa,49e96341cb63,d361934ba253,ee0fd7b9aa5f,cad56228a64c,c5b2b643ee48,09f4a8451739,e120522b7054,210abd129985,e0bb3dc849ed,00aa94c1f449,5074d83f2973,0f763fd8cded,e1baa1baad17,822dabe6be8f,95d1d031894e,49bfb3cf0009,044ec00c58b6,756f74004ad9,7fd88708111f,1453f187b416,8abdf00cb2e6,33230ee86919,cd7adf56a157,0b29cecdbdd0,5de946e63e95,db2a30ffdc4f,cac0e668291f,b1fdc897157e,c97ef3640134,38f7f74acfc0,177beaf72504,f11d571a490d,47aeff0af1ce,a6d0fb7719df,3d669a27762f,e5729fc96757,d4694e4cc39c,9f07cb7cb3b9,6ae8cc7e55a2,3f6c52b352c7,955aee5db295,8603a835a89e,db6e96c0804c,cb975e07235a,435c30ad4c73,c1435028f525,8ea7e6b500db,475b21f084ee,a498c16bf46f,ae4b72a65800,79f6252823d2,0846499ef8d9,9398de53fd99,6375f82db69d,986bf5762684,537c63798d41,dc6b6f957910,8ab9e3c9dc1a,180821d808a8,0223c4b18ac3,229ea1b163a4,a428808a67b5,7be2efb4ff07,9ad5e3f78828,96d654b739be,161c059ea25a,c7a270435d6b,80f58e9056fc,3f0e849beff8,a49aff00e74c,853b23dc18e0,30a87c2c79ba,0e57f5cee5a8,ffabfaf3cb08,df0ae3bbd5d4,dc3b09026ccd,245a02c1eef7,6ed5106e1e06,da6166551cfc,44e4def65edc,468d88666d7a,1b8ca4bfebb6,261d6a863eab,cc54f5d38dfe,f4630b32ca77,f057729a09b0,aa75c3a8e580,fa1d7fd91c69,de33ec8a8dc5,5d653d8bcf42,6df9677aa9a5,38b3183c2f81,156c726d487b,67103faddc96,c88e0d723a69,1503841ff43c,d219bc0d0df9,eea42b699c02,dfc42cc15e2f,b8cd0aec489a,3af99f5ee2fd,45b36f7ac41e predicate

Remote @contexts considered harmful April 19, 2026

Problem

A JSON-LD document with a remote context does not fully define its own meaning. Its semantics depend on bytes fetched later from another URL.

The front page of json-ld.org presents us with an example statement about John Lennon, a famous British rock musician. For the sake of brevity and readability, let's rewrite this example in YAML-LD and render it as a graph.

"@context":
  - https://json-ld.org/contexts/person.jsonld
  - https://json-ld.org/contexts/dollar-convenience.jsonld
  - dbr: http://dbpedia.org/resource/
$id: dbr:John_Lennon
name: John Lennon
born: 1940-10-09
spouse: ["dbr:Yoko_Ono", "dbr:Cynthia_Lennon"]

graph LR
  http___dbpedia_org_resource_John_Lennon("John Lennon")
  click http___dbpedia_org_resource_John_Lennon "http://dbpedia.org/resource/John_Lennon"
  http___dbpedia_org_resource_Cynthia_Lennon("Cynthia Lennon")
  click http___dbpedia_org_resource_Cynthia_Lennon "http://dbpedia.org/resource/Cynthia_Lennon"
  http___dbpedia_org_resource_Yoko_Ono("Yoko Ono")
  click http___dbpedia_org_resource_Yoko_Ono "http://dbpedia.org/resource/Yoko_Ono"
  Literal-4649fa93775b[["📅 1940-10-09"]]
  http___dbpedia_org_resource_John_Lennon --- ccd6a52ef4f0(["spouse"])--> http___dbpedia_org_resource_Cynthia_Lennon
  click ccd6a52ef4f0 "http://schema.org/spouse"
  http___dbpedia_org_resource_John_Lennon --- dc81cc5be03d(["spouse"])--> http___dbpedia_org_resource_Yoko_Ono
  click dc81cc5be03d "http://schema.org/spouse"
  http___dbpedia_org_resource_John_Lennon --- ece8797f1934(["birthDate"])--> Literal-4649fa93775b
  click ece8797f1934 "http://schema.org/birthDate"
  classDef predicate fill:#1f2233,stroke:transparent,color:#f8fafc,stroke-width:0px;
  classDef hidden fill:transparent,stroke:transparent,color:transparent,stroke-width:0px;
  classDef label fill:transparent,stroke:transparent,color:#e5e7eb,stroke-width:0px;
  classDef nanopubdot fill:#0f172a,stroke:#0f172a,color:transparent,stroke-width:2px;
  classDef transparent fill:transparent,stroke:transparent,color:transparent,stroke-width:0px;
  class ccd6a52ef4f0,dc81cc5be03d,ece8797f1934 predicate

The machine responsible for rendering the graph was able to discern that the born: property maps to machine-readable http://schema.org/birthDate. That was possible thanks to the remote context that we referenced from https://json-ld.org/contexts/person.jsonld, here is the relevant excerpt:

person.jsonld

…
      "born":
      {
         "@id": "http://schema.org/birthDate",
         "@type": "xsd:date"
      },
…

What could go wrong?

What if the same context URL — https://json-ld.org/contexts/person.jsonld — returns different JSON than authors and readers expect? Nothing in your repository needs to change; only the bytes served at that URL change.

For instance, json-ld.org has been hacked, and now it returns a hostile response which keeps the same keys yet remaps born → schema:deathDate and spouse → schema:parent.

This would alter the meaning of the document about John Lennon:

Spoofed person.jsonld (excerpt)

…
    "born": {
      "@id": "http://schema.org/deathDate",
      "@type": "xsd:date"
    },
…
    "spouse": {
      "@id": "http://schema.org/parent",
      "@type": "@id"
    },
…

graph LR
  http___dbpedia_org_resource_John_Lennon("John Lennon")
  click http___dbpedia_org_resource_John_Lennon "http://dbpedia.org/resource/John_Lennon"
  Literal-4649fa93775b[["📅 1940-10-09"]]
  http___dbpedia_org_resource_Cynthia_Lennon("Cynthia Lennon")
  click http___dbpedia_org_resource_Cynthia_Lennon "http://dbpedia.org/resource/Cynthia_Lennon"
  http___dbpedia_org_resource_Yoko_Ono("Yoko Ono")
  click http___dbpedia_org_resource_Yoko_Ono "http://dbpedia.org/resource/Yoko_Ono"
  http___dbpedia_org_resource_John_Lennon --- faa2f964aa1f(["deathDate"])--> Literal-4649fa93775b
  click faa2f964aa1f "http://schema.org/deathDate"
  http___dbpedia_org_resource_John_Lennon --- 038343392367(["parent"])--> http___dbpedia_org_resource_Cynthia_Lennon
  click 038343392367 "http://schema.org/parent"
  http___dbpedia_org_resource_John_Lennon --- 987e5ca265cd(["parent"])--> http___dbpedia_org_resource_Yoko_Ono
  click 987e5ca265cd "http://schema.org/parent"
  classDef predicate fill:#1f2233,stroke:transparent,color:#f8fafc,stroke-width:0px;
  classDef hidden fill:transparent,stroke:transparent,color:transparent,stroke-width:0px;
  classDef label fill:transparent,stroke:transparent,color:#e5e7eb,stroke-width:0px;
  classDef nanopubdot fill:#0f172a,stroke:#0f172a,color:transparent,stroke-width:2px;
  classDef transparent fill:transparent,stroke:transparent,color:transparent,stroke-width:0px;
  class faa2f964aa1f,038343392367,987e5ca265cd predicate

JSON-LD 1.1 specification § Security Considerations warns:

JSON-LD contexts that are loaded from the Web over non-secure connections, such as HTTP, run the risk of being altered by an attacker such that they may modify the JSON-LD active context in a way that could compromise security.

Being hacked is not the only risk associated with remote contexts.

Risks

• Context Changed

  ---

  The context publisher does not need to be malicious for old documents to change meaning. A maintainer can revise a term mapping, publish an incompatible new version at the same URL, or make an ordinary mistake while editing the context. Existing documents keep pointing at the same URL, but now expand to different IRIs than they did when they were written.

• Context Spoofed

  ---

  The context URL resolves, but returns attacker-controlled content instead of the legitimate context. This can happen through fairly ordinary failures of Internet infrastructure and ownership:

  • DNS spoofing or cache poisoning
  • Domain name hijacking
  • Abandoned infrastructure or expired delegated domains leading to takeover
  • Cybersquatting

  ActivityPub implementations resolve JSON-LD over the wire when handling remote actors and objects; that has produced both shipped vulnerabilities and long-running design discussion about attacker-controlled contexts:

  • mastodon/mastodon GHSA-3fjr-858r-92rw
  • SocialHub — remote JSON-LD contexts in federation

• Context Unavailable

  ---

  The context URL stops resolving entirely. A processor that cannot retrieve a context cannot expand any of the terms it defines, so the document becomes unprocessable regardless of whether its own bytes are intact. Remote URLs are inherently fragile over time: link rot, server shutdowns, and deleted documents are ordinary events on a long enough horizon.

• Client Offline

  ---

  Many JSON-LD and YAML-LD workflows need documents to remain processable without any network access at all: air-gapped deployments, archival workflows, reproducible builds, local analysis, privacy-sensitive processing, or simply working offline on a laptop. This is separate from server failure: a context server may be healthy and reachable in principle, yet the document still fails in any environment that forbids or lacks network access.

• Privacy Exposure

  ---

  Each remote context fetch tells the context publisher which document is being processed and by whom — a timing and correlation signal. The JSON-LD WG addresses this under privacy considerations for remote contexts ( w3c/json-ld-syntax#430).

• Server Overloaded

  ---

  A context URL shared across millions of documents generates a fetch every time any processor encounters any of those documents. High-volume deployments such as ActivityPub federation, Verifiable Credential issuers, and bulk RDF pipelines can produce enormous request rates against a handful of context servers. This is precisely why the JSON-LD Best Practices recommend liberal cache-control headers and why implementations such as mastodon/mastodon#9412 cache contexts rather than fetching them on demand.

The specification itself points toward one mitigation direction for semantic instability, which brings us to the first alternative.

Alternatives

The matrix below summarizes how each alternative addresses the six risks above. Each alternative name links to its tab for details.

Legend: mitigates, partially or conditionally mitigates, does not mitigate.

	Context Changed	Context Spoofed	Context Unavailable	Client Offline	Privacy Exposure	Server Overloaded
@sri
@protected
Inline Contexts
Hash Fragment in application/ld+json
Content-Addressed Context URIs
Aggressively Cache Contexts
Use a Vetted Context Allowlist
Origin-Based Policy

The tabs below provide the example and the implementation tradeoffs for each alternative.

@sri@protectedInlineHashContent-AddressedCacheAllowlistOrigin

Future versions of this specification may incorporate subresource integrity [SRI] as a means of ensuring that cached and retrieved content matches data retrieved from remote servers; see w3c/json-ld-syntax#86.

— JSON-LD 1.1 § Security Considerations

One concrete proposal is w3c/json-ld-syntax#108 (see also w3c/json-ld-syntax#422):

john-lennon-sri.jsonld

{
  "@context": {
    "@value": "https://json-ld.org/contexts/person.jsonld",
    "@sri": "sha256-abc123..."
  },
  "@id": "http://dbpedia.org/resource/John_Lennon",
  "name": "John Lennon",
  "born": "1940-10-09",
  "spouse": [
    "http://dbpedia.org/resource/Yoko_Ono",
    "http://dbpedia.org/resource/Cynthia_Lennon"
  ]
}

Result

╭──────────────────────────────────────────────────────────────────────────────╮
│ ('Invalid JSON-LD syntax; keywords cannot be overridden.',) Type:            │
│ jsonld.SyntaxError Code: keyword redefinition Details: {'context':           │
│ {'@value': 'https://json-ld.org/contexts/person.jsonld', '@sri':             │
│ 'sha256-abc123...'}, 'term': '@value'}                                       │
╰──────────────────────────────────────────────────────────────────────────────╯

Pro

• Familiar model: Direct analogy to a proven browser standard, HTML SRI
• Self-contained reference: The hash travels with the reference, with no separate lockfile

Contra

• Awkward object form: A plain URL reference turns into a structured object, making the simplest @context case heavier and less readable
• Syntax ambiguity: It is unclear how to distinguish metadata objects from inline context-by-value objects
• Incomplete coverage: Does not yet cover @import chains

Used to prevent term definitions of a context to be overridden by other contexts.

— JSON-LD 1.1 § Syntax Tokens and Keywords

For example, the John Lennon document could protect born and spouse before a later spoofed context is loaded. Instead of producing the spoofed graph, the processor rejects the document:

That only helps when terms are protected before the later context is loaded; it does not authenticate the fetched context.

john-lennon-protected.yamlld

"@context":
  - born:
      "@id": http://schema.org/birthDate
      "@type": xsd:date
      "@protected": true
    spouse:
      "@id": http://schema.org/spouse
      "@type": "@id"
      "@protected": true
    dbr: http://dbpedia.org/resource/
    xsd: http://www.w3.org/2001/XMLSchema#
  - person-spoofed.jsonld  # Spoofed, https://json-ld.org/contexts/person.jsonld was here originally
  - https://json-ld.org/contexts/dollar-convenience.jsonld
$id: dbr:John_Lennon
name: John Lennon
born: 1940-10-09
spouse: ["dbr:Yoko_Ono", "dbr:Cynthia_Lennon"]

Result

╭──────────────────────────────────────────────────────────────────────────────╮
│ ('Invalid JSON-LD syntax; tried to redefine a protected term.',) Type:       │
│ jsonld.SyntaxError Code: protected term redefinition Details: {'context':    │
│ {'Person': 'http://xmlns.com/foaf/0.1/Person', 'xsd':                        │
│ 'http://www.w3.org/2001/XMLSchema#', 'name':                                 │
…

Pro

• Already in JSON-LD 1.1: No new syntax or future revision is required

Contra

• Messy inline setup: Meaningful protection requires declaring key terms inline before loading remote contexts, which reduces the value of loading them remotely at all
• Limited scope: It protects named term definitions, not terms resolved through @vocab or @base
• No fetch integrity: It does not authenticate the remote context or pin its bytes
• No @import fix: Imported contexts still extend the same remote trust boundary

In JSON-LD documents, contexts may also be specified inline. This has the advantage that documents can be processed even in the absence of a connection to the Web.

— JSON-LD 1.1 § The Context

Instead of URL references in the John Lennon document, embed the needed term definitions directly in the document itself.

john-lennon-inline-context.yamlld

"@context":
  born:
    "@id": http://schema.org/birthDate
    "@type": xsd:date
  spouse:
    "@id": http://schema.org/spouse
    "@type": "@id"
  name: http://xmlns.com/foaf/0.1/name
  dbr: http://dbpedia.org/resource/
  xsd: http://www.w3.org/2001/XMLSchema#
$id: dbr:John_Lennon
name: John Lennon
born: 1940-10-09
spouse: ["dbr:Yoko_Ono", "dbr:Cynthia_Lennon"]

graph LR
  5f101372727c98c91391212c3a17d5ea_b0("John Lennon")
  Literal-4649fa93775b9ab0c7a5e1bd15b6744a[["📅 1940-10-09"]]
  5f101372727c98c91391212c3a17d5ea_b0("John Lennon")
  http___dbpedia_org_resource_Cynthia_Lennon("Cynthia Lennon")
  click http___dbpedia_org_resource_Cynthia_Lennon "http://dbpedia.org/resource/Cynthia_Lennon"
  5f101372727c98c91391212c3a17d5ea_b0("John Lennon")
  http___dbpedia_org_resource_Yoko_Ono("Yoko Ono")
  click http___dbpedia_org_resource_Yoko_Ono "http://dbpedia.org/resource/Yoko_Ono"
  5f101372727c98c91391212c3a17d5ea_b0 --- c61fa04ee4bc149ca544908066fc5320(["birthDate"])--> Literal-4649fa93775b9ab0c7a5e1bd15b6744a
  click c61fa04ee4bc149ca544908066fc5320 "http://schema.org/birthDate"
  class c61fa04ee4bc149ca544908066fc5320 predicate
  5f101372727c98c91391212c3a17d5ea_b0 --- 9a4226e685e7907b94de856d2f6fbda5(["spouse"])--> http___dbpedia_org_resource_Cynthia_Lennon
  click 9a4226e685e7907b94de856d2f6fbda5 "http://schema.org/spouse"
  class 9a4226e685e7907b94de856d2f6fbda5 predicate
  5f101372727c98c91391212c3a17d5ea_b0 --- 6c450ce6fb06a569581c81cc5107d4b3(["spouse"])--> http___dbpedia_org_resource_Yoko_Ono
  click 6c450ce6fb06a569581c81cc5107d4b3 "http://schema.org/spouse"
  class 6c450ce6fb06a569581c81cc5107d4b3 predicate
  classDef predicate fill:#1f2233,stroke:transparent,color:#f8fafc,stroke-width:0px;
  classDef hidden fill:transparent,stroke:transparent,color:transparent,stroke-width:0px;
  classDef label fill:transparent,stroke:transparent,color:#e5e7eb,stroke-width:0px;
  classDef nanopubdot fill:#0f172a,stroke:#0f172a,color:transparent,stroke-width:2px;
  classDef transparent fill:transparent,stroke:transparent,color:transparent,stroke-width:0px;

Pro

• Single-file semantics: The document fully carries the term definitions it depends on
• No loader policy: Correct processing does not depend on cache or document-loader configuration

Contra

• Verbose: Large shared contexts such as schema.org are repeated in every document
• No deduplication: Context updates require re-issuing all documents

The Working Group intends to address this problem through more explanatory specification text, but also through the exploration of options such as the addition of a hash fragment to be used with the application/ld+json media type responses. This fragment conveys a content hash which may be used by implementations to further confirm and handle the intentions of the original document author.

— JSON-LD Working Group Charter § Scope

For the John Lennon context, this would look like:

This does not mitigate the risks above because the hash is supplied by the response server, not by the document that references the context.

john-lennon-context-response.http

Content-Type: application/ld+json; hash="sha256-abc123..."

graph LR
  http___dbpedia_org_resource_John_Lennon("John Lennon")
  click http___dbpedia_org_resource_John_Lennon "http://dbpedia.org/resource/John_Lennon"
  http___dbpedia_org_resource_Yoko_Ono("Yoko Ono")
  click http___dbpedia_org_resource_Yoko_Ono "http://dbpedia.org/resource/Yoko_Ono"
  http___dbpedia_org_resource_John_Lennon("John Lennon")
  click http___dbpedia_org_resource_John_Lennon "http://dbpedia.org/resource/John_Lennon"
  Literal-4649fa93775b9ab0c7a5e1bd15b6744a[["📅 1940-10-09"]]
  http___dbpedia_org_resource_John_Lennon("John Lennon")
  click http___dbpedia_org_resource_John_Lennon "http://dbpedia.org/resource/John_Lennon"
  http___dbpedia_org_resource_Cynthia_Lennon("Cynthia Lennon")
  click http___dbpedia_org_resource_Cynthia_Lennon "http://dbpedia.org/resource/Cynthia_Lennon"
  http___dbpedia_org_resource_John_Lennon --- 203e23da021cfaec8fe3608f1809cc89(["spouse"])--> http___dbpedia_org_resource_Yoko_Ono
  click 203e23da021cfaec8fe3608f1809cc89 "http://schema.org/spouse"
  class 203e23da021cfaec8fe3608f1809cc89 predicate
  http___dbpedia_org_resource_John_Lennon --- 1759f753de49b9a729174a0162121fbc(["birthDate"])--> Literal-4649fa93775b9ab0c7a5e1bd15b6744a
  click 1759f753de49b9a729174a0162121fbc "http://schema.org/birthDate"
  class 1759f753de49b9a729174a0162121fbc predicate
  http___dbpedia_org_resource_John_Lennon --- 5467d103f69601bbafb5c89daa6ba9e2(["spouse"])--> http___dbpedia_org_resource_Cynthia_Lennon
  click 5467d103f69601bbafb5c89daa6ba9e2 "http://schema.org/spouse"
  class 5467d103f69601bbafb5c89daa6ba9e2 predicate
  classDef predicate fill:#1f2233,stroke:transparent,color:#f8fafc,stroke-width:0px;
  classDef hidden fill:transparent,stroke:transparent,color:transparent,stroke-width:0px;
  classDef label fill:transparent,stroke:transparent,color:#e5e7eb,stroke-width:0px;
  classDef nanopubdot fill:#0f172a,stroke:#0f172a,color:transparent,stroke-width:2px;
  classDef transparent fill:transparent,stroke:transparent,color:transparent,stroke-width:0px;

Pro

• Transport-level enforcement: Analogous to how SRI works in browsers
• Transparent to authors: No syntax change required

Contra

• Server adoption required: Existing context servers such as schema.org and w3id.org would need to emit the header
• HTTP-only scope: It only helps when contexts are fetched through cooperating HTTP servers, not when they are copied, mirrored, or embedded elsewhere

This document defines the "Named Information" identifier, which provides a set of standard ways to use hash function outputs in names.

— RFC 6920 § 1: Introduction

Replace location-based context URLs with content-hash-based URIs: IPFS CIDs, ni: URIs, or Trusty URIs. For the John Lennon example, that means replacing the location-based person context with a content-addressed one:

john-lennon-content-addressed.yamlld

"@context":
  - ni:///sha-256;abc123...?ct=application/ld+json
  - https://json-ld.org/contexts/dollar-convenience.jsonld
  - dbr: http://dbpedia.org/resource/
$id: dbr:John_Lennon
name: John Lennon
born: 1940-10-09
spouse: ["dbr:Yoko_Ono", "dbr:Cynthia_Lennon"]

Result

╭──────────────────────────────────────────────────────────────────────────────╮
│ Failed to load the context.                                                  │
│                                                                              │
│ URL of the context: ni:///sha-256;abc123...?ct=application/ld+json Reason:   │
│ Cannot choose the loader by URL protocol.                                    │
│                                                                              │
│  • URL: ni:/sha-256;abc123...?ct=application/ld+json                         │
│  • Scheme: ni                                                                │
│  • Available schemes: file, http, https                                      │
╰──────────────────────────────────────────────────────────────────────────────╯

Pro

• Built-in integrity: The URI itself is the integrity check, so mutation produces a different URI by construction
• Architectural fit: Consistent with broader Linked Data trust literature, including Trusty URIs and nanopublications

Contra

• Migration cost: All existing context URLs such as schema.org and w3id.org would need to be replaced or aliased
• Weak adoption: The ni: scheme has no mainstream adoption, and IPFS adds infrastructure dependency
• Version churn: Context versioning becomes explicit URI changes, which may complicate backwards compatibility

Services providing a JSON-LD Context SHOULD set HTTP cache-control headers to allow liberal caching of such contexts, and clients SHOULD attempt to use a locally cached version of these documents.

— JSON-LD Best Practices: Cache JSON-LD Contexts

Aggressive caching keeps processors from repeatedly fetching the same shared context URL. It helps most after a known-good first fetch: later runs can reuse cached bytes, tolerate temporary outages, and avoid hammering shared context servers.

For PyLD, digitalbazaar/pyld#253 proposes a disk-backed document loader that would persist fetched documents and honor HTTP cache metadata such as Cache-Control, Expires, ETag, and Last-Modified.

john-lennon-context-cache-response.http

HTTP/1.1 200 OK
Content-Type: application/ld+json
Cache-Control: public, max-age=31536000, immutable

{
  "@context": {
    "born": {
      "@id": "http://schema.org/birthDate",
      "@type": "xsd:date"
    }
  }
}

Pro

• Server relief: Reduces repeated fetches against shared public context servers
• Warm-cache resilience: Repeat processing can survive temporary server or network failures

Contra

• First fetch still matters: A cache does not authenticate the first response or make spoofed bytes trustworthy
• Not permanent: Cached entries may expire, be evicted, or differ between deployments
• Limited offline privacy: Offline and privacy benefits only apply after the context is already cached locally

For air-gapped, security-hardened, reproducible, or privacy-sensitive deployments, a processor can refuse the network entirely and resolve known context URLs only from vetted local files.

digitalbazaar/pyld#250 proposes FrozenDocumentLoader, which lets PyLD convert the document to RDF using only an explicit allowlist of local context files:

john_lennon_vetted_loader.py

from pathlib import Path

import yaml
from pyld import FrozenDocumentLoader, jsonld

HERE = Path(__file__).parent

loader = FrozenDocumentLoader(
    documents={
        "https://json-ld.org/contexts/person.jsonld": HERE / "person.jsonld",
        "https://json-ld.org/contexts/dollar-convenience.jsonld": (
            HERE / "dollar-convenience.jsonld"
        ),
    },
)

document = yaml.safe_load((HERE / "john-lennon.yamlld").read_text())

rdf_dataset = jsonld.to_rdf(
    document,
    options={"documentLoader": loader},
)

graph LR
  http___dbpedia_org_resource_John_Lennon("John Lennon")
  click http___dbpedia_org_resource_John_Lennon "http://dbpedia.org/resource/John_Lennon"
  http___dbpedia_org_resource_Yoko_Ono("Yoko Ono")
  click http___dbpedia_org_resource_Yoko_Ono "http://dbpedia.org/resource/Yoko_Ono"
  http___dbpedia_org_resource_John_Lennon("John Lennon")
  click http___dbpedia_org_resource_John_Lennon "http://dbpedia.org/resource/John_Lennon"
  Literal-4649fa93775b9ab0c7a5e1bd15b6744a[["📅 1940-10-09"]]
  http___dbpedia_org_resource_John_Lennon("John Lennon")
  click http___dbpedia_org_resource_John_Lennon "http://dbpedia.org/resource/John_Lennon"
  http___dbpedia_org_resource_Cynthia_Lennon("Cynthia Lennon")
  click http___dbpedia_org_resource_Cynthia_Lennon "http://dbpedia.org/resource/Cynthia_Lennon"
  http___dbpedia_org_resource_John_Lennon --- 203e23da021cfaec8fe3608f1809cc89(["spouse"])--> http___dbpedia_org_resource_Yoko_Ono
  click 203e23da021cfaec8fe3608f1809cc89 "http://schema.org/spouse"
  class 203e23da021cfaec8fe3608f1809cc89 predicate
  http___dbpedia_org_resource_John_Lennon --- 1759f753de49b9a729174a0162121fbc(["birthDate"])--> Literal-4649fa93775b9ab0c7a5e1bd15b6744a
  click 1759f753de49b9a729174a0162121fbc "http://schema.org/birthDate"
  class 1759f753de49b9a729174a0162121fbc predicate
  http___dbpedia_org_resource_John_Lennon --- 5467d103f69601bbafb5c89daa6ba9e2(["spouse"])--> http___dbpedia_org_resource_Cynthia_Lennon
  click 5467d103f69601bbafb5c89daa6ba9e2 "http://schema.org/spouse"
  class 5467d103f69601bbafb5c89daa6ba9e2 predicate
  classDef predicate fill:#1f2233,stroke:transparent,color:#f8fafc,stroke-width:0px;
  classDef hidden fill:transparent,stroke:transparent,color:transparent,stroke-width:0px;
  classDef label fill:transparent,stroke:transparent,color:#e5e7eb,stroke-width:0px;
  classDef nanopubdot fill:#0f172a,stroke:#0f172a,color:transparent,stroke-width:2px;
  classDef transparent fill:transparent,stroke:transparent,color:transparent,stroke-width:0px;

Pro

• PyLD-managed allowlist: Uses a reusable document loader instead of custom fetch logic
• Strict local policy: Unknown context URLs are refused instead of fetched
• Fits controlled deployments: Works well for archival, reproducible, air-gapped, and privacy-sensitive processing

Contra

• Operational burden: Requires an organizational process to update and re-vet cached copies
• Policy portability gap: A document does not carry its own trust policy, so another deployment may resolve the same contexts differently

The same-origin policy uses URIs to designate trust relationships.

— RFC 6454 § 3.5: Conclusion

Applied to JSON-LD context loading: a document from https://example.org would load same-origin contexts by default; cross-origin contexts would require explicit CORS permission. This is a rejected non-solution: it controls origin access, not context bytes or durability.

Pro

• Self-describing policy: No external configuration or allowlist is needed
• Mature model: It is already implemented in every web browser

Contra

• Impractical default: Most real JSON-LD usage is cross-origin by design, so shared vocabularies such as schema.org and w3id.org would be blocked without a cross-origin permission mechanism
• Wrong layer: It restricts who can serve contexts, not what they contain; a same-origin server can still change, spoof, or lose its context