ISO/TS 10303-332:2002

TECHNICAL ISO/TS
SPECIFICATION 10303-332
First edition
2002-04-15
Industrial automation systems and
integration — Product data representation
and exchange —
Part 332:
Abstract test suite: Technical data
packaging core information and exchange
Systèmes d'automatisation industrielle et intégration — Représentation et
échange de données de produits —
Partie 332: Suite d'essai abstrait: Paquet de données techniques

Reference number
©
ISO 2002
PDF disclaimer
This PDF file may contain embedded typefaces. In accordance with Adobe's licensing policy, this file may be printed or viewed but shall not
be edited unless the typefaces which are embedded are licensed to and installed on the computer performing the editing. In downloading this
file, parties accept therein the responsibility of not infringing Adobe's licensing policy. The ISO Central Secretariat accepts no liability in this
area.
Adobe is a trademark of Adobe Systems Incorporated.
Details of the software products used to create this PDF file can be found in the General Info relative to the file; the PDF-creation parameters
were optimized for printing. Every care has been taken to ensure that the file is suitable for use by ISO member bodies. In the unlikely event
that a problem relating to it is found, please inform the Central Secretariat at the address given below.

©  ISO 2002
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or by any means, electronic
or mechanical, including photocopying and microfilm, without permission in writing from either ISO at the address below or ISO's member body
in the country of the requester.
ISO copyright office
Case postale 56 • CH-1211 Geneva 20
Tel. + 41 22 749 01 11
Fax + 41 22 749 09 47
E-mail copyright@iso.ch
Web www.iso.ch
Printed in Switzerland
ii © ISO 2002 – All rights reserved

Contents Page
1 Scope . 1
2 Normative references. 1
3 Terms, definitions, and abbreviations. 2
3.1 Terms defined in ISO 10303-1 . 2
3.2 Terms defined in ISO 10303-31 . 2
3.3 Terms defined in ISO 10303-232 . 3
3.4 Other terms and definitions . 3
3.5 Abbreviations . 4
4 Test purposes. 4
4.1 Application element test purposes. 5
4.2 AIM test purposes. 52
4.3 Implementation method test purposes . 53
4.4 Domain test purposes . 53
5 General test purposes and verdict criteria. 57
5.1 General test purposes. 57
5.2 General verdict criteria for all abstract test cases . 57
5.3 General verdict criteria for preprocessor abstract test cases. 57
5.4 General verdict criteria for postprocessor abstract test cases . 57
6 Abstract test cases. 58
6.1 1UoF_DDE_for_files . 59
6.2 2UoF_DDE_for_TDP_elements . 65
6.3 4UoF_PL1 . 73
6.4 4UoF_PL2 . 83
6.5 4SMPL_initial . 93
6.6 4SMPL_revised . 120
6.7 4SMPL_em. 153
6.8 4SMPL_instl_rqmts. 167
6.9 4SMPL_developmental . 192
6.10 6UoF_IDL1 . 208
6.11 6UoF_IDL2 . 215
6.12 6SCML_initial. 224
6.13 6SCML_revised. 244
6.14 6SCML_removeSCP . 264

Annex A (normative) Conformance classes. 276
A.1 Conformance class 1. 276
A.2 Conformance class 2. 276
A.3 Conformance class 3. 276
A.4 Conformance class 4. 276
A.5 Conformance class 5. 277
A.6 Conformance class 6. 277
A.7 Conformance class 7. 277
A.8 Conformance class 8. 277
A.9 Conformance class 9. 277
A.10 Conformance class 10. 277
A.11 Conformance class 11. 278
A.12 Conformance class 12. 278
A.13 Conformance class 13. 278
A.14 Conformance class 14. 278
Annex B (normative) Information object registration. 279
Annex C (normative) Computer interpretable postprocessor input specification . 280
Annex D (informative) Excluded test purposes. 281
Annex E (informative) Instance diagrams. 282
E.1 1UoF_DDE_for_files. 282
E.2 2UoF_DDE_for_TDP_elements. 283
E.3 4UoF_PL1. 284
E.4 4UoF_PL2. 286
E.5 4SMPL_initial. 288
E.6 4SMPL_revised. 296
E.7 4SMPL_em . 308
E.8 4SMPL_instl_rqmts . 312
E.9 4SMPL_developmental. 320
E.10 6UoF_IDL1. 325
E.11 6UoF_IDL2. 326
E.12 6SCML_initial . 328
E.13 6SCML_revised . 333
E.14 6SCML_removeSCP. 339
Bibliography. 341
Index. 342
Figures
Figure E. 1 – Instance diagram 1 of 59. 282
Figure E. 2 – Instance diagram 2 of 59. 283
Figure E. 3 – Instance diagram 3 of 59. 284
Figure E. 4 – Instance diagram 4 of 59. 285
Figure E. 5 – Instance diagram 5 of 59. 286
Figure E. 6 – Instance diagram 6 of 59. 287
Figure E. 7 – Instance diagram 7 of 59. 288
Figure E. 8 – Instance diagram 8 of 59. 289
Figure E. 9 – Instance diagram 9 of 59. 290
Figure E. 10 – Instance diagram 10 of 59. 291
Figure E. 11 – Instance diagram 11 of 59. 292
Figure E. 12 – Instance diagram 12 of 59. 293
Figure E. 13 – Instance diagram 13 of 59. 294
Figure E. 14 – Instance diagram 14 of 59. 295
Figure E. 15 – Instance diagram 15 of 59. 296
Figure E. 16 – Instance diagram 16 of 59. 297
iv © ISO 2002 – All rights reserved

