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 attribute 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:

5.1.1 Basic_multi_stratum_printed_part_template

5.1.1.1 Basic_multi_stratum_printed_part_template to Library_stack_model (as material_stack)

5.1.1.2 Basic_multi_stratum_printed_part_template to Stratum_feature_template (as reference_template)

5.1.2 Functional_usage_view_to_printed_part_template_terminal_assignment

5.1.2.1 Functional_usage_view_to_printed_part_template_terminal_assignment to Printed_part_template_terminal (as physical_usage_view_terminal)

5.1.2.2 Functional_usage_view_to_printed_part_template_terminal_assignment to Scalar_terminal_definition (as functional_usage_view_terminal)

5.1.3 Multi_stratum_printed_part_template

5.1.4 Non_conductive_cross_section_template

5.1.4.1 Non_conductive_cross_section_template to Length_data_element (as nominal_width)

5.1.4.2 Non_conductive_cross_section_template to Stratum_technology (as template_technology)

5.1.5 Printed_connector_template

5.1.6 Printed_connector_template_terminal_relationship

5.1.6.1 Printed_connector_template_terminal_relationship to Printed_connector_template (as connector)

5.1.6.2 Printed_connector_template_terminal_relationship to Printed_part_template_interface_terminal (as interface_terminal)

5.1.6.3 Printed_connector_template_terminal_relationship to Printed_part_template_join_terminal (as join_terminal)

5.1.7 Printed_part_cross_section_template

5.1.7.1 Printed_part_cross_section_template to Analytical_model_application (as maximum_transmission_line_characteristic)

5.1.7.2 Printed_part_cross_section_template to Analytical_model_application (as minimum_transmission_line_characteristic)

5.1.7.3 Printed_part_cross_section_template to Analytical_model_definition (as transmission_line_model)

5.1.7.4 Printed_part_cross_section_template to Length_data_element (as unit_length)

5.1.7.5 Printed_part_cross_section_template to Length_tolerance_characteristic (as width)

5.1.7.6 Printed_part_cross_section_template to Printed_part_template_material_link (as horizontal_material_link)

5.1.7.7 Printed_part_cross_section_template to Printed_part_template_material_link (as vertical_material_link)

5.1.8 Printed_part_cross_section_template_terminal

5.1.8.1 Printed_part_cross_section_template_terminal to Printed_part_cross_section_template (as associated_definition)

5.1.8.2 Printed_part_cross_section_template_terminal to Printed_part_template_material_link (as material_to_bottom_of_terminal)

5.1.8.3 Printed_part_cross_section_template_terminal to Printed_part_template_material_link (as material_to_left_of_terminal)

5.1.8.4 Printed_part_cross_section_template_terminal to Printed_part_template_material_link (as material_to_right_of_terminal)

5.1.8.5 Printed_part_cross_section_template_terminal to Printed_part_template_material_link (as material_to_top_of_terminal)

5.1.9 Printed_part_template

5.1.9.1 Printed_part_template to Functional_unit_usage_view (as implemented_function)

5.1.10 Printed_part_template_connected_terminals_definition

5.1.10.1 name

5.1.10.2 Printed_part_template_connected_terminals_definition to Printed_part_template_terminal (as connected_terminals)

5.1.11 Printed_part_template_interface_terminal

5.1.11.1 Printed_part_template_interface_terminal to Printed_connector_template (as associated_definition)

5.1.12 Printed_part_template_join_terminal

5.1.13 Printed_part_template_material

5.1.13.1 Printed_part_template_material to Length_tolerance_characteristic (as width)

5.1.13.2 Printed_part_template_material to Stratum_technology (as required_material)

5.1.14 Printed_part_template_material_link

5.1.14.1 Printed_part_template_material_link to Template_material_cross_section_boundary (as precedent_material)

5.1.14.2 Printed_part_template_material_link to Template_material_cross_section_boundary (as subsequent_material)

5.1.15 Printed_part_template_terminal

5.1.15.1 connection_zone_category

5.1.15.2 Printed_part_template_terminal to Connection_zone_in_layout_template (as connection_area)

5.1.15.3 Printed_part_template_terminal to Printed_part_template (as associated_definition)

5.1.16 Printed_tiebar_template

5.1.17 Single_stratum_printed_part_template

5.1.18 Structured_printed_part_template

5.1.19 Structured_printed_part_template_terminal

5.1.19.1 Structured_printed_part_template_terminal to Structured_printed_part_template (as associated_definition)

5.1.19.2 Structured_printed_part_template_terminal to Template_location_in_structured_template (as associated_composition_relationship)

5.1.20 Template_material_cross_section_boundary

5.1.20.1 Template_material_cross_section_boundary to Printed_part_template_material (as associated_definition2)

5.1.21 Usage_concept_usage_relationship

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

5.1.21.1 Usage_concept_usage_relationship to Printed_part_template_terminal (as associated_usage)

© ISO 2021 — All rights reserved