ISO/TS 10303-1679:2018-11 Functional specification


Application module: Functional specification	ISO/TS 10303-1679:2018-11(E) © ISO

Cover page
Table of contents
Copyright
Foreword
Introduction
1 Scope
2 Normative references
3 Terms, definitions and abbreviated terms
3.1 Terms and definitions
3.2 Abbreviated terms

4 Information requirements
4.1 Required AM ARMs
4.2 ARM type definitions
4.3 ARM entity definitions
5 Module interpreted model
5.1 Mapping specification
5.2 MIM EXPRESS short listing
5.2.1 MIM type definitions
5.2.2 MIM entity definitions

A MIM short names
B Information object registration
C ARM EXPRESS-G
D MIM EXPRESS-G
E Computer interpretable listings
F Change history
Bibliography
Index

5.1 Mapping specification

In the following, "Application element" designates any entity data type defined in Clause 4, any of its explicit attributes and any subtype constraint. "MIM element" designates any entity data type defined in Clause 5.2 or imported with a USE FROM statement, from another EXPRESS schema, any of its attributes and any subtype constraint defined in Clause 5.2 or imported with a USE FROM statement.

This clause contains the mapping specification that defines how each application element of this part of ISO 10303 (see Clause 4) maps to one or more MIM elements (see Clause 5.2).

The mapping for each application element is specified in a separate subclause below. The mapping specification of an attribute of an ARM entity is a subclause of the clause that contains the mapping specification of this entity. Each mapping specification subclause contains up to five elements.

Title: The clause title contains:

the name of the considered ARM entity or subtype constraint, or
the name of the considered ARM entity atribute when this attribute refers to a type that is not an entity data type or a SELECT type that contains or may contain entity data types, or
a composite expression, <attribute name> to <referred type>, when this attribute refers to a type that is not an entity data type or a SELECT type that contains or may contain entity data types.

MIM element: This section contains, depending on the considered application element:

the name of one or more MIM entity data types;
the name of a MIM entity attribute, presented with the syntax <entity name>.<attribute name>, when the considered ARM attribute refers to a type that is not an entity data type or a SELECT type that contains or may contain entity data types;
the term PATH, when the considered ARM entity attribute refers to an entity data type or to a SELECT type that contains or may contain entity data types;
the term IDENTICAL MAPPING, when both application objects involved in an application assertion map to the same instance of a MIM entity data type;
the term NO MAPPING EXTENSION PROVIDED, when the extension to an extensible SELECT TYPE has no impact;
the syntax /SUPERTYPE(<supertype name>)/, when the considered ARM entity is mapped as its supertype;
one or more constructs /SUBTYPE(<subtype name>)/, when the mapping of the considered ARM entity is the union of the mapping of its subtypes.

When the mapping of an application element involves more than one MIM element, each of these MIM elements is presented on a separate line in the mapping specification, enclosed between parentheses or brackets.

Source: This section contains:

the ISO standard number and part number in which the MIM element is defined, for those MIM elements that are defined in a common resource document;
the ISO standard number and part number of this part of ISO 10303, for those MIM elements that are defined in the MIM schema of this part.

This section is omitted when the keywords PATH or IDENTICAL MAPPING or NO MAPPING EXTENSION PROVIDED are used in the MIM element section.

Rules: This section contains the name of one or more global rules that apply to the population of the MIM entity data types listed in the MIM element section or in the reference path. When no rule applies, this section is omitted.

A reference to a global rule may be followed by a reference to the subclause in which the rule is defined.

Constraint: This section contains the name of one or more subtype constraints that apply to the population of the MIM entity data types listed in the MIM element section or in the reference path. When no subtype constraint applies, this section is omitted.

A reference to a subtype constraint may be followed by a reference to the subclause in which the subtype constraint is defined.

Reference path: This section contains:

the reference path to its supertypes in the common resources, for each MIM element created within this part of ISO 10303;
the specification of the relationships between MIM elements, when the mapping of an application element requires to relate instances of several MIM entity data types. In such a case, each line in the reference path documents the role of a MIM element relative to the referring MIM element or to the next referred MIM element.

For the expression of reference paths and of the constraints between MIM elements, the following notational conventions apply:

