From 62d490367d48889552f85b794598db8438b6b64b Mon Sep 17 00:00:00 2001 From: Brooklyn Zelenka Date: Mon, 16 Oct 2023 16:32:37 -0700 Subject: [PATCH] Fix name --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 1894ae4..93cebb2 100644 --- a/README.md +++ b/README.md @@ -273,7 +273,7 @@ Abilities MUST be presented as a case-insensitive string. By convention, abiliti } ``` -Abilities MAY be organized in a hierarchy that abstract over many [Action]s. A typical example is a superuser capability ("anything") on a file system. Another is command vs query access, such that in an HTTP context, `WRITE` implies `PUT`, `PATCH`, `DELETE`, and so on. [`*` gives full access][Wildcard Ability] to a Resource more in the vein of object capabilities. Organizing abilities this way allows Resources to evolve over time in a backward-compatible manner, avoiding the need to reissue UCANs with new resource semantics. +Abilities MAY be organized in a hierarchy that abstract over many [Command]s. A typical example is a superuser capability ("anything") on a file system. Another is mutation vs read access, such that in an HTTP context, `write` implies `put`, `patch`, `delete`, and so on. [`*` gives full access][Wildcard Ability] to a Resource more in the vein of object capabilities. Organizing abilities this way allows Resources to evolve over time in a backward-compatible manner, avoiding the need to reissue UCANs with new resource semantics. ### 4.3.1 Reserved Abilities @@ -655,7 +655,7 @@ We want to especially recognize [Mark Miller] for his numerous contributions to [Mikael Rogers]: https://github.com/mikeal/ [OCAP]: https://en.wikipedia.org/wiki/Object-capability_model [OCapN]: https://github.com/ocapn/ -[Operation]: https://github.com/ucan-wg/spec#33-operation +[Command]: https://github.com/ucan-wg/spec#33-command [Philipp Krüger]: https://github.com/matheus23 [PoLA]: https://en.wikipedia.org/wiki/Principle_of_least_privilege [Protocol Labs]: https://protocol.ai/