Standards and guidelines that apply to all Messages


CategoryDescription of guideline/standardConstraints/exceptionsSupporting work/issues/resources
{First Section} 

Schema

(Example row from API Stds & Guidelines)

Relationship of TIER schema with SCIM-defined schema, RFC7643
  1. Each schema element used in TIER will be defined within a TIER schema.
  2. Any element defined in SCIM that would be useful as is in TIER will have a TIER equivalent element with an identical definition.
  3. Elements not defined in SCIM will be newly defined in the TIER schema specifications.

On making schema compliant and extensible, see:

https://spaces.at.internet2.edu/display/DSAWG/Ignoring+Unrecognized+
Schema+Fragments+in+a+Received+Resource+Representation

Message PayloadMust be a resolvable reference to a resource representation or the representation itself  
Message PayloadA 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} 
...