Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Consistent naming for invocation and execution #25

@andrewzhurov

Description

@andrewzhurov

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions