<font color="#29313b">Figure As.01a – Root Entity Instances and Associations shows an Object diagram that contains all the examples of RootEntityType instances described to this point.</font><br/><font color="#29313b">Note that in the figure, the Customer instance is an explicit subclass of PartyRole, but the instance of this association is not shown in the figure. Also, this model can support the dynamic addition of entities and subclasses not contained in the SID model. Examples of this are not shown in the figure either.</font><br/><font color="#29313b">The meta-model is only part of the solution to support dynamic extensibility.  Application functionality, including user interfaces, must also be developed. A representative set of insights into functionality, excluding user interfaces, will be described next.</font><br/><font color="#29313b">When creating/updating an instance of an EntitySpecification in a database, such as a CompoundResourceSpecAtomic, the application can ask if it is to be dynamically extended. If the answer is yes, an instance of RootEntityType is created. Once the extensions have been created/updated, then the value of the attribute “dynamicAttrAssoc” can be set to indicate whether attributes or associations or both have been added. The database for the meta-model, including implementation considerations for it, will be shown later after all meta-modeling concepts have been described.</font><br/><font color="#29313b">When adding an instance of a specification, the application could ask if a corresponding entity should be created. Adding the corresponding entity will enable the creation of dynamic associations between the entity and other entities. This follows from the fact that an association between specifications is often mirrored for the entities described by the specification. This will also assist the application to automatically create instances of RootEntity, which may participate in instances of the associations.</font><br/>