RU2621185C2 - System for determination of relationship between first and second data entities - Google Patents

Abstract

FIELD: physics, computer engineering.

SUBSTANCE: invention relates to the field of information technology, namely to data structuring, access and processing systems. The technical result is achieved due to the fact that the first entity component and the second entity component are linked by another entity, and the entity connecting the first and the second entity is an index. The plurality of such indices, specific for a particular relationship between the first and the second data entities, is a type of index that is defined by a unique name in a variety of names of indices types, and always possesses instances of this type of index. The index represents the fact, the semantics of which is described by a grammatical sentence, and divided into three categories in relation to the management function: current reading, target reading, historical reading.

EFFECT: invention provides the ability to dynamically change the relationship between the entities expressed by figures, depending on the events and phenomena.

9 cl

Description

The invention relates to the field of information technology, namely to systems for structuring, access and data processing, and can be applied to design and create information systems, transmit information, develop information data warehouses and integrate heterogeneous information systems.

The prior art system for determining the relationship between the first and second data entities contains a computer processor for executing computer-executable instructions and processing data stored in memory, a memory connected to the processor that stores the components of the entity and components of the relationship, and: the first component of the entity and the second component of the entity provide the first data entity and the second data entity, each object The data entity has a unified identity on a large number of heterogeneous subject areas, and the unified identity of the data entities is supplemented by the value of the identifier of the entity, which is the basis for linking to each entity, and the relationship component explicitly determines the relationship between the first and second entities data entities, and the relation contains two sides, so that the first side represents the first data entity, and the other side represents the second data entity, wherein the first data entity is independent of the second data entity in relation, the relation allowing the first multiple in the first side and the second multiple in the second side, the first multiple having multiplicities other than the second multiple, and the first multiplicity is the first constraint indicating the first number of instances of the data entity involved in the relationship on the first side, and the second multiplicity l is a second constraint indicating a second number of instances of the data entity involved in the relationship on the second side, wherein the relationship includes operational behavior for the relationship between the first and second data entities, where the data entity includes a data entity type , and the memory, presented in the form of a machine-readable medium, contains instructions executed by the computer processor stored in it, to ensure that the computer process is implemented a litter of a method for determining the relationship between the first and second data entities, and comprising the steps of: providing a first entity and a second entity, wherein the first and second entities are aligned with the underlying data, the first and second entities entities are uniquely identifiable; identify the structure of the first entity and the second entity as properties; determine the relationship between the first and second entities; save related data (see, e.g., RU 2421798, publ. 06/20/2011).

The disadvantages of this technical solution are:

1. The absence of a strictly formalized set of relationship attributes.

2. The presence of a relationship between the first and second data entities, expressed solely by the name of the relationship.

3. The absence of a pronounced and strictly formalized dependence of the relationship on time.

4. The lack of a mechanism for clarifying the semantics of relationships.

5. The lack of a mechanism for materializing the relationship, ie binding relationships to the source of information about this relationship.

6. The presence of attributes that define the relationship between data entities in the data entities themselves associated with the relation.

7. The lack of uniform application of the relationship between data entities, ie a relation may be explicitly represented through an entity, or it may not be represented through an entity.

8. The lack of typification of relations, and as a consequence of the impossibility of creating instances of relations between data entities.

9. The lack of semantic completeness of the description of the relationship between the data entities using the attributes of the relationship and attributes associated with the relationship of the object data entities.

The tasks to which this technical solution is directed are:

1. Providing the ability to represent the indicator as the smallest composite unit of information, consisting of a strictly formalized set of attributes, from a semantic point of view, representing a logical statement with a complete meaning and essentially a “mini-document”.

2. Providing a uniform definition in the form of an indicator of both the relationship between the data entities and the characteristics of the entity expressed by the attribute and its value.

3. Providing the ability to manipulate operational, planned and historical information presented in the form of a set of indicators and data entities.

4. Providing the ability to dynamically change relationships, expressed through indicators, between entities, depending on events and phenomena.

5. Ensuring the integrated use of the concept of an indicator in the conceptualization of subject areas, the transfer of information, the design of information repositories and the integration of heterogeneous information systems.

