>Currently it's hard to read, there is no single document. No single source of truth.
We can make it happen.
I am currently working on this: https://codeberg.org/ap-next/ap-next/src/branch/main/guide.md. It's a guide for developers, but in the future it may be used as a base for a more formal specification.
julian@activitypub.space 2 weeks ago
Hmm, how do you reconcile the fact that not all FEPs are applicable to all application types?
For example soft deletion is preferable but not required...
silverpill@mitra.social 2 weeks ago
By separating core protocol requirements and optional features.
The guide has a section titled "Protocol features":
https://codeberg.org/ap-next/ap-next/src/commit/f1ee497085f56cde9860b9417eba8cd05cd1522a/guide.md#protocol-features
This is a place where information about optional features is collected, and soft deletion FEP could be mentioned there. A formal specification could be structured in a similar way.
Cooper8@feddit.online 2 weeks ago
You could include “either x or y or z…” specifications in the unified documentation.
So “Either soft deletion is to be disabled as by default in which case [explain standard behavior], or it is to be enabled by [yadda yadda]…”
The single document is searchable and cross-referenced internally, making it better in many cases.