SysFEAT - Systemic Framework for Enterprise Architecture & Transformation

CLASS OF CONNECTION - Temporal Bounding

Description

Abstract Concept

A Temporal Bounding is an Individual whose temporal extent is instantaneous, and whose spatial extent corresponds with the start or end of the Bounded Individuals for which it is the temporal border.

Example:

. The Eiffel tower completion (31st March 1889)

. William Shakespeare birth (1564)

. Confucius death (758).

. Start of the first Plinian phase of the Mount Vesuvius eruption (18h, Aug. 24 A.D. 79)

. Oakland hospital opening in 1994.

Functional Domain: 4D Composite Knowledge Graph

The purpose of the 4D Composite Knowledge Graph is to layer structured spatio-temporal concepts onto the Reflexive Knowledge Graph,

Super Types

Concrete Entity

Individual (from partition: Structural Partition of Individual)

Ordering Connection

Power Type

Temporal Bounding Type

Dictionary

SysFEAT Upper Ontology

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
PowerTyped by Temporal Bounding Type	[1..1]	Temporal Bounding Type	Temporal Bounding
Start	[*..0]	Bounded Individual	Temporal Bounding	Abstract Relationship
End	[*..0]	Bounded Individual	Temporal Bounding	Abstract Relationship
Connection End	[*..0]	Bounded Aggregate	Ordering Connection	Abstract Relationship
Connection Member	[*..0]	Ordering Connection	Ordering Connection
Hierarchical Member	[*..0]	Building Block	Aggregate Block	A Hierarchical Member is an Aggregate Member that is also a Block Lexical Scope for the Building Block it aggregates: it relates its aggregated block by nesting (see Nesting Relationship).Hierarchical Members are used to build hierarchical structures of Building Blocks, in constrast to Block Members which are used to build network structures of Building Blocks.
Block Member	[*..0]	Building Block	Aggregate Block	A Block Member is an Aggregate Member that aggregates its releated Building Block by reference (see Referencing Relationship).Block Members are used to build network structures of Building Blocks while Hierarchical Members are used to build hierarchical structures of Building Blocks.
Meronymy (Part Of)	[*..0]	Particular Entity	Particular Entity	Abstract Relationship Meronymy (Part Of) is a directional part-to-whole Relationship between Particular Entitys, where the source Particular Entity (the part) is defined has being part of a larger whole Particular Entity.In accordance with principles of Compositionality, Meronymy (Part Of) is not simply the inverse of Holonymy. In some cases, the whole Particular Entity is not inherently defined by some its parts. Location (Located at) and period relationships are such Meronymy (Part Of).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.
Holonymy	[*..0]	Particular Entity	Particular Entity	Abstract Relationship Holonymy is a directional whole-to-part Relationship (often called Composition) between Particular Entitys, where the source Particular Entity (the whole) incorporates the target Particular Entity as one of its constituent parts.In accordance with principles of Compositionality, Holonymy is not simply the inverse of Meronymy (Part Of). In many cases, the target part is an independant Particular 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 Relationship and Aggregate Block). It is important to note, however, that nesting does not inherently imply composition.Example:
Existential Dependency	[1..1]	Entity	Entity	Abstract Relationship An Existential Dependency relationship is a Relationship where the source Entitys existence depends on the existence of the target Entity.The cardinality of the set of targetted Entity is [1..1].

SERIALIZATION FORMAT

TEXTUAL SYNTAX RDF

File: 267b6a126675a0b9.rdf

CONNECTION DIAGRAM

../images/267b6a126675a0b9_ab8f258367532776_i.png

CONNECTION ENDS

	Name	Type	Super Type	Description
Source End	Start	Bounded Individual	Ordering Connection::Source Connection End
Target End	End	Bounded Individual	Ordering Connection::Target Connection End

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.

CLASS OF CONNECTION - Temporal Bounding

RELATIONSHIPS

Simple Graph

Graph & Hierarchy

Relationship Table

SERIALIZATION FORMAT

CONNECTION DIAGRAM

CONNECTION ENDS

SEMANTIC TAXONOMY

SUB-TYPES

SUPER-TYPES

CHARTER

Missing Content

Governance

Provide Feedback