ISO 10303-214:2010(E)
The following note correspond to the footnotemarks listed in the Table 30.NOTE 1 If collection_definition is also of type assembly_definition and/or mating_definition, it is assumed, that only one of the attributes collection_definition.purpose, assembly_definition.assembly_type, or mating_definition.mating_type is instantiated.
NOTE 2 Permissive list value 'version hierarchy' in ARM renamed to 'hierarchy' as product_definition_formation_relationship already implies a relationship between two version objects.
NOTE 3 Permissive list value 'version sequence' in ARM renamed to 'sequence' as product_definition_formation_relationship already implies a relationship between two version objects.
NOTE 4 The optional attribute cartesian_transformation_operator.scl is omitted
NOTE 5 The optional attribute cartesian_transformation_operator.scl is omitted
NOTE 6 Due to the SET, there is no order or specific semantics related to the usage of relating_product_concept_feature or related_product_concept_feature.
NOTE 7 In case the SET of operands is greater than two, a tree structure has to be built using the constructs stated in the parentheses. In this case, all concept_feature_relationship_with_condition instances used reference the same concept_feature_operator as the conditional_operator.
NOTE 8 Due to the SET, there is no order or specific semantics related to the usage of relating_product_concept_feature or related_product_concept_feature.
NOTE 9 In case the SET of operands is greater than two, a tree structure has to be built using the constructs stated in the parentheses.
© ISO 2010 — All rights reserved