ISO/TS 10303-1684:2010-03 Interconnect module connection routing


Application module: Interconnect module connection routing	ISO/TS 10303-1684:2010-03(E) © ISO

Cover page
Table of contents
Copyright
Foreword
Introduction
1 Scope
2 Normative references
3 Terms, definitions and abbreviations

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 definition
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
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 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 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 Dielectric_crossover_area

MIM element:	dielectric_crossover_area
Source:	ISO 10303-1684
Reference path:	[dielectric_crossover_area <= shape_aspect_relationship] [dielectric_crossover_area <= shape_aspect]

5.1.1.1 Dielectric_crossover_area to Stratum_feature (as related_concept)

MIM element:	PATH
Reference path:	dielectric_crossover_area <= shape_aspect_relationship shape_aspect_relationship.related_shape_aspect -> shape_aspect => stratum_feature

5.1.1.2 Dielectric_crossover_area to Stratum_feature (as relating_concept)

MIM element:	PATH
Reference path:	dielectric_crossover_area <= shape_aspect_relationship shape_aspect_relationship.relating_shape_aspect -> shape_aspect => stratum_feature

5.1.1.3 Dielectric_crossover_area to Stratum_feature (as resulting_dielectric_crossover)

MIM element:	PATH
Reference path:	dielectric_crossover_area <= shape_aspect <- shape_aspect_relationship.related_shape_aspect shape_aspect_relationship {shape_aspect_relationship shape_aspect_relationship.name = 'resulting dielectric crossover'} shape_aspect_relationship.relating_shape_aspect -> shape_aspect => stratum_feature

5.1.1.4 Dielectric_crossover_area to Geometric_model (as resulting_shape)

MIM element:	PATH
Reference path:	dielectric_crossover_area <= shape_aspect_relationship shape_definition = shape_aspect_relationship shape_definition characterized_definition = shape_definition characterized_definition <- property_definition.definition property_definition <- property_definition_representation.definition property_definition_representation property_definition_representation.used_representation -> representation

5.1.2 Direct_stratum_component_join_implementation

MIM element:	direct_stratum_component_join_implementation
Source:	ISO 10303-1684
Reference path:	direct_stratum_component_join_implementation <= shape_aspect_relationship

5.1.2.1 Direct_stratum_component_join_implementation to Stratum_embedded_physical_component_join_relationship (as topological_requirement)

MIM element:	PATH
Reference path:	direct_stratum_component_join_implementation <= shape_aspect_relationship shape_aspect_relationship.related_shape_aspect -> {shape_aspect shape_aspect.name = 'stratum embedded physical component join'} shape_aspect => join_shape_aspect

5.1.2.2 Direct_stratum_component_join_implementation to Fabrication_joint (as implementing_joint)

MIM element:	PATH
Reference path:	direct_stratum_component_join_implementation <= shape_aspect_relationship shape_aspect_relationship.relating_shape_aspect -> shape_aspect => component_feature_joint => fabrication_joint

5.1.3 Indirect_stratum_component_join_implementation

MIM element:	indirect_stratum_component_join_implementation
Source:	ISO 10303-1684
Reference path:	indirect_stratum_component_join_implementation <= plated_inter_stratum_feature

5.1.3.1 Indirect_stratum_component_join_implementation to Stratum_embedded_physical_component_join_relationship (as indirect_topological_requirement)

MIM element:

PATH

Reference path:

indirect_stratum_component_join_implementation <=
plated_inter_stratum_feature <=
inter_stratum_feature <=
laminate_component <=
assembly_component <=
product_definition_shape <-
shape_aspect.of_shape
shape_aspect <-
shape_aspect_relationship.related_shape_aspect
shape_aspect_relationship
{shape_aspect_relationship
shape_aspect_relationship.name = 'indirect topological requirement'}
shape_aspect_relationship.relating_shape_aspect ->
{shape_aspect
shape_aspect.name = 'stratum embedded physical component join'}
shape_aspect =>
join_shape_aspect

5.1.3.2 Indirect_stratum_component_join_implementation to Fabrication_joint (as implementing_joint)

MIM element:

PATH

Reference path:

indirect_stratum_component_join_implementation <=
plated_inter_stratum_feature <=
inter_stratum_feature <=
laminate_component <=
assembly_component <=
product_definition_shape <-
shape_aspect.of_shape
shape_aspect <-
shape_aspect_relationship.related_shape_aspect
shape_aspect_relationship
{shape_aspect_relationship
shape_aspect_relationship.name = 'implementing joint'}
shape_aspect_relationship.relating_shape_aspect ->
shape_aspect =>
component_feature_joint =>
fabrication_joint

