Page History

...

1. The solution must provide the foundational layer for consuming dynamic schema changes in the future
2. AAI schema service must support the ability to centrally persist (build-time) and serve (run-time) schema via REST
3. AAI schema service must support the ability to centrally persist (build-time) and serve (run-time) custom queries via REST - removing the custom query definitions from the traversal service and making the schema service responsible for them.
4. AAI schema service must support the ability to provide a complete schema as one document even if persisted via multiple files
5. AAI schema service must support the ability to provide a list of documents stored
6. AAI schema service must support the ability to provide an individual document
7. AAI schema service must support the ability to provide associations/grouping between documents (needs more clarity)
   1. OXM and Edgerules paired by version [v11, v12, v13]
   2. Grouped by usecase w/ multiple OXM files
8. AAI schema service must continue to support clients that consume the schema via XSDs and POJOs as build-time artifacts
   1. MSO uses this, and would have to update configuration for the location
   2. Followup item: Check with SEs on who is consuming the XSDs
9. AAI schema service must start before the Client AAI microservices that depend on it
10. Client AAI microservices that currently depend on aai-common / aai-schema artifact at build time must use the AAI schema service REST API as its source for OXM schema files and edge rules 
11. Client AAI microservices must support an fallback mechanism that can be optionally triggered at microservice start-time

...