From e28f96265bc60fc93d9d24d459e21ae26ea6d585 Mon Sep 17 00:00:00 2001 From: silverpill Date: Sat, 15 Jul 2023 09:25:26 +0000 Subject: [PATCH] FEP-8b32: Update proposal (#133) - Update references to Data Integrity spec. - Require proof purpose to be assertionMethod. Co-authored-by: silverpill Reviewed-on: https://codeberg.org/fediverse/fep/pulls/133 Co-authored-by: silverpill Co-committed-by: silverpill --- fep/8b32/fep-8b32.feature | 2 +- fep/8b32/fep-8b32.md | 6 +++--- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/fep/8b32/fep-8b32.feature b/fep/8b32/fep-8b32.feature index 79edd33..413bd4f 100644 --- a/fep/8b32/fep-8b32.feature +++ b/fep/8b32/fep-8b32.feature @@ -81,7 +81,7 @@ Feature: FEP-8b32: Object Integrity Proofs "id": "https://server.example/users/alice", "inbox": "https://server.example/users/alice/inbox", "outbox": "https://server.example/users/alice/outbox", - "authentication": [ + "assertionMethod": [ { "id": "https://server.example/users/alice#ed25519-key", "type": "Multikey", diff --git a/fep/8b32/fep-8b32.md b/fep/8b32/fep-8b32.md index 69e8886..fa55a9c 100644 --- a/fep/8b32/fep-8b32.md +++ b/fep/8b32/fep-8b32.md @@ -30,7 +30,7 @@ The proposed authentication mechanism is based on [Data Integrity](https://w3c.g ### Proof generation -The proof MUST be created according to the *Data Integrity* specification, section [4.1 Generate Proof](https://w3c.github.io/vc-data-integrity/#generate-proof). +The proof MUST be created according to the *Data Integrity* specification, section [4.1 Add Proof](https://w3c.github.io/vc-data-integrity/#add-proof). The process of proof generation consists of the following steps: @@ -82,7 +82,7 @@ Example of activity with integrity proof: } ``` -The list of attributes used in integrity proof is defined in *Data Integrity* specification, section [2.1 Proofs](https://w3c.github.io/vc-data-integrity/#proofs). The proof type SHOULD be `DataIntegrityProof`, as specified in section [3.1 DataIntegrityProof](https://w3c.github.io/vc-data-integrity/#dataintegrityproof). The value of `verificationMethod` attribute SHOULD be an URL of actor's public key or a [DID](https://www.w3.org/TR/did-core/) associated with an actor. +The list of attributes used in integrity proof is defined in *Data Integrity* specification, section [2.1 Proofs](https://w3c.github.io/vc-data-integrity/#proofs). The proof type SHOULD be `DataIntegrityProof`, as specified in section [3.1 DataIntegrityProof](https://w3c.github.io/vc-data-integrity/#dataintegrityproof). The value of `verificationMethod` attribute SHOULD be an URL of actor's public key or a [DID](https://www.w3.org/TR/did-core/) associated with an actor. The value of `proofPurpose` attribute MUST be `assertionMethod`. ### Proof verification @@ -121,7 +121,7 @@ See [fep-8b32.feature](./fep-8b32.feature) - [ActivityPub] Christine Lemmer Webber, Jessica Tallon, [ActivityPub](https://www.w3.org/TR/activitypub/), 2018 - [RFC-2119] S. Bradner, [Key words for use in RFCs to Indicate Requirement Levels](https://tools.ietf.org/html/rfc2119.html), 1997 -- [Data Integrity] Dave Longley, Manu Sporny, [Verifiable Credential Data Integrity 1.0](https://w3c.github.io/vc-data-integrity/), 2022 +- [Data Integrity] Dave Longley, Manu Sporny, [Verifiable Credential Data Integrity 1.0](https://w3c.github.io/vc-data-integrity/), 2023 - [DID] Manu Sporny, Dave Longley, Markus Sabadell, Drummond Reed, Orie Steele, Christopher Allen, [Decentralized Identifiers (DIDs) v1.0](https://www.w3.org/TR/did-core/), 2022 - [jcs-eddsa-2022] Dave Longley, Manu Sporny, [EdDSA Cryptosuite v2022](https://w3c.github.io/vc-di-eddsa/), 2023 - [JCS] A. Rundgren, B. Jordan, S. Erdtman, [JSON Canonicalization Scheme (JCS)](https://www.rfc-editor.org/rfc/rfc8785), 2020