Figure E. 17 – Instance diagram 17 of 59. 298
Figure E. 18 – Instance diagram 18 of 59. 299
Figure E. 19 – Instance diagram 19 of 59. 300
Figure E. 20 – Instance diagram 20 of 59. 301
Figure E. 21 – Instance diagram 21 of 59. 302
Figure E. 22 – Instance diagram 22 of 59. 303
Figure E. 23 – Instance diagram 23 of 59. 304
Figure E. 24 – Instance diagram 24 of 59. 305
Figure E. 25 – Instance diagram 25 of 59. 306
Figure E. 26 – Instance diagram 26 of 59. 307
Figure E. 27 – Instance diagram 27 of 59. 308
Figure E. 28 – Instance diagram 28 of 59. 309
Figure E. 29 – Instance diagram 29 of 59. 310
Figure E. 30 – Instance diagram 30 of 59. 311
Figure E. 31 – Instance diagram 31 of 59. 312
Figure E. 32 – Instance diagram 32 of 59. 313
Figure E. 33 – Instance diagram 33 of 59. 314
Figure E. 34 – Instance diagram 34 of 59. 315
Figure E. 35 – Instance diagram 35 of 59. 316
Figure E. 36 – Instance diagram 36 of 59. 317
Figure E. 37 – Instance diagram 37 of 59. 318
Figure E. 38 – Instance diagram 38 of 59. 319
Figure E. 39 – Instance diagram 39 of 59. 320
Figure E. 40 – Instance diagram 40 of 59. 321
Figure E. 41 – Instance diagram 41 of 59. 322
Figure E. 42 – Instance diagram 42 of 59. 323
Figure E. 43 – Instance diagram 43 of 59. 324
Figure E. 44 – Instance diagram 44 of 59. 325
Figure E. 45 – Instance diagram 45 of 59. 326
Figure E. 46 – Instance diagram 46 of 59. 327
Figure E. 47 – Instance diagram 47 of 59. 328
Figure E. 48 – Instance diagram 48 of 59. 329
Figure E. 49 – Instance diagram 49 of 59. 330
Figure E. 50 – Instance diagram 50 of 59. 331
Figure E. 51 – Instance diagram 51 of 59. 332
Figure E. 52 – Instance diagram 52 of 59. 333
Figure E. 53 – Instance diagram 53 of 59. 334
Figure E. 54 – Instance diagram 54 of 59. 335
Figure E. 55 – Instance diagram 55 of 59. 336
Figure E. 56 – Instance diagram 56 of 59. 337
Figure E. 57 – Instance diagram 57 of 59. 338
Figure E. 58 – Instance diagram 58 of 59. 339
Figure E. 59 – Instance diagram 59 of 59. 340
Tables
Table 1 – Application elements for 1UoF_DDE_for_files. 60
Table 2 – Application elements for 2UoF_DDE_for_TDP_elements. 66
Table 3 – Application elements for 4UoF_PL1. 73
Table 4 – Application elements for 4UoF_PL2. 83
Table 5 – Application elements for 4SMPL_initial. 94
Table 6 – Application elements for 4SMPL_revised . 121
Table 7 – Application elements for 4SMPL_em. 153
Table 8 – Application elements for 4SMPL_instl_rqmts. 168
Table 9 – Application elements for 4SMPL_developmental . 192
Table 10 – Application elements for 6UoF_IDL1. 208
Table 11 – Application elements for 6UoF_IDL2. 216
Table 12 – Application elements for 6SCML_initial . 225
Table 13 – Application elements for 6SCML_revised. 245
Table 14 – Application elements for 6SCML_removeSCP . 264
Table C.1 – Postprocessor input specification file names .277
vi © ISO 2002 – All rights reserved

