| Category | Description of guideline/standard | Constraints/exceptions | Supporting work/issues/resources |
|---|
| Message Payload | Must be a resolvable reference to a resource representation or the representation itself | | |
| Message Payload | A resolved representation of a given resource must be the same whether via Messaging or via API | | |
| | Explicitly declare supported guarantees for use as needed: One-time delivery; At least one-time delivery; Order preserved; | | |
| | Standard metadata with each message | | |
| | Are messages where the payload is the current resource state enough to support all institutional processes? I.e. Do we need process-specific, process-identified events? C.f. "Identity Events" | | |
| | | | |
| ... | | | |