Application module: Physical node requirement to implementing component allocation ISO/TS 10303-1723: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 entity definitions
   4.3 ARM function definitions
5 Module interpreted model
   5.1 Mapping specification
   5.2 MIM EXPRESS short listing
     5.2.1 MIM entity definitions

A MIM short names
B Information object registration
C ARM EXPRESS-G   EXPRESS-G
D MIM EXPRESS-G   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:

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

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:

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:

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 Assembly_to_part_connectivity_structure_allocation

MIM element: assembly_to_part_connectivity_structure_allocation
Source: ISO 10303-1723
Reference path:   {[assembly_to_part_connectivity_structure_allocation <=
shape_aspect]
[assembly_to_part_connectivity_structure_allocation <=
shape_aspect_relationship]}

5.1.1.1 name

MIM element: shape_aspect.name
Reference path:   assembly_to_part_connectivity_structure_allocation <=
shape_aspect
shape_aspect.name

5.1.1.2 Assembly_to_part_connectivity_structure_allocation to Part_connected_terminals_element (as part_element)

MIM element: PATH
Reference path:   assembly_to_part_connectivity_structure_allocation <=
shape_aspect_relationship
shape_aspect_relationship.relating_shape_aspect ->
shape_aspect =>
part_connected_terminals_element

5.1.1.3 Assembly_to_part_connectivity_structure_allocation to Physical_connectivity_definition (as assembly_context)

MIM element: PATH
Reference path:   assembly_to_part_connectivity_structure_allocation <=
shape_aspect <-
shape_aspect_relationship.related_shape_aspect
{shape_aspect_relationship
shape_aspect_relationship.name = 'assembly context'}
shape_aspect_relationship.relating_shape_aspect ->
shape_aspect =>
physical_connectivity_definition

5.1.1.4 Assembly_to_part_connectivity_structure_allocation to Physical_connectivity_element (as assembly_element)

MIM element: PATH
Reference path:   assembly_to_part_connectivity_structure_allocation <=
shape_aspect_relationship
shape_aspect_relationship.related_shape_aspect ->
shape_aspect =>
physical_connectivity_element

5.1.2 Physical_node_branch_requirement_to_implementing_component_allocation

MIM element: physical_node_branch_requirement_to_implementing_component_allocation
Source: ISO 10303-1723
Reference path:   {[physical_node_branch_requirement_to_implementing_component_allocation <=
shape_aspect]
[physical_node_branch_requirement_to_implementing_component_allocation <=
shape_aspect_relationship]}

5.1.2.1 name

MIM element: shape_aspect.name
Source: ISO 10303-41
Reference path:   physical_node_branch_requirement_to_implementing_component_allocation <=
shape_aspect
shape_aspect.name

5.1.2.2 Physical_node_branch_requirement_to_implementing_component_allocation to Assembly_component (as implementation_component)

MIM element: PATH
Reference path:   physical_node_branch_requirement_to_implementing_component_allocation <=
shape_aspect
shape_aspect.of_shape ->
product_definition_shape =>
assembly_component

5.1.2.3 Physical_node_branch_requirement_to_implementing_component_allocation to Assembly_joint (as implementation_joint_set)

MIM element: PATH
Reference path:   physical_node_branch_requirement_to_implementing_component_allocation <=
shape_aspect <-
shape_aspect_relationship.related_shape_aspect
{shape_aspect_relationship
shape_aspect_relationship.name = 'implementation joint'}
shape_aspect_relationship.relating_shape_aspect ->
shape_aspect =>
component_feature_joint =>
assembly_joint

5.1.2.4 Physical_node_branch_requirement_to_implementing_component_allocation to Interface_mounted_join (as implementation_interface_joint_set)

MIM element: PATH
Reference path:   physical_node_branch_requirement_to_implementing_component_allocation <=
shape_aspect <-
shape_aspect_relationship.related_shape_aspect
{shape_aspect_relationship
shape_aspect_relationship.name = 'implementation interface joint'}
shape_aspect_relationship.relating_shape_aspect ->
shape_aspect =>
interface_mounted_join

5.1.2.5 Physical_node_branch_requirement_to_implementing_component_allocation to Part_connected_terminals_element (as part_element)

MIM element: PATH
Reference path:   physical_node_branch_requirement_to_implementing_component_allocation <=
shape_aspect_relationship
shape_aspect_relationship.relating_shape_aspect ->
shape_aspect =>
part_connected_terminals_element

5.1.2.6 Physical_node_branch_requirement_to_implementing_component_allocation to Physical_connectivity_element (as physical_node_branch_requirement)

MIM element: PATH
Reference path:   physical_node_branch_requirement_to_implementing_component_allocation <=
shape_aspect_relationship
shape_aspect_relationship.related_shape_aspect ->
shape_aspect =>
physical_connectivity_element

5.1.3 Physical_node_requirement_to_implementing_component_allocation

MIM element: physical_node_requirement_to_implementing_component_allocation
Source: ISO 10303-1723
Reference path:   {[physical_node_requirement_to_implementing_component_allocation <=
shape_aspect]
[physical_node_requirement_to_implementing_component_allocation <=
shape_aspect_relationship]}

5.1.3.1 Physical_node_requirement_to_implementing_component_allocation to Assembly_component (as implementation_component)

MIM element: PATH
Reference path:   physical_node_requirement_to_implementing_component_allocation <=
shape_aspect_relationship
shape_aspect_relationship.related_shape_aspect ->
shape_aspect.of_shape ->
product_definition_shape =>
assembly_component

5.1.3.2 Physical_node_requirement_to_implementing_component_allocation to Assembly_joint (as implementation_joint_set)

MIM element: PATH
Reference path:   physical_node_requirement_to_implementing_component_allocation <=
shape_aspect <-
shape_aspect_relationship.related_shape_aspect
{shape_aspect_relationship
shape_aspect_relationship.name = 'implementation joint'}
shape_aspect_relationship.relating_shape_aspect ->
shape_aspect =>
component_feature_joint =>
assembly_joint

5.1.3.3 Physical_node_requirement_to_implementing_component_allocation to Interface_mounted_join (as implementation_interface_joint_set)

MIM element: PATH
Reference path:   physical_node_requirement_to_implementing_component_allocation <=
shape_aspect <-
shape_aspect_relationship.related_shape_aspect
{shape_aspect_relationship
shape_aspect_relationship.name = 'implementation interface joint'}
shape_aspect_relationship.relating_shape_aspect ->
shape_aspect =>
interface_mounted_join

5.1.3.4 Physical_node_requirement_to_implementing_component_allocation to Physical_connectivity_definition (as physical_node_requirement)

MIM element: PATH
Reference path:   physical_node_requirement_to_implementing_component_allocation <=
shape_aspect_relationship
shape_aspect_relationship.relating_shape_aspect ->
shape_aspect =>
physical_connectivity_definition


© ISO 2018 — All rights reserved