The tasks are solved due to the fact that in the system for determining the relationship between the first and second data entities containing a computer processor for executing computer-executable instructions and processing data stored in memory, a memory connected to the processor that stores components of object entities and components relations, moreover: the first component of the entity and the second component of the entity provide the first data entity and the second data entity, each the object data entity has a unified identity on a large number of heterogeneous subject areas, while the unified identity of the data object entities is supplemented by the value of the identifier of the entity, which is the basis for linking to each entity, and the relationship component explicitly determines the relationship between the first and second object data entities, and the relation contains two sides, so that the first side represents the first entity given ny, and the second side represents the second data entity, wherein the first data entity is independent of the second data entity in relation, the relation allowing the first multiple in the first side and the second multiple in the second side, the first multiple having a different value than the second fold, and the first fold is the first constraint indicating the first number of instances of the data entity involved in the relationship on the first side, and the second cr Attitude is a second constraint indicating the second number of instances of the data entity involved in the relationship on the second side, the relationship includes operational behavior for the relationship between the first and second data entities, where the data entity includes a data entity type , and the memory, presented in the form of a machine-readable medium, contains instructions executed by the computer processor stored in it, according to the technical solution, the first and second Paradise objects are interconnected using another object, moreover, this other object connecting the first and second objects is an indicator, and many similar indicators specific to a certain relationship between the first and second data objects are an indicator type , where the type of indicator is defined by a unique name on the set of names of types of indicators, and the type of indicator always has instances of the indicator of this type, and the indicator is all Yes, it is expressed explicitly through an entity that has many attributes, and the indicator is a function of time, where time arguments are specified as a group of attributes, the composition of which is determined by the category of the indicator, and an attribute group is selected in the indicator, which determines the path according to information sections such as indicator, while the name of the indicator type is constructed in the form of a text expression that determines the operational behavior of the associated data entities, it’s convenient o for the presentation by a person, as well as in the form of a decomposition of the name of an indicator type into separate attributes, for machine processing of the name of an indicator type, and the indicator itself is a fact whose semantics are described by a grammatical sentence, and which is formed by the concatenation of the values of the indicator’s attributes, and this grammatical sentence a logical statement with a complete meaning regarding the relationship between the first object and the second object, and many indicators in relation to the management function is classified into three categories, which are: current indicator, planned indicator, historical indicator, while many types of indicators in the form of relations between the first and second data entities are divided into subsets, which are types of indicators: characteristic, interaction , association, and where the view determines the operational behavior of the indicators, and for the first and second entities, constant roles are defined in the form of attribute names , one attribute is called “subject”, where the identifier of the data entity is stored, and which acts as the subject, and another attribute is called “object”, where the identifier of the data entity is stored, and which acts as the object, and navigation is set only in the direction from the subject to the object, and where the subject represents the first side of the relationship, and the object represents the second side of the relationship, where the first ratio in the first side of the indicator always takes a value equal to 1, and the second ratio in the second side index takes a value not null or 1, the value of the multiplicity of the second side is determined depending on the type of indicator.

Each indicator of the system has a unified identity on a large number of heterogeneous subject areas, while the unified identity of the indicators is supplemented by the value of the identifier of the indicator.

The type of indicator “characteristic” is a form of relationship between the type of the data entity on the one hand of the indicator acting as the subject of the relationship and the environment on the other hand of the indicator acting as the object, and the indicator in this case is the characteristic of the subject in the environment, by which data values of a certain type are associated with the subject.

The type of the “interaction” indicator is a form of the relationship between two peer data entities on one and the other side of the indicator, where the first entity acts as a subject and the second entity acts as an object, while the indicator quantitatively or qualitatively characterizes the interaction between the subject and object.

The type of indicator “association” is a form of the relationship between two peer data entities on one and the other side of the indicator, where the first data entity acts as the subject, and the second data entity acts as the object, and the subject and object, through this indicator species, form aggregation.

The planned indicators of the system characterize the state of planning of data entities and their relationships with each other.

Current indicators of the system characterize the state at the current point in time of the data entities and their relationships with each other.

Historical indicators of the system characterize the past state of the data entities and their relationships with each other.

The path along the information sections of each type of indicator semantically clarifies the relationship between the first and second data entities.

The technical result provided by the given set of features is:

1. Providing the ability to represent the indicator as the smallest constituent unit of information, and in fact being a “mini-document”, due to the composition of the set of indicator attributes that are logically interconnected and grouped into groups, defined as the minimum necessary and sufficient for document formation, transmission, storage and perception of information ;

2. Ensuring the uniformity of the definition expressed by the indicator, both the relationship between the data entities and the definition through the indicator of the characteristics of the entity expressed by the attribute and its value, due to the constant composition of the attributes of the indicator, a certain category, type and type.

3. Providing the ability to manipulate operational, planned and historical information contained in indicators by providing the ability to select and include the indicator according to one of three categories of functional behavior: either the planned category, or the current category, or the historical category of the indicator.

4. Providing the ability to dynamically change the relationships expressed through indicators between data entities due to the presence of a group of indicator attributes whose values are time values and that allow you to directly control the dependence of the indicator on time;

5. Ensuring the comprehensive use of the method for determining the relationship between object entities in the form of an indicator: for conceptualizing subject areas, transmitting information, designing information repositories and integrating heterogeneous information systems due to the fact that the indicator is the smallest composite unit of information, which is a logical statement with complete meaning and essentially a “mini-document."

Disclosure of the invention.

The following presentation is intended to present the basic concepts of the disclosed invention using a formalized ontology description language.

The system for determining the relationship between the first and second data entities contains a computer processor for executing computer-executable instructions and processing the data stored in the memory, a memory connected to the processor that stores the components of the entities and the components of the relationship.

The terms “component” and “system” are elements that are any combination of hardware and software, as well as software among themselves.

The first component of the entity and the second component of the entity represent the first data entity and the second data entity. Each data entity has a unified identity on a large number of heterogeneous subject areas. The unified identity of data entities is supplemented by the value of the identifier of the entity, which is the basis for forming a link to each entity, and the relationship component explicitly defines the relationship between the first and second data entities.

The following illustrates the general structure of a data model in accordance with the related invention. The data model includes a Declaration entity component (Class (: ObjectiveEntity)), which provides data entities that have a unified identity on a large number of heterogeneous subject areas, and a Declaration (Class (: Indicator)) relationship component that defines the relationship between two entities data entities.

Declaration (ObjectProperty (: hasIndicator_objectId_forObjectEntity))

and

