...
Chesla Wechsler to take action item to write up schemaless behavior need which would accommodate service-level properties which are not global (i.e., do not belong in the STANDARD COMMON definition of service-instance) but which still need to be stored on certain service-instance to which they apply. Chesla will talk to AAI PTL about this, as this is a feature that would be needed on AAI.
Schemaless behavior (note, I haven't spoken to the AAI PTL yet):
The internal service model global type has properties and attributes which are common to all service-instances. This is likely a very small set. When a node type extends the service global type, it adds properties and attributes specific to that particular service model (like your portal url, slice characteristcs, etc.).
AAI has an interface that permits payloads (that have the specific properties and not just the common ones in the base object).
AAI stores all the data in the payload and returns it when queried.
The common fields can be indexed. Model specific ones would not have an index at first unless they is also an AAI feature to ask for an index on it or there is a way to specify it in the model.
Today, AAI expects the fields in its payloads to be defined by an OXM file, and the relationships between vertexed defined in an edge rules file. It uses a "superset of all possibilities" approach which I think should evolve to an InternalXModel approach where the specific InternalModel, which has properties and attributes, defines the fields of the instance. Alternatively, there would need to be instances modeled at the same time as the design time objects and mapping ensues.
People I'm expecting to participate in this conversation are as follows:
...