ISO 10303-214:2010(E)
The implementation method defines what types of exchange behaviour are required with respect to this part of ISO 10303.
For various reasons, there may be some entities that cannot be completely instantiated in any implementation method (ISO 10303-2x). In the AIM there may be mandatory information that has no correspondence in the ARM. Sometimes an application may not maintain all the information that is anticipated for the data exchange. Other times, the information may be maintained by a sending system but not included in the data exchange. Never the less, the preprocessor must provide values for all mandatory attributes in an exchange file. When no data is provided by a sending system for a string value, the preprocessor shall use '/NULL' or the empty string ''.
To further indicate the reason why no data is provided, the following convention shall be used:
In general, the empty null string '' or the default string '/NULL' shall not be used as valid user data.
In case a mandatory AIM instance has no ARM correspondence through the mapping and no useful values can be provided the AIM instance shall be created with minimal 'dummy' information:
EXAMPLE The following cases give examples for such required '' 'dummy' AIM instances:
For an exchange structure, the file format shall be encoded according to the syntax and EXPRESS language mapping defined in ISO 10303–21 and the AIM defined in annex A of this part of ISO 10303. The header of the exchange structure shall identify use of this part of ISO 10303 by the schema name 'automotive_design' and include the object information identifier (see annex E).
EXAMPLE The instance below identifies the automotive_design extended schema of the 2001 edition
FILE_SCHEMA (('AUTOMOTIVE_DESIGN { 1 0 10303 214 1 1 1} ')).The exchange structure shall not make use of the SCOPE construct.
© ISO 2010 — All rights reserved