THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
Schema typically have a hierarchical structure. Figure 5 provides for a structure of nested Schema Elements. These structures are further specialized later on this page for specific types of Asset.
Figure 5: Nested structures in metadata representations of schema |
...
Linked Schema Elements
Figure 5: Links between schema elements from different hierarchies |
...
Map Schema Elements
Figure 6 7 adds support for a map structure in a schema.
Figure 67: Maps in schema |
Derived Schema Elements
Derived Attributes (such as in relational views) are defined in figure 78.
Figure 78: Schema element for virtual resources |
...
The next series of figures show specialized entities for different shapes of data that inherit from the Schema Element structures. They do not add attributes of new relationships, but change the entity type to make it easier for programs processing the metadata because the type name is more specific.
...
Tabular Schema
Figure 8 9 shows the the structure of a single table. This could be a file that is organized into columns.
Figure 89: Schema for tabular data |
...
Document Schema
Figure 9 10 shows the definitions for structured documents such as JSON or XML.
Figure 910: Schema for structured documents |
...
Object Schema
Figure 10 11 describes an object schema - such as the structure for a series of POJO Java objects.
Figure 1011: Schema for object structures |
...
Graph Schema
Figure 11 12 describes the schema for a property graph.
Figure 1112: Structures for property graphs |
...
Relational Schema
Figure 12 13 describes the parts of a relational schema. These are used in relational databases. There are multiple tables and views defined within the relational schema. The columns are within both the tables and views.
Figure 1213: Parts of a relational schema |
...
Events are simple linear structures. They typically are defined in sets of related events. Figure 13 14 shows the parts of an event schema.
Figure 1314: Schema for a collection of events |
...
APIs exchange data structures and commands. The schema of the API is its interface definition. It is an access point for data and so it is important to understand and control what data is passing over an API. Figure 14 15 shows the structure of an API schema. The top level schema for the API lists the operations. Under that, each operation defines its requests and responses.
Figure 1415: The structure of an API |
...
Models are used during the development of schema and their related software to provide templates and abstractions of the implementation. We add representations of models the the metadata repository to help organize and explain data assets - particularly when they are complex, or the schema is not available.
Figure 15 16 shows the definition of a model element ad its relationship to the part of the IT landscape that it describes. This is the base for many different types of models. Currently we only have solution blueprints defined. Their models follow on later on this page.
Figure 1516: Base for model elements |
...
Solution blueprints are models of an IT deployment. They show the way different processes and assets are used in combinations to deliver a solution.
Figure 16 17 shows the root definition of a solution blueprint.
Figure 1617: Solution Blueprints |
Figure 17 18 covers the wiring of the blueprint
Figure 1718: Data and control wiring in the solution blueprint |
...