Category | Description of guideline/standard | Constraints/exceptions | Supporting work/issues/resources | |
---|---|---|---|---|
{First Section} | ||||
Schema
| Relationship of TIER schema with SCIM-defined schema, RFC7643 |
| On making schema compliant and extensible, see: | |
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: One-time delivery; At least one-time delivery; Order preserved; | ||||
Standard metadata with each message | ||||
Are bare resource states enough to support all institutional processes? I.e. Do we need process-specific, process-identified events? | ||||
{Another Section} | ||||
... |