Skip to content

Commit

Permalink
Spelling
Browse files Browse the repository at this point in the history
  • Loading branch information
expede committed Oct 13, 2023
1 parent 29150b6 commit 1354580
Show file tree
Hide file tree
Showing 2 changed files with 5 additions and 2 deletions.
2 changes: 2 additions & 0 deletions .custom-words.txt
Original file line number Diff line number Diff line change
Expand Up @@ -108,6 +108,7 @@ const
const
const
crudGraph
crypto
cryptographically
del
delegable
Expand All @@ -129,6 +130,7 @@ escelation
et
ewvi
ewvi
extensibility
extractable
filesystem
fooey
Expand Down
5 changes: 3 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -383,7 +383,7 @@ flowchart BT

## 4.4 Caveats

Caveats define a set of constraints on what can be redelegated or invoked. Caveat semantics MUST be established by the Subject. They are openly extensible, but vocabularies may be reused across many Subjects.
Caveats define a set of constraints on what can be re-delegated or invoked. Caveat semantics MUST be established by the Subject. They are openly extensible, but vocabularies may be reused across many Subjects.

Caveats MAY be open ended. Caveats MUST be understood by the executor of the eventual [invocation][UCAN Invocation]. Caveats MUST be formatted as maps.

Expand Down Expand Up @@ -434,7 +434,8 @@ The above MUST be interpreted as the set of capabilities below in the following
| `did:web:example.com` | `crud/update` | Posts at `https://blog.example.com` with the `published` status and tagged with `published` and `news` |

When validating a delegation chain in the abstract, all caveats MUST be present in each successive delegation. At invocation time, only the capability being invoked MUST be match the delegation chain.
Note that all caveats need to be understable to th executor

Note that all caveats need to be understood by the Executor.

### 4.4.1 The "True" Caveat

Expand Down

0 comments on commit 1354580

Please sign in to comment.