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!
Alana Purdy’s Husband ⁂
When will schema.org create org.schema lexicons?
Aug 28, 2026 at 2:55 PM
Lexicon Garden - ATProtocol Lexicon Browser
Browse and discover ATProtocol lexicon schema definitions
Lexicon Store - ATProto Lexicon Schema Registry
Discover and explore AT Protocol lexicon schemas. The verified registry for Bluesky and ATProto lexicons.
atproto made simple: publishing lexicons - underreacted
i find some atproto documentation extremely confusing. the section about publishing lexicons is one of those parts that makes me want to tear my hair out. it…
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
Transmogrify Record - Lexicon Garden
Transform records between ATProtocol lexicon schemas
Two Types of Interoperability Without Sharing Lexicons - Wesley's notes
Sharing lexicons is not the only way to leverage atproto’s interoperability
Two Types of Interoperability Without Sharing Lexicons - Wesley's notes
Sharing lexicons is not the only way to leverage atproto’s interoperability
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 😭
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 😭
curious to hear other #atproto devs’ thoughts on fragmentation in the ecosystem? is there a thing as too much choice? many users, but all across various apps implementing their own lexicons?
There's lots I haven't yet understood about atproto, but I simply won't do the standard.site thing whilst it offers a worse UX than… not doing it.
Guido X Jansen
It keeps confusing me that the main call to action in these cards (the button) does NOT go to the article but to the main website Is it just me that finds this weird...? The main visual CTA for a card about an article should go to that article no...?
