Using the network to distribute JSON-LD contexts and rule sets

[reinkrul]

Using the network to distribute JSON-LD contexts would have several advantages:

1. It empowers parties developing their own VCs:
   1.1. External parties developing custom VCs don't have to barter with the Nuts community if/when/how their JSON-LD contexts are released in a version.
   1.2. An alternative for the above would be to configure the Nuts node with the custom JSON-LD contexts, which is cumbersome and thus doesn't scale very well.
2. Network distribution might be more stable than hosting on a centralized webserver, which can be slow, temporarily down, misconfigured, permanently phased out of taken over by hackers (e.g., defacing, tampering).

Disadvantages:

1. JSON-LD contexts would be only resolvable for parties actually using the Nuts network. Sort of technology-lockin.
   1.1. Alternative; resolve in JSON-LD contexts received over Nuts network first, then fallback to HTTP if not found.
   Would require measures to avoid these 2 manifestations of the same JSON-LD context to differ, e.g. a hash of the JSON-LD context document in the URL.

[woutslakhorst]

1 doesn't promote using the network or an URL for distribution just the general advantage of a decentralised way of managing contexts.

3 URL based context is way easier to setup/implement

[woutslakhorst]

This is a more general discussion on implementing governance through the network. How to distribute the rules of a network.