[]	enclosed section constrains multiple MIM elements or sections of the reference path are required to satisfy an information requirement;
()	enclosed section constrains multiple MIM elements or sections of the reference path are identified as alternatives within the mapping to satisfy an information requirement;
{}	enclosed section constrains the reference path to satisfy an information requirement;
<>	enclosed section constrains at one or more required reference path;
\|\|	enclosed section constrains the supertype entity;
->	the attribute, whose name precedes the -> symbol, references the entity or select type whose name follows the -> symbol;
<-	the entity or select type, whose name precedes the <- symbol, is referenced by the entity attribute whose name follows the <- symbol;
[i]	the attribute, whose name precedes the [i] symbol, is an aggregate; any element of that aggregate is referred to;
[n]	the attribute, whose name precedes the [n] symbol, is an ordered aggregate; member n of that aggregate is referred to;
=>	the entity, whose name precedes the => symbol, is a supertype of the entity whose name follows the => symbol;
<=	the entity, whose name precedes the <= symbol, is a subtype of the entity whose name follows the <= symbol;
=	the string, select, or enumeration type is constrained to a choice or value;
\	the reference path expression continues on the next line;
*	one or more instances of the relationship entity data type may be assembled in a relationship tree structure. The path between the relationship entity and the related entities, is enclosed with braces;
--	the text following is a comment or introduces a clause reference;
*>	the select or enumeration type, whose name precedes the > symbol, is extended into the select or enumeration type whose name follows the > symbol;
<*	the select or enumeration type, whose name precedes the <* symbol, is an extension of the select or enumeration type whose name follows the <* symbol;
!{}	section enclosed by {} indicates a negative constraint placed on the mapping.

The definition and use of mapping templates is not supported in the present version of the application modules. However, use of predefined templates /SUBTYPE/ and /SUPERTYPE/ is supported.

5.1.1 Document_assignment

This application object, Document_assignment, is defined in the module document_assignment. This mapping section extends the mapping of Document_assignment, to include assertions defined in this module.

5.1.1.1 Document_assignment to Signal_specification (as is_assigned_to)

#1: If the assignment is not a partial document assignment.

Reference path:

applied_document_reference
applied_document_reference.items[i] ->
document_reference_item
document_reference_item *> fs_document_reference_item
fs_document_reference_item = representation

#2: If the assignment is a partial document assignment.

Reference path:

applied_document_reference
applied_document_reference.items[i] ->
document_reference_item
document_reference_item *> fs_document_reference_item
fs_document_reference_item = representation

5.1.2 External_source_identification

This application object, External_source_identification, is defined in the module external_item_identification_assignment. This mapping section extends the mapping of External_source_identification, to include assertions defined in this module.

5.1.2.1 External_source_identification to Functional_specification (as item)

Reference path:

applied_external_identification_assignment.items[i]-> external_identification_item
external_identification_item *> fs_external_identification_item
fs_external_identification_item = functional_specification

5.1.3 Functional_specification

MIM element:	functional_specification
Source:	ISO 10303-1679
Reference path:	functional_specification <= representation

5.1.3.1 Functional_specification to Functional_specification_definition (as associated_definition)

MIM element:	PATH
Reference path:	functional_specification <= representation <- property_definition_representation.used_representation property_definition_representation property_definition_representation.definition -> property_definition => product_definition_shape => functional_unit => functional_specification_definition

5.1.3.2 Functional_specification to Functional_unit (as characterizing_functional_unit)

MIM element:

PATH

Reference path:

functional_specification <=
representation <-
property_definition_representation.used_representation
property_definition_representation
property_definition_representation.definition ->
property_definition
property_definition.definition ->
characterized_definition
characterized_definition = characterized_product_definition
characterized_product_definition
characterized_product_definition = product_definition
product_definition =>
component_functional_unit

5.1.3.3 Functional_specification to Signal_specification (as characterizing_signal)

MIM element:	PATH
Reference path:	functional_specification <= representation <- representation_relationship.rep_1 representation_relationship {representation_relationship representation_relationship.name = 'characterizing signal for functional specification'} representation_relationship.rep_2 -> representation {representation representation.name = 'signal specification'}

5.1.3.4 Functional_specification to Signal_specification (as reference_signal)

MIM element:	PATH
Reference path:	functional_specification <= representation <- representation_relationship.rep_1 representation_relationship {representation_relationship representation_relationship.name = 'reference signal for functional specification'} representation_relationship.rep_2 -> representation {representation representation.name = 'signal specification'}

