Post

Yeah Lexicon Garden is a handy site. And/also, lexicon "self-discovery" should totally be a thing. Like I would possibly kill for a single standard endpoint on xrpc that outputted the lexicons for that site. Which brings up another standard.site idea... standard.site.service/endpoint ... ?

standard.siteStandard.site - One schema. Every platform.Standard.site provides shared lexicons for long-form publishing on AT Protocol. Making content easier to discover, index, and move across the ATmosphere.

I respectfully disagree with this viewpoint. A Lexicon is akin to an OpenAPI or JSON Schema. While we think of both of these as "developer tools", they also purposefully contain enough metadata to autogenerate UIs. People will interact with our lexicons, because programmers make it easy.

0 reposts0 likes

Autogenerated UIs sound great! And yes, good descriptions and metadata are important there. Still, UIs are a far cry from the actual JSON lexicons themselves. I wouldn't expect non-technical people to ever have to find and read OpenAPI or JSON Schemas either.

Also, asking: do we not already have this / how broad is the awareness gap? I ask because the At wrapper I wrote back in ~2023 is automatically generated from lexicons via metadata. If auto-coders are helpful, I should probably spin that functionality off. aka: autorest for lexicons?

Yeah, I think we may be hair-splitting here. I don't expect non-technical people to write JSON. I do hope that people keep usability and metadata in mind when they make a lexicon, and think if someone can use it clearly with only metadata descriptions.