5.1.4 Junction_vertex_allocation

MIM element:	shape_aspect_relationship
Source:	ISO 10303-41
Reference path:	{shape_aspect_relationship shape_aspect_relationship.name = 'junction vertex allocation'}

5.1.4.1 Junction_vertex_allocation to trace_junction_or_via (as implementation_point)

MIM element:	PATH
Reference path:	shape_aspect_relationship shape_aspect_relationship.related_shape_aspect -> shape_aspect

5.1.4.2 Junction_vertex_allocation to Explicitly_located_layer_connection_point (as implementation_point)

MIM element:	PATH
Reference path:	shape_aspect_relationship shape_aspect_relationship.related_shape_aspect -> shape_aspect => layer_connection_point

5.1.4.3 Junction_vertex_allocation to Inter_stratum_join_relationship (as implementation_point)

MIM element:	PATH
Reference path:	shape_aspect_relationship shape_aspect_relationship.related_shape_aspect -> shape_aspect => join_shape_aspect

5.1.4.4 Junction_vertex_allocation to Part_connected_terminals_topological_junction (as required_vertex)

MIM element:	PATH
Reference path:	shape_aspect_relationship shape_aspect_relationship.relating_shape_aspect -> shape_aspect {shape_aspect [shape_aspect.description = 'part connected terminals topological junction'] [shape_aspect.product_definitional = .TRUE.]}

5.1.5 Physical_connectivity_abstraction_map

MIM element:	shape_aspect_relationship
Source:	ISO 10303-41
Reference path:	{shape_aspect_relationship shape_aspect_relationship.name = 'physical to topological abstraction map'}

5.1.5.1 Physical_connectivity_abstraction_map to Conductive_interconnect_element_terminal_link (as geometric_context_based_definition)

MIM element:	PATH
Reference path:	shape_aspect_relationship shape_aspect_relationship.relating_shape_aspect -> shape_aspect => conductive_interconnect_element_terminal_link

5.1.5.2 Physical_connectivity_abstraction_map to Passage_terminal_based_fabrication_joint_link (as geometric_context_based_definition)

MIM element:	PATH
Reference path:	shape_aspect_relationship shape_aspect_relationship.relating_shape_aspect -> shape_aspect => passage_terminal_based_fabrication_joint_link

5.1.5.3 Physical_connectivity_abstraction_map to Part_connected_terminals_element (as name_space_context_based_definition)

MIM element:	PATH
Reference path:	shape_aspect_relationship shape_aspect_relationship.related_shape_aspect -> shape_aspect => part_connected_terminals_element

5.1.6 Physical_connectivity_element

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

5.1.6.1 Physical_connectivity_element to Inter_stratum_join_relationship (as start_terminus)

MIM element:	PATH
Reference path:	physical_connectivity_element <= shape_aspect_relationship {shape_aspect_relationship shape_aspect_relationship.name = 'start to end terminus'} shape_aspect_relationship.relating_shape_aspect -> shape_aspect => join_shape_aspect

5.1.6.2 Physical_connectivity_element to Explicitly_located_layer_connection_point (as start_terminus)

MIM element:	PATH
Reference path:	physical_connectivity_element <= shape_aspect_relationship {shape_aspect_relationship shape_aspect_relationship.name = 'start to end terminus'} shape_aspect_relationship.relating_shape_aspect -> shape_aspect => layer_connection_point

5.1.6.3 Physical_connectivity_element to Inter_stratum_join_relationship (as end_terminus)

MIM element:	PATH
Reference path:	physical_connectivity_element <= shape_aspect_relationship {shape_aspect_relationship shape_aspect_relationship.name = 'start to end terminus'} shape_aspect_relationship.relating_shape_aspect -> shape_aspect => join_shape_aspect

5.1.6.4 Physical_connectivity_element to Explicitly_located_layer_connection_point (as end_terminus)

MIM element:	PATH
Reference path:	physical_connectivity_element <= shape_aspect_relationship {shape_aspect_relationship shape_aspect_relationship.name = 'start to end terminus'} shape_aspect_relationship.relating_shape_aspect -> shape_aspect => layer_connection_point

5.1.7 Requirement_assignment

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

5.1.7.1 Requirement_assignment to Stratum_feature_conductive_join (as assigned_to)

Reference path:

requirement_assignment <-
requirement_assigned_object.assigned_group
requirement_assigned_object
requirement_assigned_object.items ->
requirement_assigned_item
requirement_assigned_item *> imcr_requirement_assigned_item
imcr_requirement_assigned_item = stratum_feature_conductive_join

5.1.7.2 Requirement_assignment to Dielectric_crossover_area (as assigned_to)

Reference path: