Working on polls and writing a new #FEP
https://codeberg.org/silverpill/feps/src/branch/main/9967/fep-9967.md
Working on polls and writing a new #FEP
https://codeberg.org/silverpill/feps/src/branch/main/9967/fep-9967.md
I've made some changes to FEP-521a: https://codeberg.org/fediverse/fep/pulls/482
- Many changes due to a rename of Controller Documents specification to Controlled Identifiers.
- Using https://www.w3.org/ns/cid/v1 context in example. I haven't tried it myself yet, but it works in JSON-LD playground.
- Key ID and actor ID are now recommended to have same origin.
All implementations of FEP-521a are implementations of Controlled Identifiers spec.
#fep #fep_521a #ActivityPub #ControlledIdentifiers
RE: https://w3c.social/users/w3c/statuses/113947371169653222
I am working on a new revision of FEP-8b32:
https://codeberg.org/fediverse/fep/pulls/527
There are many editorial changes, such as replacing Controller Documents with Controlled Identifiers, new implementation (apsig), and one new requirement:
>The identifier of the verification method MUST have the same origin as the identifier of the secured document, or have a different origin, but with an established cross-origin trust relationship to the identifier of the secured document.
This is related to today's FEP-fe34 update and should cover all possible uses of integrity proofs, including regular objects signed with DID keys, and portable objects (FEP-ef61). I expect that all existing implementations of FEP-8b32 already meet this new requirement, but if not, please let me know. I'll keep this PR open / WIP for a couple of days.