From 3fa59da52a6776d8722b835b934c4fc9f9bac2ec Mon Sep 17 00:00:00 2001 From: silverpill Date: Thu, 22 May 2025 22:26:47 +0200 Subject: [PATCH] FEP-521a: Rephrase recommendations for constructing key IDs (#605) Based on feedback: https://socialhub.activitypub.rocks/t/fep-521a-representing-actors-public-keys/3380/26 Reviewed-on: https://codeberg.org/fediverse/fep/pulls/605 Co-authored-by: silverpill Co-committed-by: silverpill --- fep/521a/fep-521a.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/fep/521a/fep-521a.md b/fep/521a/fep-521a.md index aeee503..18537dd 100644 --- a/fep/521a/fep-521a.md +++ b/fep/521a/fep-521a.md @@ -36,7 +36,7 @@ The `Multikey` object MAY contain the `expires` property indicating the expirati ### Key IDs -Identifiers SHOULD be generated by appending a fragment identifier to the actor ID. Different public keys of the same actor MUST be identified using different fragment IDs. +Identifiers SHOULD be generated by appending a fragment identifier to the actor ID. That allows consumers to retrieve both actor object and associated keys with a single HTTP request. If actor's keys are identified using fragment identifiers, each key MUST have a unique fragment identifier. Resolution of a URI containing a fragment identifier is performed using the algorithm specified in section *3.4 Fragment Resolution* of [Controlled Identifiers][FragmentResolution] specification.