From 3d1efc090a905a277852e1c3fc31cefeffdfe81c Mon Sep 17 00:00:00 2001 From: "Tammi L. Coles" Date: Fri, 19 Jan 2024 14:31:46 +0100 Subject: [PATCH] edit 20.1 notations section --- book/source/adv/signatures.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/book/source/adv/signatures.md b/book/source/adv/signatures.md index daf2769..f6a0d9b 100644 --- a/book/source/adv/signatures.md +++ b/book/source/adv/signatures.md @@ -8,11 +8,11 @@ SPDX-License-Identifier: CC-BY-SA-4.0 (notation-signature-subpackets)= ## Notation signature subpackets -[Notation signature subpackets](https://www.ietf.org/archive/id/draft-ietf-openpgp-crypto-refresh-12.html#notation-data) can be used to effectively extend the otherwise limited set of {term}`signature subpacket types` in OpenPGP with user-defined {term}`notations`. {term}`Issuers` can use these {term}`notations` to add name-value pairs to an {term}`OpenPGP signature`. +[Notation signature subpackets](https://www.ietf.org/archive/id/draft-ietf-openpgp-crypto-refresh-12.html#notation-data) can extend the otherwise limited set of {term}`signature subpacket types` in OpenPGP with user-defined {term}`notations`. {term}`Issuers` can use these {term}`notations` to add name-value pairs to an {term}`OpenPGP signature`. -{term}`Notation` names - strings encoded in UTF-8 - may reside in the "user namespace." This namespace is characterized by a {term}`notation tag`, followed by a DNS domain name, both in UTF-8 format. +{term}`Notation` names – strings encoded in UTF-8 – may reside in the "user namespace." In this namespace, each notation is identified by a {term}`notation tag`, which is followed by a DNS domain name. Both the notation tag and the domain name are encoded in UTF-8 format. -{term}`Notations`, as described earlier, allow for user-defined extensions to the {term}`OpenPGP signature subpacket types`. A practical and popular application of this functionality is seen in Keyoxide, a decentralized {term}`identity verification` service. Keyoxide uses {term}`notations` in the `ariadne.id` namespace. For the details of this {term}`implementation`, refer to the [Keyoxide documentation](https://docs.keyoxide.org/wiki/ariadne-identity/). +{term}`Notations` allow for user-defined extensions to the {term}`OpenPGP signature subpacket types`. A practical and popular example of this functionality is applied in Keyoxide, a decentralized {term}`identity verification` service. Keyoxide uses {term}`notations` in the `ariadne.id` namespace. For the details of this {term}`implementation`, refer to the [Keyoxide documentation](https://docs.keyoxide.org/wiki/ariadne-identity/). ## Choosing the hash algorithm for a signature