Excerpt |
---|
Standards and guidelines that apply to all TIER Messages |
Category | Description of guideline/standard | Constraints/exceptions | Supporting work/issues/resources | ||
---|---|---|---|---|---|
{First Section} | |||||
Schema
| Relationship of TIER schema with SCIM-defined schema, RFC7643 |
| |||
Message Payload | Must be a resolvable reference to a representation of the current state of the resource representation or the resource representation itself | ||||
Message Payload | A resolved The representation of a given resource must be the same whether obtained via Messaging or via API | ||||
Explicitly declare supported guarantees for use as needed: One-time delivery; At least one-time delivery; Order preserved; | |||||
Standard Provide 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} | |||||
... |