Christine Lemmer-Webber
Christine Lemmer-Webber
It MUST not be possible to swap out keys or capability documents unexpectedly. In general, I think this makes the case for immutability such as content addressing of capability documents...
I'm going to elaborate on this further in the thread, and indeed much conversation on this has recently happened [on the cap-talk mailing list](https://groups.google.com/forum/#!topic/cap-talk/e48rvAc1t9A). But first a high level summary......
We say so in the ocap-ld spec currently, but if the capability document is embedded with the invocation, I don't see why that's true. The main case it would make...
The "Actions" section is outdated... we no longer use the `action` property, since the invocation document's `@type` is the action.
To prevent ambient authority, the toplevel capability document should specify a list of actions (read: the types valid for the invocation document) which are acceptable. Later documents in the chain...
This has come up in #5 and in [this issue on the VC repo](https://github.com/w3c/vc-data-model/issues/72) but it really is its own discussion. First off, *can* ld-ocap be built on top of...
In some json-ld using applications, input may be consumed with a default/limplied context, which ensures robustness in case not all participants are "json-ld aware". These are generally not formally specified...
> Object Capabilities is limited authority by possession; you are allowed to do something in a system because you hold something that allows you to do it. A valet key...
> I think I found an accessibility bug in the GUI view 🙂 It uses color indicators for test results in the tree of tests. This will work only for...