5.1.4 Functional_specification_definition

MIM element:	functional_specification_definition
Source:	ISO 10303-1679
Reference path:	functional_specification_definition <= functional_unit <= product_definition {product_definition <- product_definition_context_association.definition product_definition_context_association {product_definition_context_association.role -> product_definition_context_role product_definition_context_role.name = 'part definition type'} product_definition_context_association.frame_of_reference -> product_definition_context <= application_context_element application_context_element.name = 'functional network design'}

5.1.5 Signal_specification

MIM element:	representation
Source:	ISO 10303-43
Reference path:	{representation representation.name = 'signal specification'}

5.1.5.1 Signal_specification to Functional_unit_network_definition (as characterization_network)

MIM element:

PATH

Reference path:

representation <-
property_definition_representation.used_representation
property_definition_representation
property_definition_representation.definition ->
property_definition =>
product_definition_shape =>
functional_unit
{functional_unit <=
product_definition <-
product_definition_context_association.definition
product_definition_context_association
{product_definition_context_association.role ->
product_definition_context_role
product_definition_context_role.name = 'part definition type'}
product_definition_context_association.frame_of_reference ->
product_definition_context <=
application_context_element
application_context_element.name = 'functional network design'}

5.1.5.2 Signal_specification to Functional_unit_network_node_definition (as reference_access_mechanism)

MIM element:

PATH

Reference path:

{representation
representation.items[i] ->
representation_item
representation_item.name = 'reference access mechanism'}
representation <-
property_definition_representation.used_representation
property_definition_representation
property_definition_representation.definition ->
property_definition
property_definition.definition ->
characterized_definition = characterized_product_definition
characterized_product_definition
characterized_product_definition = product_definition
product_definition =>
network_node_definition

5.1.5.3 Signal_specification to Functional_unit_network_node_definition (as signal_access_mechanism)

MIM element:

PATH

Reference path:

{representation
representation.items[i] ->
representation_item
representation_item.name = 'signal access mechanism'}
representation <-
property_definition_representation.used_representation
property_definition_representation
property_definition_representation.definition ->
property_definition
property_definition.definition ->
characterized_definition
characterized_definition = characterized_product_definition
characterized_product_definition
characterized_product_definition = product_definition
product_definition =>
network_node_definition

5.1.5.4 Signal_specification to Functional_unit_terminal (as reference_access_mechanism)

MIM element:

PATH

Reference path:

{representation
representation.items[i] ->
representation_item
representation_item.name = 'reference access mechanism'}
representation <-
property_definition_representation.used_representation
property_definition_representation
property_definition_representation.definition ->
property_definition
property_definition.definition ->
characterized_definition
characterized_definition = shape_definition
shape_definition
shape_definition = shape_aspect
shape_aspect =>
component_functional_terminal

5.1.5.5 Signal_specification to Functional_unit_terminal (as signal_access_mechanism)

MIM element:

PATH

Reference path:

{representation
representation.items[i] ->
representation_item
representation_item.name = 'signal access mechanism'}
representation <-
property_definition_representation.used_representation
property_definition_representation
property_definition_representation.definition ->
property_definition
property_definition.definition ->
characterized_definition
characterized_definition = shape_definition
shape_definition
shape_definition = shape_aspect
shape_aspect =>
component_functional_terminal

5.1.5.6 Signal_specification to Signal_property (as maximum_characteristic)

MIM element:	PATH
Reference path:	{representation representation.items[i] -> representation_item representation_item.name = 'maximum characteristic'} representation <- property_definition_representation.used_representation property_definition_representation property_definition_representation.definition -> property_definition {property_definition property_definition.name = 'signal property'}

5.1.5.7 Signal_specification to Signal_property (as minimum_characteristic)

MIM element:	PATH
Reference path:	{representation representation.items[i] -> representation_item representation_item.name = 'minimum characteristic'} representation <- property_definition_representation.used_representation property_definition_representation property_definition_representation.definition -> property_definition {property_definition property_definition.name = 'signal property'}

5.1.5.8 Signal_specification to Signal_property (as nominal_characteristic)

MIM element:	PATH
Reference path:	{representation representation.items[i] -> representation_item representation_item.name = 'nominal characteristic'} representation <- property_definition_representation.used_representation property_definition_representation property_definition_representation.definition -> property_definition {property_definition property_definition.name = 'signal property'}