...
| Section | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
- AAI-CCVPN Schema Proposal for Casablanca Release
- AAI-BBS Proposals for Dublin Release /
Jira server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb key AAI-2154
Principles
tbc
Discussion
From BBS use case
In general, first option is written as "add <new attribute> to <class>".
- First justification for this action is that the <new attribute> is more generally applicable to other uses, not just this one case.
- Second justification is that it will be used in high percentage of cases (not left empty) and have additional properties such as being mandatory.
- Third justification is that there will be core code written that depends on this attribute, so it should be a core part of the schema
- Fourth justification is that the exact nature and number of <new attributes> is well-known, so it will not require frequent schema changes to adjust to the conditions.
In general, the second option is written as "add Metadata sub-object then configure <new attribute> Metadatum entry".
- First justification for this action is that the <new attribute> is more specifically applicable to this one case only.
- Second justification is that it will be left empty in high percentage of cases, i.e. not mandatory.
- Third justification is that there will be none of the core code depends on this attribute, but the information needs to be conveyed somehow
- Fourth justification is that the exact nature and number of <new attributes> is variable or unbounded, so this avoids frequent schema changes to adjust to the conditions.
In general, the third option is written as "configure <new attribute> Metadatum entry linked from service-instance into relationship-list".
- First justification for this action is that schema change is to be avoided as much as possible.
- Second justification is that the <new attribute> is more specifically applicable to this one case only
- Third justification is that it will be shared/linked/referred from several other objects via the relationship-list
- Fourth justification is that there will be none of the core code depends on this attribute, but the information needs to be conveyed somehow
- Fifth justification is that the exact nature and number of <new attributes> is variable or unbounded.
Attachments
| Attachments | ||
|---|---|---|
|
...