Versions Compared

Old Version 4

changes.mady.by.user Keith Hazelton (wisc.edu)

Saved on

compared with

New Version Current

changes.mady.by.user Keith Hazelton (wisc.edu)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Excerpt

Standards and guidelines that apply to all TIER Messages


Another Category
CategoryDescription of guideline/standardConstraints/exceptionsSupporting work/issues/resources
Message PayloadMust be a resolvable reference to a representation of the current state of the resource or the resource representation itself  
Message PayloadThe 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  
  

Schema

Info

(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		  
    
...