...
- As a developer of the CCVPN Use Case in ONAP, I would like to use an API to dynamically change the AAI schema to support all the new data and relationships as needed. It would be nicer to use an API to dynamically update the schema, rather than using a static configuration file.
Glossary
Description | OXM terminology | XSD terminology | Java terminology |
---|---|---|---|
"schema element" "java-type" "class" | "java-type" XML tag | "xs:element" XML tag as outer container | Java class |
"attribute" "java-attribute" | "xml-element" XML tag inside "java-attributes" XML tag
| "xs:element" XML tag as inner container
| Java field/member variable |
"relationship" | "xml-element" XML tag inside "java-attributes" XML tag
| "xs:element" XML tag as inner container
| Java field/member variable |
"metadata" "xml-property" | "xml-property" XML tag inside "xml-properties" XML tag | "xs:annotation" XML tag containing "annox:annotate" metadata | N/A. There are various hard-coded behaviours for each individual item of metadata. |
"namespace" | special "java-type" that
| "xs:element" XML tag as outer container
| N/A. There is special hard-coded behaviour for a specific set of "namespaces". |
"top-level" | a "relationship" of a "namespace" | N/A. There is special hard-coded behaviour that prevents "top-level" classes from also being used as "sub-components". | |
"sub-component" | a "relationship" of a "java-type" that is not a "namespace" | N/A. There is special hard-coded behaviour that prevents "top-level" classes from also being used as "sub-components". | |
"EdgeRule" | a separate JSON configuration file that regulates the behaviour of the "relationship" | N/A. There is special hard-coded behaviours for each individual item of metadata. | |
"cousin edge" |
| N/A. There is special hard-coded behaviour that handles the "relationship-list" for "cousin edges". |
...