Documenting event-driven payloads is necessary to promote healthy consumption.
ReadMe · Developer-friendly API documentation
ReadMe helps you create beautiful, interactive API documentation that developers love.
ReadMe · Developer-friendly API documentation
ReadMe helps you create beautiful, interactive API documentation that developers love.
ReadMe · Developer-friendly API documentation
ReadMe helps you create beautiful, interactive API documentation that developers love.
ReadMe · Developer-friendly API documentation
ReadMe helps you create beautiful, interactive API documentation that developers love.
ReadMe · Developer-friendly API documentation
ReadMe helps you create beautiful, interactive API documentation that developers love.
ReadMe · Developer-friendly API documentation
ReadMe helps you create beautiful, interactive API documentation that developers love.
ReadMe · Developer-friendly API documentation
ReadMe helps you create beautiful, interactive API documentation that developers love.
Generating event descriptions under syntactic and semantic constraints
With the goal of supporting scalable lexical semantic annotation, analysis, and theorizing, we conduct a comprehensive evaluation of different methods for generating event descriptions under both synt
How Documentation Affects API Quality
If quality depends on consumers' perception, how can API documentation influence it?
The Many Meanings of Event-Driven Architecture • Martin Fowler • GOTO 2017
ATProto's Application Primacy
The amount of chatter from ATmosphere developers around an “everything app” has me thinking of an article from almost exactly 10 years ago. Back in 2016, Joel Monegro at USV wrote about “fat protocols
standard.site/lexicons
Shared lexicon schemas for long-form publishing on AT Protocol. Uses typescript to json via prototypey.
Introducing the Elicit API - Elicit
Search our 138M+ papers and generate Reports using our API.
Recurring Events
We’re about to start building recurring events for Roundabout, but before we do, I’d love to tap into the collective wisdom of the atproto community. Our existing events are stored as community.lexicon.calendar.event records. Those records don’t capture necessary information about event recurrence, so we’ll need to either extend the lexicon or use sidecar records. The data that we want to store is relatively complex. RFC 5545 is comprehensive on what recurrence rules we might want to support[1...
