Distillation of requirements

Requirements Name	Who proposed the requirement	Description	Who needs/will need the functionality	Stakeholders affected or to be consulted
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?"	maybe Sparky?	?
Schema modifications hub	William Reehil /AT&T	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	William Reehil /AT&T	ability to consume new schema dynamically, without downtime	?	?
Interface support	William Reehil /AT&T	interface to validate proposed schema changes	?	?
Input format support	William Reehil /AT&T	ability to provide the schema via flexible document formats (OXM, TOSCA etc.)	?	?
Dynamic schema updates	CT Paterson /Amdocs William Reehil and Manisha Aggarwal /AT&T Keong Lim / Huawei	Ability do dynamically update schemas in a running schema service without downtime. Changes to the schema are persisted "forever" (assuming even after redeploy).	According to CT Paterson this functionality would be appreciated by an unknown Amdocs customer According to William Reehil this step is a preparation for "SDC model → A&AI target architecture" According to Keong Lim it would make development of CCVPN use case easier as changes can be made dynamically	?
SDC schema import	William Reehil /AT&T	Ability to import SDC TOSCA/CSAR schemas	?	Chesla Wechsler
Support non-standard schemas	CT Paterson /Amdocs	Support standard and non-standard schemas, as some customers may have different schemas altogether. In terms of usage is related to the requirements Dynamic schema updates	According to Distillation of requirements this functionality would be appreciated by an unknown Amdocs customer