Declaration (ObjectProperty (: hasIndicator_subjecId_forObjectEntity)).

### Declaring a relationship between data entities

Declaration (Class (: Indicator))

### Declaring Entities

Declaration (Class (: ObjectiveEntity))

### Reference to the first data entity

Declaration (ObjectProperty (: hasIndicator_subjectId_forObjectEntity))

### Reference to the second data entity

Declaration (ObjectProperty (: hasIndicator_objectId_forObjectEntity))

An indicator is a component of information selected in the process of studying the properties of data objects and standardized to the necessary degree, which is a relation or attribute of a data object of interest in its interaction with other individual data objects of the environment or the environment as a whole.

Each indicator has a unified identity on a large number of heterogeneous subject areas, while the unified identity of the indicators is supplemented by the value of the indicator identifier.

### Rules defining common attributes of a relation (indicator)

Declaration (Class (: Indicator))

AnnotationAssertion (rdfs: label: Indicator "Indicator")

SubClassOf (: Indicator owl: Thing)

SubClassOf (: Indicator

ObjectIntersectionOf (ObjectAllValuesFrom (: hasIndicator_kindIndicatorId_forKindIndic ator: QualifierIndicatorKind)

ObjectSomeValuesFrom (: hasIndicator_kindIndicatorId_forKindIndicator: QualifierIndicatorKind)))

SubClassOf (: Indicator ObjectSomeValuesFrom (: hasIndicator_objectId_forObjectEntity: ObjectiveEntity))

SubClassOf (: Indicator ObjectSomeValuesFrom (: hasIndicator_sourceIInftId_forObjectEntity: ObjectiveEntity))

SubClassOf (: Indicator ObjectSomeValuesFrom (: hasIndicator_subjectId_forObjectEntity: ObjectiveEntity))

SubClassOf (: Indicator ObjectSomeValuesFrom (: hasIndicator_typeIndicatorId_forTypeIndicator: QualifierIndicatorType))

SubClassOf (: Indicator DataSomeValuesFrom (: hasCategoryIndicator xsd: string))

SubClassOf (: Indicator DataSomeValuesFrom (: hasFrequencyIndicator xsd: string))

SubClassOf (: Indicator DataSomeValuesFrom (: hasNameMeasureValueBasis xsd: string))

SubClassOf (: Indicator DataSomeValuesFrom (: hasReferenceToDocumentInformationSource xsd: string))

SubClassOf (: Indicator DataSomeValuesFrom (: hasTypeValueBasisIndicator xsd: string))

SubClassOf (: Indicator DataSomeValuesFrom (: hasWayOnInformationCuts xsd: string))

SubClassOf (: Indicator DataSomeValuesFrom (: valueIndicatorBases xsd: string))

The identifying attribute of an indicator is its name (type name):

Declaration (Class (: IndicatorGroupsByType))

AnnotationAssertion (rdfs: label: IndicatorGroupsByType "Indicators By Type")

AnnotationAssertion (rdfs: comment: IndicatorGroupsByType "set of indicators grouped under the name of type" ^∧∧ xsd: string)

SubClassOf (: IndicatorGroupsByType: IndicatorGroups).

The relationship contains two sides, so that the first side represents the first data entity and the second side represents the second data entity, wherein the first data entity is independent of the second data entity in relation.

For the first and second entities, constant roles are defined in the form of attribute names, one attribute is called “subject”, where the identifier of the data entity is stored, and which acts as the subject, and another attribute is called “subject”, where the identifier of the data entity is stored, and which acts as an object. Navigation is set only in the direction from subject to object. In this case, the subject represents the first side of the relationship, and the object represents the second side of the relationship:

AnnotationAssertion (rdfs: label: Indicator "Indicator")

SubClassOf (: Indicator owl: Thing)

### first side of the relationship

SubClassOf (: Indicator ObjectSomeValuesFrom (: hasIndicator_subjectId_forObjectEntity: ObjectiveEntity))

### second side of the relationship

SubClassOf (: Indicator ObjectSomeValuesFrom (: hasIndicator_objectId_forObjectEntity: ObjectiveEntity)).

The ratio allows a first multiplicity in the first side and a second multiplicity in the second side. The first multiplicity has a multiplicity value different from the second multiplicity, and is the first constraint indicating the first number of instances of the data entity involved in the relationship on the first side, and the second multiplicity is the second constraint indicating the second number of instances of the data entity involved in attitude on the second side.

The ratio ratio is described in more detail below.

A relationship includes operational behavior for a relationship between the first and second data entities. The operational behavior of a relationship is determined by its type and type. The operational behavior of the relationship is discussed in detail below.

The data entity includes the type of data entity, which is determined by the attribute:

Declaration (DataProperty (: hasNameTypeObjectEntity)).

The memory, presented in the form of a machine-readable medium, contains instructions executed by the computer processor stored in it.

The first and second entities are interconnected using another entity, and this other entity that connects the first and second entities is an indicator.

### Definition of an indicator

Declaration (Class (: Indicator))

AnnotationAssertion (rdfs: label: Indicator "Indicator").

The set of such indicators specific for a certain relationship between the first and second data entities is a type of indicator:

Declaration (Class (: QualifierIndicatorType))

AnnotationAssertion (rdfs: label: QualifierIndicatorType "Indicator Type").