Foreword
ISO (the International Organization for Standardization) is a worldwide federation of national
standards bodies (ISO member bodies). The work of preparing International Standards is normally
carried out through ISO technical committees. Each member body interested in a subject for which a
technical committee has been established has the right to be represented on that committee.
International organizations, governmental and non-governmental, in liaison with ISO, also take part in
the work. ISO collaborates closely with the International Electrotechnical Commission (IEC) on all
matters of electrotechnical standardization.
International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part
3.
The main task of technical committees is to prepare International Standards. Draft International
Standards adopted by the technical committees are circulated to the member bodies for voting.
Publication as an International Standard requires approval by at least 75 % of the member bodies
casting a vote.
In other circumstances, particularly when there is an urgent market requirement for such documents, a
technical committee may decide to publish other types of normative document:
— an ISO Publicly Available Specification (ISO/PAS) represents an agreement between technical
experts in an ISO working group and is accepted for publication if it is approved by more than
50 % of the members of the parent committee casting a vote;
— an ISO Technical Specification (ISO/TS) represents an agreement between the members of a
technical committee and is accepted for publication if it is approved by 2/3 of the members of the
committee casting a vote.
An ISO/PAS or ISO/TS is reviewed every three years with a view to deciding whether it can be
transformed into an International Standard.
Attention is drawn to the possibility that some of the elements of this part of ISO 10303 may be the
subject of patent rights. ISO shall not be held responsible for any or all such patent rights.
ISO/TS 10303-323 was prepared by Technical Committee ISO/TC 184, Industrial automation
systems and integration, Subcommittee SC 4, Industrial data.
This International Standard is organised as a series of parts, each published separately. The structure
of this International Standard is described in ISO 10303-1.
Each part of this International Standard is a member of one of the following series: description
methods, implementation methods, conformance testing methodology and framework, integrated
generic resources, integrated application resources, application protocols, abstract test suites,
application interpreted constructs, and application modules. This part is a member of the abstract test
suite series.
A complete list of parts of ISO 10303 is available from the Internet:

Annexes A, B and C form a normative part of this part of ISO 10303. Annexes D and E are for
information only.
viii © ISO 2002 – All rights reserved

Introduction
ISO 10303 is an International Standard for the computer-interpretable representation of product
information and for the exchange of product data. The objective is to provide a neutral mechanism
capable of describing products throughout their life cycle. This mechanism is suitable not only for
neutral file exchange, but also as a basis for implementing and sharing product databases, and as a
basis for archiving.
This part of ISO 10303 specifies the abstract test suite for ISO 10303-232, Application protocol:
Technical data packaging core information and exchange. The abstract test cases presented here are
the basis for conformance testing of implementations of ISO 10303-232.
The purpose of an abstract test suite is to provide a basis for evaluating whether a particular
implementation of an application protocol actually conforms to the requirements of that application
protocol. A standard abstract test suite helps ensure that evaluations of conformance are conducted in
a consistent manner by different test laboratories.
This abstract test suite is made up of two major parts:
— the test purposes, the specific items to be covered by conformance testing;
— the set of abstract test cases that meet those test purposes.
The test purposes are statements of the application protocol requirements that are to be addressed by
the abstract test cases. Test purposes are derived primarily from the application protocol’s information
requirements and AIM, as well as from other sources such as standards referenced by the application
protocol and requirements stated in the application protocol conformance requirements clause.
The abstract test cases address the test purposes by:
— specifying the requirements for input data to be used when testing an implementation of the
application protocol;
— specifying the verdict criteria to be used when evaluating whether the implementation
successfully converted the input data to a different form.
The abstract test cases set the requirements for the executable test cases that are required to actually
conduct a conformance test. Executable test cases contain the scripts, detailed values, and other
explicit information required to conduct a conformance test on a specific implementation of the
application protocol.
At the time of publication of this document, conformance testing requirements had been established
for implementations of application protocols in combination with ISO 10303-21 and ISO 10303-22.
This part of ISO 10303 only specifies test purposes and abstract test cases for a subset of such
implementations.
NOTE ISO TC184/SC4 has prepared Standing Documents [1] and [2] for documenting abstract test suites that
are prepared as International Standards. Subsequent ISO TC184/SC4 resolutions allow abstract test suites to be
prepared as Technical Specifications. This part of ISO 10303 was documented as a Technical Specification
using the ISO TC184/SC4 Standing Documents [1] and [2] as a guide. Primary reliance was placed on [2].
Portions of this part of ISO 10303 that relied on [1] are identified in NOTEs in the appropriate clause or
subclause. Technical differences in documentation of abstract test suites from the Standing Documents [1] and
[2] are identified in NOTEs throughout this part of ISO 10303. Editorial differences in documentation are not
identified in this part of ISO 10303.
For ISO 10303-21, two kinds of implementations, preprocessors and postprocessors, must be tested.
Both these are addressed in this abstract test suite.
For ISO 10303-22, a class of applications will possess the capability to upload and download AP-
compliant SDAI-models or schema instances to and from applications that implement the SDAI. By
providing test case data that correspond with SDAI-models, this abstract test suite addresses such
applications in a single-schema scenario.
x © ISO 2002 – All rights reserved

