Context namespace does not exist

[ubamrein]

In this commit the context string was changed from "../controller/.." to "../cid/..", but the document is not available under the new URL (so all examples provided fail) (and also not under the old one). Funny enough, the controller seems to be defined under the https://www.w3.org/ns/did/v1 namespace (according to https://w3c.github.io/vc-data-integrity/vocab/security/vocabulary.html#controller).

[msporny]

Yes, good catch. The current context URL is broken because we're in the middle of a specification rename and publication, which has gotten caught up in a month+ long administrative process. The URL will eventually resolve, and when it does, we'll note that in this issue.

[ubamrein]

Is there any preferred way, how to handle such cases (renaming/removing those context urls) when relaying on Json-LD expansion? Is it best to have local versions of the relevant documents?

[dlongley]

@ubamrein,

Is there any preferred way, how to handle such cases (renaming/removing those context urls) when relaying on Json-LD expansion? Is it best to have local versions of the relevant documents?

Yes, for well-defined and eventually immutable contexts (such as those in this specification and others produced by the VCWG), local copies of the contexts should absolutely be installed in software (similar to library "imports") and treated as if "already resolved" (i.e., always use a JSON-LD document loader that loads from your local copy) when performing JSON-LD API operations such as expansion.

Note that once the specs are finalized, the contexts identified by specific URLs in the specifications are expected to be immutable such that local copies made at that point should never change.

[ubamrein]

Thanks for clarifying!