The type of an indicator is determined by the unique name on the set of names of indicator types, and the indicator type always has instances of an indicator of this type, and the indicator is always expressed explicitly through an entity that has many attributes:

### Indicator Type Definition

Declaration (Class (: QualifierIndicatorType))

AnnotationAssertion (rdfs: label: QualifierIndicatorType "Indicator Type")

SubClassOf (: QualifierIndicatorType: Qualifier)

### Declaration of Attributes of a Metric Type

SubClassOf (: QualifierIndicatorType DataSomeValuesFrom (: hasNameTypeIndicator xsd: string))

SubClassOf (: QualifierIndicatorType DataSomeValuesFrom (: hasCodeTypeIndicator xsd: string))

SubClassOf (: QualifierIndicatorType DataSomeValuesFrom (: hasProcessName xsd: string))

SubClassOf (: QualifierIndicatorType DataSomeValuesFrom (: hasNameMeasuredEssence xsd: string))

SubClassOf (: QualifierIndicatorType DataSomeValuesFrom (: hasFormalCharacteristic xsd: string))

SubClassOf (: QualifierIndicatorType DataSomeValuesFrom (: hasNameMeasuredEssenceAddition xsd: string))

SubClassOf (: QualifierlndicatorType DataSomeValuesFrom (: hasNameProcessAddition xsd: string))

Description of the attributes of the metric type.

The NameTypeIndicator attribute is the name of an indicator that carries a semantic description of the relationship and has a textual representation form convenient for human visual perception.

Attribute group for machine processing instances of a measure type The CodeTypelndicator attribute is a unique identifier for a measure type.

The ProcessName attribute is the name of the process, action or state in which the dimension entity is involved, i.e. this attribute refers to the activity of the subject aimed at the object, as a result of which the "measurement" of the measured entity is made, and declares a positive end result of this activity. The value of the “process name” attribute is a text phrase that represents the part of the name of the indicator expressed by the predicate and answers the question “What is being done with the essence of the dimension?”

The NameMeasuredEssence attribute is the name of the entity being measured during the process, action, or state. The attribute value is a text phrase that represents the part of the indicator name expressed by a noun that answers the question “What is measured?”. For the convenience of presenting and organizing the transfer of information using the indicator, the measured entities are grouped and classified within the framework of information sections. The unit of measurement of the value of the indicator is associated with the measured entity.

FormalCharacteristic attribute - defines the method of obtaining the indicator value. The attribute value is a text phrase representing a part of the indicator’s name, expressed by circumstance and answering the question “How is a measured entity measured?”

The NameMeasuredEssenceAddition attribute - semantically complements the name of the measured entity. The attribute value is a text phrase that represents the part of the indicator name expressed by the adjective.

NameProcessAddition attribute - complements the name of the process, action or state. The attribute value is a text phrase that represents the part of the indicator name expressed by the adjective.

The name of the indicator type is constructed in the form of a text expression that defines the operational behavior of the associated data entities that is convenient for human presentation, as well as in the form of a decomposition of the indicator type name into separate attributes for machine processing of the indicator type name.

The name of the indicator is formed in the form of a set of attribute values of the indicator type, in the form of a complete simple grammatical sentence of a natural language containing the subject and predicate. The subject in the name of the indicator is the name of the measured entity, and the predicate is the name of the process, action or state.

An example of the formation of the full name of the indicator: "Determination of the amount of chemical agent used."

Action: Definition

Addition of the process, actions:

Measured Entity: Medium

Addition of measured entity: chemical applied

Formal characteristic: quantity.

Consistently forming the name of the indicator from the attribute values, we obtain the name of the indicator type:

The indicator is a function of time, where the time arguments are specified as a group of attributes, the composition of which is determined by the category of the indicator.

Many indicators in relation to the management function are classified into three categories:

Declaration (Class (: Qualifier))

Declaration (Class (: QualifierIndicatorCategory))

### Category: Target

Declaration (Class (: PlannedIndicator))

AnnotationAssertion (rdfs: label: PlannedIndicator "Metric Planned")

SubClassOf (: PlannedIndicator: QualifierIndicatorCategory)

### Category: Current indicator

Declaration (Class (: CurrentIndicator))

AnnotationAssertion (rdfs: label: CurrentIndicator "MetricCurrent")

SubClassOf (: CurrentIndicator: QualifierIndicatorCategory)

### Category: Historical Indicator

Declaration (Class (: HistoricalIndicator))

AnnotationAssertion (rdfs: label: HistoricalIndicator "Historical Metric")

SubClassOf (: HistoricalIndicator QualifierlndicatorCategory).

A planned indicator is an indicator representing one of the many characteristics that characterize the state of planning of a data entity and its relationships with other entities. The sources of the formation of planned indicators are planning documents: decisions, plans, explanatory notes, directives, orders, applications, etc.

Current indicator - an indicator representing one of the many characteristics that characterize the current state of the data entity and its relationships with other entities. The source of the formation of current indicators is operational information about the entities of the data received in reports, summaries, reports, information messages, etc.

Historical indicator - an indicator representing one of the many characteristics that characterize the past state of an object and its relations with other objects. The historical indicator is formed on the basis of the current indicator.

A group of attributes representing time arguments based on the category of a measure.

For the current indicator, this group is represented by one attribute TimeBeginningUrgency:

### Attribute TimeBeginningUrgency - time of the beginning of the relevance of the current indicator.