TECHNICAL SPECIFICATION ISO/TS 10303-332:2002(E)
Industrial automation systems and integration —
Product data representation and exchange —
Part 332:
Abstract test suite: Technical data packaging core
information and exchange
1 Scope
This part of ISO 10303 specifies the abstract test suite to be used in the conformance testing of
implementations of ISO 10303-232. The following are within the scope of this part of ISO 10303:
— the specification of the test purposes associated with ISO 10303-232;
— the verdict criteria to be applied during conformance testing of an implementation of ISO 10303-
232 using ISO 10303-21 or ISO 10303-22;
NOTE The verdict criteria are used to ascertain whether a test purpose has been satisfactorily met by an
implementation under test (IUT) within the context of a given test case.
— the abstract test cases to be used as the basis for the executable test cases for conformance testing.
The following are outside the scope of this part of ISO 10303:
— the creation of executable test cases;
— test specifications for tests other than conformance testing such as interoperability or acceptance
testing;
— other implementation methods.
2 Normative references
The following normative documents contain provisions which, through reference in this text,
constitute provisions of this part of ISO 10303. For dated references, subsequent amendments to, or
revisions of, any of these publications do not apply. However, parties to agreements based on this part
of ISO 10303 are encouraged to investigate the possibility of applying the most recent editions of the
normative documents indicated below. For undated references, the latest edition of the normative
document referred to applies. Members of ISO and IEC maintain registers of currently valid
International Standards.
ISO 10303-1:1994, Industrial automation systems and integration — Product data representation and
exchange — Part 1: Overview and fundamental principles
ISO 10303-11:1994, Industrial automation systems and integration — Product data representation
and exchange — Part 11: Description methods: The EXPRESS language reference manual
 ISO 2002 - All rights reserved 1

ISO 10303-21:2002, Industrial automation systems and integration — Product data representation
and exchange — Part 21: Implementation methods: Clear text encoding of the exchange structure
ISO 10303-22:1998, Industrial automation systems and integration — Product data representation
and exchange — Part 22: Implementation methods: Standard data access interface
ISO 10303-31:1994, Industrial automation systems and integration — Product data representation
and exchange — Part 31: Conformance testing methodology and framework: General concepts
ISO 10303-32:1998, Industrial automation systems and integration — Product data representation
and exchange — Part 32: Conformance testing methodology and framework: Requirements on testing
laboratories and clients
ISO 10303-34:2001, Industrial automation systems and integration — Product data representation
and exchange — Part 34: Conformance testing methodology and framework: Abstract test methods
for application protocol implementations
ISO 10303-232:2002, Industrial automation systems and integration — Product data representation
and exchange — Part 232: Application protocol: Technical data packaging core information and
exchange
ISO/IEC 8824-1:1998, Information technology — Abstract Syntax Notation One (ASN.1): Specification
of basic notation
3 Terms, definitions, and abbreviations
3.1 Terms defined in ISO 10303-1
For the purpose of this part of ISO 10303, the following terms defined in ISO 10303-1 apply.
— abstract test suite (ATS);
— application protocol (AP);
— implementation method.
3.2 Terms defined in ISO 10303-31
For the purpose of this part of ISO 10303, the following terms defined in ISO 10303-31 apply.
— abstract test case (ATC);
— conformance testing;
— executable test case;
— implementation under test (IUT);
— postprocessor;
— preprocessor;
2  ISO 2002 - All rights reserved

