Interaction types
A type describes a kind of work an agent can handle through email. It defines the actions available, the information they need and what each result means.
Start with the work your service asks someone to do. Each entry links to its definition, examples and review history in the Registry.
1 draft, 2 proposals, and 2 reuse assessmentsContent Review
Request changes or approve a specific revision of content.
ExampleReview a campaign draft
Operations in the draft- Request changes
- Approve
Event Response
Tell an organiser whether an invitee expects to attend.
ExampleRespond to a workshop invitation
Proposed operations- Accept
- Decline
- Respond tentatively
Information Request
Supply specified information in response to a service’s request.
ExampleConfirm a company’s contact details
Proposed operations- Submit response
- Decline
Subscription Preferences
Choose which emails a service sends and how often.
ExampleSwitch to a weekly digest
Proposed operations- Update preferences
Task Assignment
Accept assigned work and report its progress or completion.
ExampleCheck links in a documentation release
Proposed operations- Accept or decline
- Report progress
- Report completion
Drafts are open for review. Proposals describe work still being scoped. Reuse assessments start with existing standards and ask whether a MAP binding is needed.
Using a type
Start with the Registry. Read the definition and examples, check the version, and identify which operations your service or client will support. The execution profile supplies the rules for exchanging requests and results.
Browse the RegistryProposing a type
A new type should describe an interaction that more than one service could use. Check whether an existing type or standard covers the work, then document any additional behaviour your proposal needs.
Prepare a type proposal