Why email
Reviews, requests and decisions already arrive in the inbox. A message often contains the context an agent needs, but each service describes the next step in its own way.
MailSchema provides a place to define those interactions together. The aim is for a service to describe an action in a form that different agents and inboxes can understand.
The project
Mail Action Protocol defines the common exchange between service and client. Interaction types describe particular kinds of work. The Registry collects submitted definitions and their history.
Services retain their own permissions and business operations. People can continue to read the email and use the service directly.
Current work
MAP 0.1 is a working draft. Content Review is the first type under development, with a browser example showing feedback, revisions and approval. The request format and compatibility tests are still being specified.
The type collection currently includes:
- Draft: Content Review
- Proposal: Information Request, Subscription Preferences
- Reuse assessment: Event Response, Task Assignment
Existing standards
MailSchema should adopt existing formats and protocols where they fit. Each type proposal identifies related work and explains what it adds. Theinteroperability chapter records the specifications under consideration.