Temporal Bounding

DEFINITION RELATIONSHIPS SEMANTIC TAXONOMY INTERNAL STRUCTURE CONNECTION ENDS LOGICAL FORMULATION CONTENT MANAGEMENT

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

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	Abstract Relationship
Property of Individual	[*..0]	Property	Individual	Abstract Relationship An instance of Entity from a Bounded Individual to a Property that asserts the Bounded Individual has the Property.
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.
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 Scoped Building Block).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.Hierarchical Members are the KerML equivalent of composite features.
Block Member	[*..0]	Building Block	Aggregate Block	A Block Member is an Aggregate Member that aggregates its releated Building Block by reference (see Reference Relation).Block Members are used to build network structures of Building Blocks while Hierarchical Members are used to build hierarchical structures of Building Blocks.
Nesting Relation	[*..0]	Entity	Lexical Scope	Abstract Relationship A Nesting Relation is a Relation that references its target Entity by nesting, using a Nesting Adjacency.Nesting is a fundamental concept in complex systems organization where elements are contained within other elements, creating hierarchical or constextual web-like structures. This embedding mechanism intrinsically links the properties, behaviors, and lifecycles of nested entities to their containing entities, forming cohesive units at multiple scales.Nesting facilitates the emergence of complex Aggregate Blocks and properties from simpler entities, enables efficient design of systems across levels, and supports both autonomy and integration within systems (see Compositionality).Nesting also facilitates the creation of modules through packaging of Building Blocks (see Packaging).
Typology	[*..0]	Class of Entity	Entity	Abstract Relationship A Typology is a Relation between an Entity and its categorical nature - the intrinsic properties or criteria that determine the Entity membership within a Class of Entity. Typology governs two distinct categorization mechanisms:- instance of Entity: assigning a Ordered Entity to a predefined Class of Entity based on shared characteristics (e.g., grouping by common traits).- SubTypeOfEntity: refining a Class of Entity into a subclass with narrower criteria (e.g., inheritance hierarchies or subtype relationships).While instance of Entity focuses on grouping Ordered Entitys into Class of Entitys, SubTypeOfEntity emphasizes hierarchical refinement of Class of Entityes themselves. Both mechanisms operate under the umbrella of typology, which formalizes how Ordered Entitys are systematically categorized.
Reference Relation	[*..0]	Entity	Entity	Abstract Relationship A Reference Relation is a Relation that points at a target Entity which is not in the Lexical Scope of its source Entity.
Existential Dependency	[1..1]	Entity	Entity	Abstract Relationship An Existential Dependency relationship is a Relation where the source Entitys existence depends on the existence of the target Entity.The cardinality of the set of targetted Entity is [1..1].
Existential Independence	[*..0]	Entity	Entity	Abstract Relationship An Existential Independence relation is a Relation that specifies that the existence of the source Entity doesnt depend on the existence of its target Entity.The cardinality of set of targetted Entity is [0..*].

LOGICAL FORMULATION

LOGIC-AGDA RDF

File: 267b6a126675a0b9.agda

File: 267b6a126675a0b9.rdf

CONNECTION DIAGRAM

../images/267b6a126675a0b9_ab8f258367532776_i.png

CONNECTION ENDS

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

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.