Conversation

Notices

1. Christine Lemmer-Webber (cwebber@octodon.social)'s status on Thursday, 03-Oct-2019 14:08:39 UTC Christine Lemmer-Webber

   • Jack Allnutt

   @jack Hi! These are great questions. It depends on the kind of ocaps you're doing, first of all! Let me give you two versions:

   - programming ocaps: an object/function has a reference to another object/function. They forward some calls but not all (eg forward only certain methods). No requirement of "shared terminology". http://mumble.net/~jar/pubs/secureos/secureos.html http://erights.org/elib/capability/ode/index.html
   - certificate ocaps (eg zcap-ld): require shared understanding of terms https://w3c-ccg.github.io/zcap-ld/

   • Christine Lemmer-Webber (cwebber@octodon.social)'s status on Thursday, 03-Oct-2019 14:11:27 UTC Christine Lemmer-Webber

     in reply to

     • Jack Allnutt

     @jack Now the former does not require "mutual understanding" of terms; whoever is the proxy knows what is and isn't allowed and simply forwards or doesn't. (However, "shortening" is an option so that server A both does not have to "proxy" to server B; this would require setting up an equivalent proxy back on server B again, which requires that server A and B can negotiate what that attenuation is.)

     In the case of certificate ocaps, then there does require some mutual terminology understanding