Declaration (DataProperty (: hasTimeBeginningUrgency))

SubClassOf (: CurrentIndicator DataSomeValuesFrom (: hasTimeBeginningUrgency xsd: string))

AnnotationAssertion (rdfs: label: hasTimeBeginningUrgency "has the Relevance Start Time" ^∧∧ xsd: string)

SubDataPropertyOt (: hasTimeBeginningUrgency: propertyCurrentIndicator)

FunctionalDataProperty (: hasTimeBeginningUrgency)

DataPropertyRange (: hasTimeBeginningUrgency xsd: string).

For a planned indicator, this group consists of the attributes:

### Time Delta Attribute

Declaration (DataProperty (: hasTimeDelta))

SubClassOf (: PlannedIndicator DataSomeValuesFrom (: hasTimeDelta xsd: string))

AnnotationAssertion (rdfs: label: hasTimeDelta "has Delta ^Time " ^∧∧ xsd: string)

SubDataPropertyOf (: hasTimeDelta: propertyPlannedIndicator)

FunctionalDataProperty (: hasTimeDelta)

DataPropertyRange (: hasTimeDelta xsd: string)

### TimeX Attribute

Declaration (DataProperty (: hasTimeX))

SubClassOf (: PlannedIndicator DataAllValuesFrom (: hasTimeX xsd: string))

AnnotationAssertion (rdfs: label: hasTimeX "hasTimeTime" ^∧∧ xsd: string)

SubDataPropertyOf (: hasTimeX: propertyPlannedIndicator)

FunctionalDataProperty (: hasTimeX)

DataPropertyRange (: hasTimeX xsd: string)

### DateAndTimeBeginningPeriodTransferIndicator Attribute

Declaration (DataProperty (: hasDateAndTimeBeginningPeriodTransferIndicator))

SubClassOf (: PlannedIndicator

DataSomeValuesFrom (: hasDateAndTimeBeginningPeriodTransferIndicator xsd: string))

