...
#10 and #11 need more analysis of use cases and design. #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 directionis the first step towards supporting dynamic schema ingestion.
Proposed Design :
- A mS called Schema Service will hold and load all the schema (OXM and edge rules) at start up
- The Schema Service will hold and load the custom query document at start up
- The Schema Service will provide REST endpoints via GETs such as /aai/schema-service/{api-version}. Consumer mS, such as resource, traversal should use the updated ingest library to make REST calls to the Schema Service
- The REST endpoint for providing the schema will support a "format" query parameter which will describe what format it is requested in eg. GET /aai/schema-service/v1/nodes?version={version}&format=OXM
- The REST endpoints such as /aai/schema-service/v1/nodes?version={version} and /aai/schema-service/v1/edgerules?version={version} will provide a complete schema from multiple files
- The REST endpoint such as /aai/schema-service/v1/list will provide the list of documents stored
- The REST endpoint such as /aai/schema-service/v1/nodes?version={version}, /aai/schema-service/v1/edgerules?version={version} and /aai/schema-service/v1/stored-query will provide the individual document
- The REST endpoint will provide the associations between documents via query parameter "version"
- The schema jar will continue to be provided as an artifact for consumers of XSD and POJOs
...