Policy Decision

CLASS OF INDIVIDUAL - Policy Decision

Description

Abstract Concept

A Policy Decision is a Decision that defines the applicability status of a Policy to a set of Functional Assets.

Example:

A Policy Decision on the applicability of the RGPD regulation to specific enterprise data assets can have the result: Applicable or Non applicable.

Functional Domain: Resolution & Decision

The Resolution & Decision domain defines constructs used by stakeholders to assess and qualify Functional Assets.

Super Types

Decision

Dictionary

SysFEAT System Operating Framework

Lexical Scope

Governing Team

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
Applicability Domain	[*..0]	Functional Asset	Policy Decision	The set of Functional Assets which are subject of the Policy Decision.
Concerned Policy	[1..1]	Policy	Policy Decision	The Policy which applicability is the subject of the Policy Decision.
Selected Policy Option	[1..1]	Policy applicability Status	Policy Decision
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: 732799d364364423.agda

File: 732799d364364423.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.