Excerpt |
---|
Standards and guidelines that apply to all TIER Messages |
Category | Description of guideline/standard | Constraints/exceptions | Supporting work/issues/resources | \{First Section\}|||
---|---|---|---|---|---|---|
Message Payload | Must be a resolvable reference to a representation of the current state of the resource or the resource representation itself | Schema
| ||||
Message Payload | 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; | ||||||
Provide standard metadata with each message | ||||||
Relationship of TIER schema with SCIM-defined schema, RFC7643 |
| On making schema compliant and extensible, see: https://spaces.at.internet2.edu/display/DSAWG/Ignoring+Unrecognized+Schema+Fragments+in+a+Received+Resource+Representation | ||||
\{Another Section\} | ||||||
... |