Нормативные ссылки(рекомендации). Термины, определенные в 10303-31. Прикладная модель деятельности (AAM), страница 18

ISO 10303-1:1994(E)                                                     ©ISO

subcommittee that prepares a standard in order to identify objects within the standard. Thus, ISO 10303 is identified by the object identifier:

{10 10303 }

Here the initial 1 indicates ISO; the 0 following it identifies the object as a standard, and the number following that is the number of the standard. ISO/IEC 8824-1 also defines identifiers to stand in the place of these numbers; thus 'iso' has the value 1 and 'standard' has the value 0. For multi-part standards, the next number is required to be the part number. Thus, this part of ISO 10303 is identified by the object identifier:

{ iso standard 10303 part(l) }

Here, the value of the part number is given explicitly, but the notation allows us to associate a term with this value, thereby providing some semantics. The notation for values of this type is defined in clause 28 of ISO/IEC 8824-1, and the predefined assignments are specified in annex B of ISO/IEC 8824-1.

For the purposes of identifying information objects unambiguously within an open information system, ISO 10303 adopts the following conventions:

— The value following the part number shall be version number. By convention, the value of the version number of the first edition shall be 1. The value 0, if used at all, is reserved to refer to DIS documents.

— The value following the version number is used to identify the type of information object defined within the part. The value 1 shall indicate that the object so identified is a schema.

— The value following the object type is an integer that identifies the instance of the object type so identified.

— To meet the syntactic requirements of ISO/IEC 8824-1, replace each occurrence of a low line in a schema name with a hyphen when defining this value.

EXAMPLE 1 - In ISO 10303-41, several schemas are defined. The application-context-schema can be identified by the value

{ iso standard 10303 part(41) version(l) object(l) application-context-schema(l) } and the product-definition schema can be identified by the value { iso standard 10303 part(41) version(l) object(l) product-definition-schema(2) }

5 Structure of ISO 10303

ISO 10303 is divided into six series of parts. Each series has a unique function. Each series may have one or more parts. The series are listed below with their numbering scheme:

— Description methods - Parts 11 to 19;

8

©ISO      ISO         10303-1:1994(E)

—   Integrated resources:

              • Generic resources - Parts 41 to 99;

              • Application resources - Parts 101 to 199;

—   Application protocols - Parts 201 to 1199;

—   Conformance testing methodology and framework - Parts 31 to 39;

—   Abstract test suites - Parts 1201 to 2199, corresponding to               the associated application protocols 201 to 1199;

—   Implementation methods - Parts 21 to 29.

6 Description methods

The description of product data in integrated resources and application protocols requires the use of formal data specification languages to ensure consistency and avoid ambiguity. The languages are intended to be both human-readable to facilitate human understanding and computer-interpretable to facilitate the generation of application software and supporting tools.

6.1 The EXPRESS language

EXPRESS is a formal data specification language, specified in ISO 10303-11, that provides the mechanism for the normative description of product data for both integrated resources and application protocols.

EXPRESS allows a description of the data and constraints applicable to product data. EXPRESS permits the definition of resource constructs from data elements, constraints, relationships, rules and functions. The language permits classification and structuring of resource constructs. Resource constructs may be interpreted within application protocols. The interpretation capability of EXPRESS is a mechanism to facilitate the development of application protocols by allowing the addition of restrictions on attributes, the addition of constraints, the addition of relationships among resource constructs and application constructs, or all of the above.

6.2 Graphical presentation of models

The graphical presentation of models to illustrate normative data definitions is informative in all cases. The four types of models within this International Standard using graphical presentations are:

— resource constructs within integrated resources;

— application activity models;

9