AnnotationAssertion (rdfs: label: hasDateAndTimeBeginningPeriodTransferIndicator has a DateStartTransmissionTransferPeriod " ^∧∧ xsd: string)

SubDataPropertyOf (: hasDateAndTimeBeginningPeriodTransferIndicator: propertyPlannedIndicator)

FunctionalDataProperty (: hasDateAndTimeBegirmingPeriodTransferIndicator)

DataPropertyRange (: hasDateAndTimeBeginningPeriodTransferIndicator xsd: string)

### DateAndTimeTerminationPeriodReportingIndicators Attribute

Declaration (DataProperty (: hasDateAndTimeTerminationPeriodReportingIndicators))

SubClassOf (: PlannedIndicator DataSomeValuesFrom (: hasDateAndTimeTerminationPeriodReportingIndicators xsd: string))

AnnotationAssertion (rdfs: label: hasDateAndTimeTerminationPeriodReportingIndicators "has a DateTimeEnd of the End of the Reporting Period by the Indicators" ^∧∧ xsd: string)

SubDataPropertyOf (: hasDateAndTimeTerminationPeriodReportingIndicators: propertyPlannedIndicator)

FunctionalDataProperty (: hasDateAndTimeTerminationPeriodReportingIndicators)

DataPropertyRange (: hasDateAndTimeTerminationPeriodReportingIndicators xsd: string)

### DeltaUnitMeasureTime Attribute

Declaration (DataProperty (: hasDeltaUnitMeasureTime))

SubClassOf (: PlannedIndicator DataSomeValuesFrom (: hasDeltaUnitMeasureTime xsd: string))

AnnotationAssertion (rdfs: label: hasDeltaUnitMeasureTime "has a Unit of Measurement of Time Delta" ^∧∧ xsd: string)

SubDataPropertyOf (: hasDeltaUnitMeasureTime: propertyPlannedIndicator)

FunctionalDataProperty (: hasDeltaUnitMeasureTime)

DataPropertyRange (: hasDeltaUnitMeasureTime xsd: string)

### FrequencyIndicator Attribute

Declaration (DataProperty (: hasFrequencyIndicator))

SubClassOf (: Indicator DataSomeValuesFrom (: hasFrequencyIndicator xsd: string))

AnnotationAssertion (rdfs: label: hasFrequencyIndicator "has a Metric Frequency of" ^∧∧ xsd: string)

SubDataPropertyOf (: hasFrequencyIndicator: propertyPndicator)

FunctionalDataProperty (: hasFrequencyIndicator)

DataPropertyRange (: hasFrequencyIndicator xsd: string)

Time attributes determine the time interval for the relevance of the relationship between the entities or values represented by the indicator, as well as the frequency of formation of the next current indicator. The time interval is characterized by the date and time of its beginning and end.

For the category “current indicator”, the time interval is specified by explicitly indicating the beginning of the time period as the value of the TimeBeginningUrgency attribute and implicitly indicating the end of the time period. In this case, the end time of the time interval is taken to be infinity, and the value of the end time of the time interval can be changed to the time when a new current indicator with the same identifier as the previous indicator was generated in the system.

For the category “planned indicator”, temporary attributes determine:

The TimeX attribute is the time the process started, the action. The value of the TimeX attribute can take either an undefined value or a specific value of the date and time of the beginning of the process, action.

The TimeDelta attribute is the time interval from the value specified by the TimeX attribute to the start time of the periodic generation of information, presented in the form of current indicators, characterizing the state of an object and its relations with other data objects.

Attribute DeltaUnitMeasureTime - sets the unit of measurement for the time period specified in the TimeDelta attribute.

The DateAndTimeBeginningPeriodTransferIndicator attribute is the date and time when the relevance of the characteristic value or relationship specified by the indicator starts.

The DateAndTimeTerminationPeriodReportinglndicators attribute is the date and time the end of the relevance of the characteristic value or relationship specified by the indicator.

The Frequencylndicator attribute - the frequency of the formation of the next current indicator DateAndTimeTerminationPeriodReportingIndicators. The value of the Frequencylndicator attribute is used to calculate the value of the DateAndTimeTerminationPeriodReportingIndicators attribute.

The sets of time attributes of the planned and current indicators allow the analysis of process control (action) by deviations (plan-fact), to control the fact of achieving the planned result.

For a historical indicator, a group of time attributes is composed of:

### DateTimeBeganRelevanceIndicator Attribute

AnnotationAssertion (rdfs: label: hasDateTimeBeganRelevanceIndicator "has a DateTimeStartedMeasurement Relevance")

SubDataPropertyOf (: hasDateTimeBeganRelevanceIndicator: HistotyIndicator)

FunctionalDataProperty (: hasDateTimeBeganRelevanceIndicator)

DataPropertyRange (: hasDateTimeBeganRelevanceIndicator xsd: string)

### DateTimeTerminationRelevanceIndicator Attribute

AnnotationAssertion (rdfs: label: hasDateTimeTerminationRelevanceIndicator "has a DateTimeEnd of End of an Indicator Relevance")

SubDataPropertyOf (: hasDateTimeTerminationRelevanceIndicator: HistotyIndicator)

FunctionalDataProperty (: hasDateTimeTerminationRelevanceIndicator)

DataPropertyRange (: hasDateTimeTerminationRelevanceIndicator xsd: string)

Attribute DateTimeBeganRelevanceIndicator - date, time of the beginning of the period of relevance of the value of the current indicator, which has become a historical indicator.

The DateTimeTerminationRelevanceIndicator attribute is the date and time of the end of the relevance of the current indicator that has become historical.

In the indicator, a group of attributes is selected, which determines the path according to information sections of the indicator type by indicator:

### WayOnInformationCuts Attribute

Declaration (DataProperty (: hasWayOnInformationCuts))

SubClassOf (: Indicator DataSomeValuesFrom (: has WayOnlnformationCuts xsd: string))

AnnotationAssertion (Annotation (rdfs: comment "Format string: nodeName1 / Node name2 / ... / NodeName N" ^∧∧ xsd: string) rdfs: label: hasWayOnlnformationCuts "has a Path for Information Sections" ^∧∧ xsd: string)

SubDataPropertyOf (: has WayOnlnformationCuts: propertyIndicator)

FunctionalDataProperty (: has WayOnlnformationCuts).

The WayOnlnformationCuts attribute contains the value of the path along the information sections of the indicator. The path along the information sections semantically clarifies the value of the measured entity in the indicator “characteristic” and the indicator “interaction”, in the indicator “association” specifies the action and attitude. The refinement is due to the classification of the measured entity. Clarification is made in the direction from the generalized measured entity to its variety. The measured entities are connected by relations of the “is a variety” type. All varieties of measured entities form a hierarchical structure. Varieties of measured entities of one level form an informational section. The totality of varieties of measured entities of one branch of the hierarchy form a "path". The full name of the specified measured entity consists of the names from the generalized measured entity to the considered specified measured entity.

An example of a path: DataPropertyAssertion (: hasWayOnInformationCuts: IndCur1 "military personnel / sergeants, soldiers" ^∧∧ xsd: string).

To understand the indicator, it is important to express its meaning through natural language.

An indicator is a fact, the semantics of which are described by a grammatical sentence, and which is formed by the concatenation of the attribute values of the indicator. The resulting grammatical sentence is a logical statement with a complete meaning regarding the relationship between the first entity and the second entity. The resulting grammatical sentence should convey the meaning of the measured process, the action laid down in the name of the indicator.

An example of the formation of a proposal from the values of the attributes of the indicator.

### For the subject labeled "Motor Rifle Brigade"

AnnotationAssertion (rdfs: label: Subj1 "Motor Rifle Brigade")

Class Assertion (: ObjectiveEntity: Subj1)

### Current metric of type defined

Declaration (NamedIndividual (: TypeInd01))

ObjectPropertyAssertion (: hasIndicator_typeIndicatorId_forTypeIndicator: IndCur 1: TypeInd01)

AnnotationAssertion (rdfs: label: TypeInd01 "Number of Personnel" ^∧∧ xsd: string)

ClassAssertion (: QualifierIndicatorType: TypeInd01)

DataPropertyAssertion (: hasNameTypeIndicator: TypeInd01 "Number of personnel" ^∧∧ xsd: string)

### Attributes of the current metric

AnnotationAssertion (rdfs: label: IndCur1 "Current Indicator 1")

ClassAssertion (: CurrentIndicator: IndCur 1)

ObjectPropertyAssertion (: hasIndicator_kindIndicatorId_forKindIndicator: IndCur1: Character)

ObjectPropertyAssertion (: hasIndicator_subjectId_forObjectEntity: IndCurl: Subj 1)

ObjectPropertyAssertion (: hasIndicator_typeIndicatorId_forTypeIndicator: IndCur1: TypeInd01)

DataPropertyAssertion (: hasCategoryIndicator: IndCurl "Current" ^∧∧ xsd: string)

DataPropertyAssertion (: hasCategoryValueIndicator: IndCurl "absolute value" ^∧∧ xsd: string)

DataPropertyAssertion (: hasFrequencyIndicator: IndCur1 monthly ^∧∧ xsd: string)

DataPropertyAssertion (: hasNameMeasureValueBasis: IndCur 1 "people" ^∧∧ xsd: string)

DataPropertyAssertion (: hasWyOnInformationCuts: IndCur1 "military personnel / sergeants, soldiers" ^∧∧ xsd: string)

DataPropertyAssertion (: valueIndicatorBases: IndCur "1600" ^∧∧ xsd: string)

Concatenating attribute metric values gives the following grammatical sentence:

"The number of personnel" military personnel / sergeants, soldiers "of the motorized rifle brigade for the previous month amounted to 1600 people."

The indicator contains a mechanism for materializing the relationship, i.e. binding relationships to the source of information about this relationship. For these purposes, use the Indicator_sourceIInfrtId_forObjectEntity: ObjectiveEntity attribute, the value of which is a reference to an object of data that acts as a source of information:

Declaration (ObjectProperty (: hasIndicator_sourceIInftId_forObjectEntity))

SubClassOf (: Indicator ObjectSomeValuesFrom (: hasIndicator_sourceIInftId_forObjectEntity: ObjectiveEntity))

AnnotationAssertion (rdfs: label: hasIndicator_sourceIInftId_forObjectEntity "has a Indicator.objectEssenceResourcesInformation Source")

SubObjectProperty Of (: hasIndicator_sourceIInftId_forObj ectEntity: CommunicationsIndicator)

FunctionalObjectProperty (: hasIndicator_sourceIInftId_forObj ectEntity)

Many types of indicators in the form of relations between the first and second data entities are divided into subsets, which are types of indicators: characteristics, interaction, association, and where the type determines the operational behavior of indicators.

The type of indicator “characteristic” is a form of relationship between the type of data entity on the one hand of the indicator, acting as the subject of the relationship, and the environment on the other hand of the indicator, acting as the object. The indicator in this case is the characteristic of the subject in the environment, through which data values of a certain type are associated with the subject.

### A set of indicators of the "Characteristic" type is formed according to the following rule:

Declaration (Class (: IndicatorGroupsByKindCharacteristic))

AnnotationAssertion (rdfs: label: IndicatorGroupsByKindCharacteristic "IndicatorsBy ViewCharacteristic")

AnnotationAssertion (rdfs: comment: IndicatorGroupsByKindCharacteristic "Many indicators of the form \" Characteristic \ " ^∧∧ xsd: string)

EquivalentClasses (: IndicatorGroupsByKindCharacteristic ObjectHasValue (: hasIndicator_kindIndicatorId_forKindIndicator: Character))

SubClassOf (: IndicatorGroupsByKindCharacteristic: IndicatorGroupsByKind).

The type of the “interaction” indicator is a form of the relationship between two peer data entities on one and the other side of the indicator, where the first entity acts as a subject and the second entity acts as an object, while the indicator quantitatively or qualitatively characterizes the interaction between the subject and object.

### A set of indicators of the type “Interaction” is formed according to the following rule:

Declaration (Class (: IndicatorGroupsByKindInteraction))

AnnotationAssertion (rdfs: label: IndicatorGroupsByKindInteraction "IndicatorsBy ViewInteraction")

AnnotationAssertion (rdfs: comment: IndicatorGroupsByKindInteraction "A lot of indicators of the form \" Interaction \ "" ^s xsd: string)

EquivalentClasses (: IndicatorGroupsByKindInteraction ObjectHasValue (: hasIndicator_kindIndicatorId_forKindIndicator: Interaction))

SubClassOf (: IndicatorGroupsByKindInteraction: IndicatorGroupsByKind).

The type of indicator “association” is a form of relationship between two peer data entities on one and the other side of the indicator, where the first data entity acts as a subject, and the second data entity acts as an object, and the subject and object, by means of an indicator of this kind form aggregation.

### The set of indicators of the “Association” type is formed according to the following rule:

Declaration (Class (: IndicatorGroupsByKindAssociation))

AnnotationAssertion (rdfs: comment: IndicatorGroupsByKindAssociation "Many indicators of the form \" Association \ "" ^∧∧ xsd: string)

AnnotationAssertion (rdfs: label: IndicatorGroupsByKindAssociation "IndicatorsBy ViewAssociation")

EquivalentClasses (: IndicatorGroupsByKindAssociation ObjectHasValue (: hasIndicator_kindIndicatorId_forKindIndicator: Association))

SubClassOf (: IndicatorGroupsByKindAssociation: IndicatorGroupsByKind).

или 1, причем значение кратности на второй стороне определяется в зависимости от вида показателя.The first ratio in the first side of the indicator always takes a value equal to 1, and the second ratio on the second side of the indicator takes the value

or 1, and the multiplicity value on the second side is determined depending on the type of indicator.

AnnotationAssertion (rdfs: label indicator "Indicator")

SubClassOf (: Indicator owl: Thing)

### The first side of the relationship. Multiplicity is always equal to 1.

SubClassOf (: Indicator ObjectSomeValuesFrom (: hasIndicator_subjectId_forObjectEntity: ObjectiveEntity))

.### The second side of the relationship. Multiplicity is 1 or

.

SubClassOf (.indicator ObjectSomeValuesFrom (: hasIndicator_objectId_forObjectEntity: Object veEntity))

. Показатель вида «Взаимодействие» имеет кратность 1:1. Показатель вида «Ассоциация» имеет кратность 1:1, либо

.An indicator of the form “Characteristic” has a multiplicity

. An indicator of the type “Interaction” has a multiplicity of 1: 1. An indicator of the type “Association” has a multiplicity of 1: 1, or

.

Claims (10)

1. A system for determining the relationship between the first and second data entities, comprising a computer processor for executing computer-executable instructions and processing data stored in memory, a memory connected to the processor, storing components of the entities and components of the relationship, and: the first component of the object entities and the second component of an entity provide a first data entity and a second data entity, wherein each data entity has uniformities identity on a large number of heterogeneous subject areas, and at the same time, the unified identity of data entities is supplemented by the value of the identifier of the entity, which is the basis for linking to each entity, and the relationship component explicitly determines the relationship between the first and second data entities, the relationship contains two sides, so the first side represents the first data entity, and the second side represents the second volume a distinct data entity, wherein the first data entity is independent of the second data entity in relation, the relation allowing a first multiplicity in the first side and a second multiplicity in the second side, the first multiplicity having a multiplicity value different from the second multiplicity, and the first the multiplicity is the first constraint indicating the first number of instances of the data entity involved in the relationship on the first side, and the second multiplicity is the second constraint indicating the second number of instances of the data entity involved in the relationship on the second side, the relationship includes operational behavior for the relationship between the first and second data entities, where the data entity includes a data entity type and the memory represented in the form of a machine-readable medium, contains instructions executed by a computer processor stored in it, characterized in that the first and second entities are interconnected using another an entity, moreover, this other entity connecting the first and second entities is an indicator, and the set of similar indicators specific to a certain relationship between the first and second data entities is an indicator type, where the indicator type is determined by a unique name on the set of names of types of indicators, and the type of indicator always has instances of an indicator of this type, and the indicator is always expressed explicitly through an entity, to that has a set of attributes, and the indicator is a function of time, where the time arguments are specified as a group of attributes, the composition of which is determined by the category of the indicator, and a group of attributes is selected in the indicator, which determines the path according to information sections of the indicator type, and the indicator type name is constructed in the form of a text expression that defines the operational behavior of the associated data entities suitable for human presentation, as well as in the form of decompositions and the name of the indicator type for individual attributes, for machine processing the name of the indicator type, and the indicator itself is a fact whose semantics are described by the grammatical sentence, and which is formed by the concatenation of the values of the indicator’s attributes, and this grammatical sentence is a logical statement with a complete sense regarding the relationship between the first entity and the second entity, and many indicators in relation to the management function of classifiers It is divided into three categories, which are: the current indicator, planned indicator, historical indicator, while many types of indicators in the form of relations between the first and second data entities are divided into subsets that are types of indicators: characteristic, interaction, association, and where defines the operational behavior of indicators, and for the first and second object entities, fixed roles are defined in the form of attribute names, one attribute is called the “subject”, where the identifier is stored the ikator of the data entity, which performs the role of the subject, and another attribute is called the “object”, where the identifier of the data entity is stored, and which serves as the object, and navigation is specified only in the direction from the subject to the object, and where the subject represents the first side of the relationship , and the object represents the second side of the relationship, where the first ratio in the first side of the indicator always takes a value of 1, and the second ratio on the second side of the indicator takes the value null or 1, and is significant e multiplicity on the second side is determined depending on the type of indicator. 2. The system according to claim 1, in which each indicator has a unified identity on a large number of heterogeneous subject areas, while the unified identity of the indicators is supplemented by the value of the indicator identifier. 3. The system according to claim 1, in which the type of indicator “characteristic” is a form of relationship between the type of data entity on the one hand of the indicator, acting as the subject of the relationship, and the environment on the other hand an indicator serving as an object, and the indicator in this case is a characteristic of the subject in the environment, through which data values of a certain type are associated with the subject. 4. The system according to claim 1, in which the form of the “interaction” indicator is a form of the relationship between two peer data entities on one and the other side of the indicator, where the first object acts as a subject and the second object acts as an object, the indicator quantitatively or qualitatively characterizes the interaction between the subject and the object. 5. The system according to claim 1, in which the type of indicator “association” is a form of the relationship between two peer data entities on one and the other side of the indicator, where the first data entity acts as the subject and the second data entity acts as object, and the subject and the object, through an indicator of this kind, form aggregation. 6. The system according to claim 1, in which the planned indicators characterize the state of planning of the data entities and their relationships with each other. 7. The system according to claim 1, in which the current indicators characterize the state at the current time of the data entities and their relationships with each other. 8. The system according to claim 1, in which historical indicators characterize the past state of the data entities and their relationships with each other. 9. The system according to claim 1, where the path along the information sections of each type of indicator semantically clarifies the relationship between the first and second data entities.