Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Consistent naming for invocation and execution #25

Open
andrewzhurov opened this issue Sep 5, 2023 · 0 comments
Open

Consistent naming for invocation and execution #25

andrewzhurov opened this issue Sep 5, 2023 · 0 comments

Comments

@andrewzhurov
Copy link
Contributor

andrewzhurov commented Sep 5, 2023

We define the following roles

Task adds two new roles to UCAN: invoker and executor. The existing UCAN delegator and delegate principals MUST persist to the invocation.

UCAN Field Delegation Task
iss Delegator: transfer authority (active) Invoker: request task (active)
aud Delegate: gain authority (passive) Executor: perform task (active)

Should it be
Invoker: requests invocation (active)
Executor: executes invocation (active)

Then, Invoker issues Invocation of a Task, as it is now, and executor issues Execution of an Invocation instead of Receipt.
I.e., renaming, in the upcoming release #21, Receipt -> Execution.

As a side-plus, "Execution Result", "Execution Effect" feels properly semantical.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant