Data Dictionary

BUILDING BLOCK - Data Dictionary

Description

Abstract Concept

A Data Dictionary is a dictionary of Data Blocks used to describe a data architecture. This includes:

1. Data Domains,

2. Data Entity(ies),

3. Data Property(ies).

Concrete implementations are Logical Data Dictionary(ies), Relational Dictionary(ies), NoSQL Dictionary(ies).

Functional Domain: EA Pattern - Data Domain

The EA Pattern - Data Domain comprises abstract concepts used to describe the logical and physical structure of Information Assets.

Super Types

Information Dictionary

Dictionary

SysFEAT Enterprise concepts

RELATIONSHIPS

Simple Graph Graph & Inheritance Table

Simple Graph

Composition: ➝ Classification: ➝ Specialization: ➝ Instance Of: --> Enumerated definition: ➝ Syntax: ➝

Graph & Hierarchy

Composition: ➝ Classification: ➝ Specialization: ➝ Instance Of: --> Enumerated definition: ➝ Syntax: ➝

Relationship Table

Relationship	Cardinality	Target Entity	Source Entity	Description
Packaged Data Asset	[*..0]	Data Block	Data Dictionary	Abstract Relationship
Imported Information Dictionary	[*..0]	Information Dictionary	Information Dictionary	Abstract Relationship The Imported Information Dictionary relationship extends the Information Lexical Scope of an Information Dictionary to Information Blocks of the imported Information Dictionary.
Parent Model Package	[1..1]	Model Package	Model Package	Abstract Relationship Existential Dependency that asserts the existence of a Model Package in a parent Model Package.
Holonymy Relation	[*..0]	First Order Entity	First Order Entity	Abstract Relationship Holonymy Relation is a directional whole-to-part Relation (often called Composition) between First Order Entitys, where the source First Order Entity (the whole) incorporates the target First Order Entity as one of its constituent parts.In accordance with principles of Compositionality, Holonymy Relation is not simply the inverse of Meronymy Relation. In many cases, the target part is an independant First Order Entity which exists conceptually and often physically without requiring knowledge of, or containing an inherent reference to, its parent whole.The embedding of a part within its whole involves a form of nesting (see Nesting Relation and Aggregate Block). It is important to note, however, that nesting does not inherently imply holonymy.Example:
Meronymy Relation	[*..0]	First Order Entity	First Order Entity	Abstract Relationship Meronymy Relation is a directional part-to-whole Meronymy Relation between First Order Entitys, where the source First Order Entity (the part) is defined has being part of a larger whole First Order Entity.In accordance with principles of Compositionality, Meronymy Relation is not simply the inverse of Holonymy Relation. In some cases, the whole First Order Entity is not inherently defined by some its parts. Location (Located at) and period relationships are such Meronymy Relations.Example:- William Shakespeare is born in Stratford-upon-Avon, but the Stratford-upon-Avon geo-location is not inherently defined by William Shakespeare. It is defined by its geophysical containers: Continent-Europe, Landmass-Great Britain.- William Shakespeare is born in 1564, but the year 1564 is not inherently defined by the birth of William Shakespeare. It is defined by its position in the Gregorian calendar and contains countless other global events.

LOGICAL FORMULATION

LOGIC-AGDA RDF

File: 67d376e36aa45056.agda

File: 67d376e36aa45056.rdf

SEMANTIC TAXONOMY

Sub-Types Super-Types

SUB-TYPES

Click node rectangle to collapse/expand one level. Click triangle for full recursive collapse/expand. Double-click on a node to open its URL. Hover for description.