Versions Compared

Key

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

...

  1. AAI should support the ability to centrally persist and serve schema
  2. AAI should support the ability to centrally persist and serve custom queries
  3. AAI should support the ability to provide schema documents via a loosely coupled REST contract
  4. AAI should support the ability to provide the schema via flexible document formats (OXM, TOSCA etc.)
  5. AAI should support the ability to provide a complete schema as one document even if persisted via multiple files
  6. AAI should support the ability to provide a list of documents stored
  7. AAI should support the ability to provide an individual document
  8. AAI should support the ability to provide associations between documents (eg. an OXM and Edgerules)
  9. AAI should continue to support clients that consume the schema via XSDs and POJOs
  10. AAI should support the ability to consume new schema dynamically, without downtime (eg. when distributed by SDC)
  11. AAI should support the ability to notify consumers of schema when new updates are available
  12. AAI should support an interface to validate proposed schema changes

Scope for Dublin:

#10 and #11 need more analysis of use cases. #12 seems to align better with the GraphGraph proposal for viewing and interfacing with the schema.

Delivering #1 - #9 in Dublin will enables us to move in that direction.

...