This is the common abstract base class for all global Biml project metadata items.
Metadata instance objects include all of the metadata specifications for a given metadata model. Note that there may be many metadata instance objects for each metadata model. The metadata model specifies the structure and rules for a collection of metadata. The metadata instance specifies the actual metadata within that model.
Metadata item column objects are used to create references to columns for that are primarily used by entity mappings.
Metadata items specify all metadata properties, relationships, and column mappings for a given item or row within a a metadata model entity. Using a relational database analogy, if the metadata model entities were tables, metadata instance items would be the rows that populate those tables.
Metadata item entity objects are used to store actual metadata information associated with a referenced metadata model entity.
Metadata item property objects are used to specify the actual property value metadata used within a metadata model.
Metadata item relationship objects are used to specify the item or row within the related entity from the metadata model that satisifes the relationship constraint for the parent metadata item.
Metadata model entities specify all of the information needed to track an individual entity within the model. Using a relational database analogy, each entity would correspond to a table, while relationships correspond to foreign keys and properties and mappings correspond to table columns.
Entity relationships define the relationships that exist between the parent entity and other entities within the model. Using a relational database analogy, if the metadata model entities were tables, relationships would be foreign keys that relate those tables.
A metadata model defines all configuration necessary for an end-user to specify and validate metadata that will be used by downstream BimlScripts to automatically generate assets.
Permitted value objects provide name/value mappings for allowed input values for metadata model properties.
Properties add configuration values to various objects within the metadata model.
Permitted value set objects provide a collection of permitted values to be used to constrain the allowable inputs for a metadata model property.
Filtered lookup items are used by the editor UI to provide completion lists. Each filtered lookup item will provide configuration information for a completion list. These completion lists can reference each other. For example, a column relationship may provide fields for connection, object, and column. In this case, the object lookup completion list would only contain objects in the selected connection. Similarly, the column lookup completion list would only provide columns in the selected table.
Lookup items are an abstract base class provided for backwards compatibility as additional types of filtered lookups are added in the future.
This is the class that is used as the basis for all validator rules that can be specified on a metadata model or any of its components.
The AstOfflineSchemaColumnNode class defines the type metadata information for an individual column within an offline schema.
The AstOfflineSchemaItemNode stores all information necessary to build a package that targets a specific table or query without having to inspect the schema information for the live table or query at build time. It is essentially a cache of column type information for a table or query result set.
The AstOfflineSchemaNode stores all information necessary to build a package that targets a specific data source without having to connect to the data source at build time. It is essentially a cache of offline schema items, each containing column type information for a table or query result set.