Events Interoperability: Validation, minimum requirements, common extensions

I created a first version of a FEP-8a8e: A common approach to using the Event object type

FEP: fep/fep/8a8e/fep-8a8e.md at fep-8a8e - linos/fep - Codeberg.org
Pull Request: #430 - WIP: Initial Draft of FEP-8a8e: A common approach to using the Event object type - fediverse/fep - Codeberg.org

See it as a proposal, I would be happy to hear some feedback here before removing the WIP flag on the pull request.

It has a few notes of things I am not sure of. Also I have to re-evaluate all MUSTs and SHOULDs cause I got lost a bit in the writing process.

About Duck-Typing vs Multi-Typing (introducing a new attribute vs adding a second type), we already had a small discussion: André Menrath: "Are there any Fediverse applications that have pr…" - graz.social

2 Likes