Dave Longley
Dave Longley
+1 for providing an optional "local only" document loader like the one in the README.
Instead of providing a local context loader I think the README should be updated to reference another module that provides a document loader with the features mentioned. I'll leave this...
Yes, this definitely sounds excessive and we should look into it.
Hi @jmcanterafonseca-iota! The reason why you get different output when you use a different JSON key (e.g., `"https://example.org/bizStep"`) is because it no longer matches the term in the context (`"bizStep"`)...
Any tests that involve prepending base (or other base manipulations) should include URLs like this: `did:example:test:1234` and `did:example:test:1234?query=foo`.
@davidlehn -- we need this implemented right away to stop the proliferation of `@version`.
Seems like a bug or a not implemented to me; will need to look more closely.
@davidlehn -- can you take a look here?
> I can't find an open issue for this. Then this is the issue for it! :) HTTP caching isn't implemented in the node.js document loader, ie: HTTP cache headers...
Well, honestly, I'm not that concerned about the maintenance costs for having two separate mechanisms in node vs. the browser. The browser has just about everything already built-in; we don't...