ГОСТ Р 55346—2012
(*A Textual_section is text in which constituent elements (paragraphs) are named. <note>The Textual_section is provid
ed for situations where the structure of the textual information needs further formatting.</note> *)
ENTITY textual_section;
(* The element specifies the individual element of the template. *)
element: LIST [1 : ?] OF textual_paragraph;
(* The name specifies the word, or set of words, that is used to refer to the Textual_section.’)
name : label;
END_ENTITY;
(*A Textual_specification is text expressed using a defined langauge. <note number=T>The language may or may not
be computer interpretab!e.<i‘note> *)
ENTITY textual_specification;
definition; text_seiect;
(* The definitionjanguage specifies with a word or set of words the language that the specification is written in. <note
number="3’> Possible values for definitionjanguage could be *ANSI C. “structured text*. etc.</note> <note num ber^
*4->The list of preferred languages shall be revisited.</note> *)
definitionjanguage : label.
END_ENT!TY:
(*A TextualJable is a representation of a row structure where a Textual_section represents each position in the structure.
<note number="r>ATextua!_section may hold a list of Textual_paragraph objects. Each Textual_paragraph represents a
column in the Textual_table.<i’note> *)
ENTITY textualJable;
(* The name specifies the word, or set of words, that is used to refer to the Textualjable. *)
name; label;
(* The table_row specifies the number of rows in theTextual Jable. <note number=‘2’>The number of rows shall be
greater than zero.</note> *)
tab!e_row ; LIST [1 ; ?] OF textual_section;
END_ENTITY;
(*A Triggered_system_view_relationship is a type of Partial_system_view_relationship and an indicator thatTBD <note
number=T>The model support specification of system modes (each PartiaJ_system_viewcan be viewed as a high level
mode ofa system).A Triggered_system_view_relationship is a Partial_system_view_relationship where the relation be
tween relating and related Partial_sysiem_view is such that the system can make a transition from one mode to another
when the transit*on_condition attribute is fu№Bed.</note><note number=’2">The relationship isunidirectional, the Trig-
gered_system_view_relationship only specifies a transition from the related to the relating Partial_system_view.</note>
*) ENTITY triggered_system_view_relationship
SUBTYPE OF (partial_system_view_relationship);
(* The transition_condition specifies, in text, the condition that shall be fulfilled. <r»otenumber="3’>lf the transition is
fulfilled the TBD.</r»ote> *)
transition_condition ; text;
END_ENTITY;
(*An Undefined_data_type_definition is a type of User_defined_dataJype_definition whose value domain and range
are not defined. <note>The Undefined_data_type_defmition shall be used in all cases where the data type of a Datajn-
stance is unknown.</note> “)
ENTITY undefined_data_type_definition
SUBTYPE OF (user_defined_dataJype_definition);
END_ENTITY;
(* A Union_dataJype_definition is a type of User_defined_data_type_definition strocture which can take the value of one
of its components at any time. *)
ENTITY union_data_type_definition
SUBTYPE OF (user_defmed_dataJype_definit»on);
END_ENTITY;
(* An Union_data_type_member is a relationship between a Union_dataJype_definition and a Data_field it contains. The
members of a Union_da!a_type_definition are mutually exclusive. ’)
ENTITY union_data_type_member;
(* The chfld specifies the DataJield object in the relationship
‘)
386