{
  "_comment": "The ShExReduce extension's manifest vocabulary: what an examples manifest may write inside the mapping it binds to this file. Bound the way Map/manifest-context.jsonld explains: a term of the manifest's choosing (rdc:parms, say) whose property-scoped @context is this file's URL, declared beside the prefix in the manifest's @context -- `rdc: http://shex.io/extensions/Reduce/#` and, beside it, `rdc:parms: {@context: https://shexspec.github.io/extensions/Reduce/manifest-context.jsonld}` -- and never imported at the top level. overlay/overlayURL is an overlay: a document of semantic actions (the vocabulary http://shex.io/ns/semact#) applied to the entry's schema before it is used, so that a schema written without actions can be reduced -- the overlay's text, or where to fetch it. The two share one IRI, the URL form typed @id, as the shared vocabulary's schema/schemaURL do. Every name maps to an absolute IRI under http://shex.io/extensions/Reduce/# (the extension's semantic actions are dispatched on http://shex.io/extensions/Reduce/, without the #), and this file declares no prefix and nothing outside the scope, so it cannot collide with another vocabulary, whatever prefix the manifest chose for it. Outer names stay visible inside the scope, so shex.js's pluginURL, naming the web-app plugin that implements this vocabulary, is written inside the mapping too. Stacked, in a manifest, onto the ShEx manifest vocabulary (https://www.w3.org/ns/shex-manifest.jsonld) and whatever terms the manifest's author adds to it (shex.js's are https://shex.js.org/doc/manifest-context.jsonld).",

  "@context": {
    "overlay": "http://shex.io/extensions/Reduce/#overlay",
    "overlayURL": {"@id": "http://shex.io/extensions/Reduce/#overlay", "@type": "@id"}
  }
}