[Atp] One spec vs a family of related specs?

[Johannes Ernst <[e-mail]>]

AtProto currently consists of several components that arguably each could have their own spec. PHB mentioned that wrt the identity component, but there are others (e.g. XRPC, probably more).

Is the plan here to create a “spec monolith” that reflects AtProto as-is or a family of pluggable “spec microservices” (to badly mangle an analogy :-) but you get my drift).

This question matters in light of:

* the potential applicability of components of what today is AtProto for other application domains (e.g. did:plc is already being used independently of the rest of AtProto)
* easier extension — e.g. the work Bluesky is currently already doing internally about supporting non-public data, once ready, would either need to lead to a new rev of a potential AtProto spec, or be “just another” additional, optional spec component.

There are obviously arguments pro and con.

Cheers,




Johannes.



Johannes Ernst

Fediforum <https://fediforum.org/>
Dazzle Labs <https://dazzlelabs.net/>