— test purpose;
— verdict criterion.
3.3 Terms defined in ISO 10303-232
For the purpose of this part of ISO 10303, the following terms defined in ISO 10303-232 apply.
— associated list;
— data definition exchange (DDE);
— data list;
— indentured data list;
— index list;
— parts list;
— TDP element;
— technical data package (TDP).
3.4 Other terms and definitions
For the purposes of this part of ISO 10303, the following definitions apply.
3.4.1
application element
an application object, attribute, or assertion defining the information requirements in clause 4 of an
application protocol.
3.4.2
application element test purpose
a test purpose derived from the application elements in the ARM of an application protocol.
3.4.3
application interpreted model test purpose
a test purpose derived from the AIM EXPRESS schema of an application protocol.
3.4.4
domain test purpose
a test purpose that arises from the requirements that are implicit in an application protocol and derived
from usage scenarios and the process and information flows in the application domain of an
application protocol.
3.4.5
external reference test purpose
test purpose derived from requirements that arise from standards referenced by an application
protocol.
 ISO 2002 - All rights reserved 3

3.4.6
input specification
the instance model of an abstract test case presented in an unambiguous form, the table format for
preprocessors and physical files (ISO 10303-21).
3.5 Abbreviations
AE application element
AIM application interpreted model
AP application protocol
ARM application reference model
ATS abstract test suite
CC conformance class
IUT implementation under test
TDP technical data package
UoF unit of functionality
4 Test purposes
NOTE 1 Portions of this clause have been written in accordance with the Guidelines for the development of
abstract test suites [1].
This clause specifies the test purposes for this part of ISO 10303. Clauses 4.1 and 4.2 describe the
source and meaning of test purposes that are derived from the information requirement defined in ISO
10303-232, clause 4, and the AIM EXPRESS schema defined in ISO 10303-232, annex A. Each test
purpose statement identifies some specific element from the application elements or the AIM. Every
test purpose statement implicitly requires that the identified element, as specified in the test purpose
statement, will be correctly instantiated by the implementation under test in at least one test case
within the test suite.
Implementation method test purposes in 4.3 are derived from ISO 10303-21. Domain test purposes in
4.4 are derived from implicit domain requirements in the AP that are not clearly specified at the ap-
plication element level. The primary source of these implicit domain requirements is optional map-
pings specified in ISO 10303-232, clause 5.1. Implementation method and domain test purposes are
individually identified by the prefix “other” in the test purpose number. These test purposes are
statements of requirements that shall be met by a conforming implementation.
NOTE 2 Not all test purposes are covered by an abstract test case in clause 6 of this edition of this part of ISO
10303. Additional test cases will be added to a future edition to provide more complete coverage of the test pur-
poses.
4  ISO 2002 - All rights reserved

4.1 Application element test purposes
NOTE 1 This clause has been written in accordance with the Guidelines for the development of abstract test
suites [1].
AE test purposes are individually identified by the prefix “ae” in the test purpose number. Each test
purpose derived from the information requirements shall be interpreted as given in the following
statement: the IUT shall preserve the semantics associated with the unique application element from
which the test purpose was derived. This implies that the semantics of the application element are pre-
served by the IUT between the input and output of a test, according to the reference path specified in
the mapping table of the AP. AE test purposes apply to the input specifications of both preprocessor
and postprocessor test cases. AE test purposes are derived from the AP information requirements as
follows:
— application objects (see 4.2 of ISO 10303-232). A test purpose derived from an application object
is a simple statement of the object's name. Each application object test purpose is documented in a
separate subclause.
NOTE 2 The following application objects function as simple type attributes and do not have separate, derived
test purposes: A_number, A_real, An_integer, Identifier, Label, Measure, and Text. See notes 2 and 3 below.
— application objects with categorisations (subtypes) (see 4.2 of ISO 10303-232). Test purposes
derived from application objects with categorisations are statements of the application object
name as a specific subtype.
— application object attributes (see 4.2 of ISO 10303-232). Test purposes derived from application
object attributes are statements of the application object name with a specific attribute name.
NOTE 3 Only the application object attributes whose type is one of the application objects identified in note 1
have test purposes of this kind.
— application assertions (see 4.3 of ISO 10303-232). Test purposes derived from application asser-
tions are statements describing the relationship between two application objects. Application as-
sertion test purposes address the directions of relationships as well as the number (cardinality) of
relationships.
NOTE 4 Application assertions that involve one of the application objects identified in note 1 do not have test
purposes.
Each application object test purpose is listed as a separate subclause, with its related application ob-
ject attribute test purposes and assertion test purposes.
4.1.1 Accessed_file
ae1 Accessed_file
ae2 Accessed_file with path_information not present
ae3 Accessed_file with path_information
ae4 Accessed_file with storage_node_identification not present
ae5 Accessed_file with storage_node_identification
ae6 Accessed_file is entry_files for one Data_definition_entry_item
ae7 Accessed_file is entry_files for many Data_definition_entry_item objects
 ISO 2002 - All rights reserved 5

