stansite is not like other lexicons, they’re distribution/discovery lexicons, not content lexicons. they have canonical locations on the web hence why we even care if a document or publication is verified keep treating them as the data and people will stop using them …and atproto loses imo
Jul 26, 2026 at 10:25 PM
Standard.site: the Publishing Gateway
Another deep exploration into ATProto and implementing lexicons
Standard.site: the Publishing Gateway
Another deep exploration into ATProto and implementing lexicons
atproto made simple: publishing lexicons - underreacted
atproto made simple: publishing lexicons - underreacted
Lex make a registry - Sri's leaflets
Introducing lexicon.store - an unconventional ATProto Lexicon Registry
ATProto Standards Bodies | Sam Clemente | Offprint
How do we go about maintaining lexicons across apps?
Lexicon Embeds Overview
ATProto’s inside out structure provides an opportunity for open, permissionless building on top of any component in the network, including its extensible data schema definition system, Lexicons. One of the opportunities this presents is users sharing their data and records with multiple apps. Those apps may be direct substitutions (different clients for microblogging say), or apps that use that data in a variety of ways, such as Popfeed an app which aggregates posts about a variety of media ty...
Lexicon Store - ATProto Lexicon Schema Registry
Discover and explore AT Protocol lexicon schemas. The verified registry for Bluesky and ATProto lexicons.
Publishing ATProto Lexicons - Nick the Sick's blog. Writings, projects and ideas.
Publishing ATProto Lexicons - Nick the Sick's blog. Writings, projects and ideas.
This is partly why I think atproto needs a more convincing vision about being a post-app protocol. A future where atproto is a bunch of apps and each app governs their own lexicon diminishes a lot of its potential in the long-term.
Laurens
yeah i think i might actually, theres a very interesting story here that the main thing that matters is a focal point around which consensus over a lexicon can get formed
Yep. This is what is missing in the ATProto vision. The lexicons should've been a like schema.org instead of domain name-based. Everyone who wants to improve it can discuss it, similar to, well, schema.org. The frontend must be separate from the content. It's beneficial in many ways.
jack
we have standard.site but wen standard.pics? rn I’m juggling between @grain.social, @flashes.blue & @sprk.so for image sharing 😭
The reason I've become such a @standard.site stan is because it's forming into the first real multi-service parallel ecosystem on atproto that can survive on it's own without the need of the @bsky.app lexicons and infra
I have a gut feeling that, despite both being open web schema systems, semantic-web and atproto-lexicons are deeply divergent. I quite like both techs and don't mean to suggest this is a problem, just want to provide my guess at this question: it won't!
Tynan Purdy ⁂
When will schema.org create org.schema lexicons?
