| Requirements Name | Who proposed the requirement | Description | Who needs/will need the functionality | Stakeholders affected by requirement |
|---|---|---|---|---|
| Provide schema per partes | William Reehil/AT&T | For example, say Sparky just needs to know the attributes of the x node, it should not have to load the entire configuration file in XML format to find out that information. Ideally it should just be able to ask the schema service "What are the attributes of the x node in JSON format?" | ? | ? |
| Schema modifications hub | Then taking this a step further we would like to leverage this service to act as the central hub of schema modifications | ? | ? | |
| Adding schemas at runtime | ability to consume new schema dynamically, without downtime | ? | ? | |
| Interface support | interface to validate proposed schema changes | ? | ? | |
| Input format support | ability to provide the schema via flexible document formats (OXM, TOSCA etc.) | ? | ? | |
| Dynamic schema updates | CT Paterson /Amdocs | Ability do dynamically update schemas in a running schema service without downtime. Changes to the schema are persisted "forever" (assuming even after redeploy) | ? | ? |
| SDC schema import | Ability to import SDC TOSCA/CSAR schemas | ? | ? |
General
Content
Integrations