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 ð
Mar 24, 2026 at 10:16 AM
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
Lexicon Garden - ATProtocol Lexicon Browser
Browse and discover ATProtocol lexicon schema definitions
fieldwork
A workshop for community schema curation on atproto. Compose dialects, vocabularies, communities, recommendations, and lens uploads against the dev.idiolect.* lexicon family.
Why Don't We Just Do This Together? - AT Protocol
Jim sits down with members of the core team building and governing Standard.site, the shared Lexicon for publishing longform writing on atproto. Brooke from pckt.blog, Jared from Leaflet, and Miguel from Offprint cover the design tradeoffs in creating a new shared format, tales of data migrations, strategies for shared governance, and why you shouldn't buy a premium domain name.
atproto made simple: publishing lexicons - underreacted
atproto made simple: publishing lexicons - underreacted
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
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?
My "Introduction to #ATProto" blog post that I've been working on for some time is ready ð It goes through things like records, lexicons, DIDs, then PDS/AppView etc. and how it all works together. Let me know if anything is wrong! More parts later, with the Fedi comparisons & misconceptions etc.
Introduction to AT Protocol
mackuba.euYep. 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 ð
@danabra.mov do you think it makes sense to frame atproto as providing a data and identity layer to the web, or as aiming to improve the web? I never want to overstep (see crypto claiming web3) but atproto is extremely web-brained like you said, and the web is where a lot of the utility shines