ae8 Accessed_file is entry_files for one Data_definition_entry_tdp_element
ae9 Accessed_file is entry_files for many Data_definition_entry_tdp_element objects
ae10 Accessed_file is file_entries for one Simple_list_of_files
ae11 Accessed_file is file_entries for many Simple_list_of_files objects
4.1.2 Alternate_element_identification
ae12 Alternate_element_identification
ae13 Alternate_element_identification with identifying_number
ae14 Alternate_element_identification with title not present
ae15 Alternate_element_identification with title
ae16 Alternate_element_identification has change_status of zero Change_identification
ae17 Alternate_element_identification has change_status of one Change_identification
ae18 Alternate_element_identification has design_activity of one Design_authority
ae19 Alternate_element_identification has element_classifications of zero Element_type
ae20 Alternate_element_identification has element_classifications of one Element_type
ae21 Alternate_element_identification has element_classifications of many Element_type objects
ae22 Alternate_element_identification has outstanding_changes of zero Other_reference_document
ae23 Alternate_element_identification has outstanding_changes of one Other_reference_document
ae24 Alternate_element_identification has outstanding_changes of many Other_reference_document
objects
ae25 Alternate_element_identification is alternate_identifications for one Element_identification
ae26 Alternate_element_identification is alternate_identifications for many Element_identification
objects
4.1.3 Alternate_identification_of_item
ae27 Alternate_identification_of_item
ae28 Alternate_identification_of_item with identifying_number of one Identifier
ae29 Alternate_identification_of_item has identifying_number of one
item_identifying_number_select as Drawing_suffix_number_combination
ae30 Alternate_identification_of_item with nomenclature_or_name not present
ae31 Alternate_identification_of_item with nomenclature_or_name
ae32 Alternate_identification_of_item has change of zero Change_identification
ae33 Alternate_identification_of_item has change of one Change_identification
ae34 Alternate_identification_of_item has classifications of zero Item_type
ae35 Alternate_identification_of_item has classifications of one Item_type
ae36 Alternate_identification_of_item has classifications of many Item_type objects
ae37 Alternate_identification_of_item has design_activity of one Design_authority
ae38 Alternate_identification_of_item has source_information of zero Source_information_type
ae39 Alternate_identification_of_item has source_information of one Source_information_type
ae40 Alternate_identification_of_item is alternate_identifications for one Item_identification
ae41 Alternate_identification_of_item is alternate_identifications for many Item_identification
objects
4.1.4 Alternate_item
ae42 Alternate_item
ae43 Alternate_item with type_of_alternate not present
ae44 Alternate_item with type_of_alternate
6  ISO 2002 - All rights reserved

ae45 Alternate_item with usage_conditions not present
ae46 Alternate_item with usage_conditions of one An_integer
ae47 Alternate_item with usage_conditions of many An_integer elements
ae48 Alternate_item with usage_conditions of one Text
ae49 Alternate_item with usage_conditions of many Text elements
ae50 Alternate_item has interchange_item of one usage_context as Item
ae51 Alternate_item has interchange_item of one usage_context as Item_usage
ae52 Alternate_item is alternates for one Item
ae53 Alternate_item is alternates for many Item objects
4.1.5 Annotation
ae54 Annotation
ae55 Annotation has annotation_geometry of zero Geometry
ae56 Annotation has annotation_geometry of one Geometry
ae57 Annotation is annotation_presentation for one Product_presentation
ae58 Annotation is annotation_presentation for many Product_presentation objects
4.1.6 Approval
ae59 Approval
ae60 Approval with purpose_of
ae61 Approval has approval_date of one Date
ae62 Approval has person_organization of zero Person_and_organization
ae63 Approval has person_organization of one Person_and_organization
ae64 Approval is approval_of_configuation for one Product_configuration
ae65 Approval is approval_of_configuation for many Product_configuration objects
ae66 Approval is effectivity_approvals for one Effectivity
ae67 Approval is effectivi
...