Versions Compared

Key

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

...

Requirements NameWho proposed the requirementDescriptionWho needs/will need the functionalityStakeholders affected by requirementor to be consulted
Provide schema per partes
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

Ability do dynamically update schemas in a running schema service without downtime. Changes to the schema are persisted "forever" (assuming even after redeploy)

?

.


  1. According to CT Paterson this functionality would be appreciated by an unknown Amdocs customer
  2. According to William Reehil this step is a preparation for "SDC model → A&AI target architecture"
?
SDC schema importAbility to import SDC TOSCA/CSAR schemas??

...