Application module: Class ISO/TS 10303-1070:2014-02(E)
© ISO

Cover page
Table of contents
Copyright
Foreword
Introduction
1 Scope
2 Normative references
3 Terms, definitions and abbreviated terms
    3.1 Terms and definitions
    3.2 Abbreviated terms

4 Information requirements
   4.1 ARM entity definitions
5 Module interpreted model
   5.1 Mapping specification
   5.2 MIM EXPRESS short listing

A MIM short names
B Information object registration
C ARM EXPRESS-G   EXPRESS-G
D MIM EXPRESS-G   EXPRESS-G
E Computer interpretable listings
F Change history
Bibliography
Index

4 Information requirements

This clause specifies the information requirements for the Class application module. The information requirements are specified as the Application Reference Model (ARM) of this application module.

NOTE 1  A graphical representation of the information requirements is given in Annex C.

NOTE 2  The mapping specification is specified in 5.1. It shows how the information requirements are met by using common resources and constructs defined or imported in the MIM schema of this application module.

This clause defines the information requirements to which implementations shall conform using the EXPRESS language as defined in ISO 10303-11. The following begins the Class schema.

EXPRESS specification:

*)
SCHEMA Class_arm;
(*

4.1 ARM entity definitions

This subclause specifies the ARM entities for this module. Each ARM application entity is an atomic element that embodies a unique application concept and contains attributes specifying the data elements of the entity. The ARM entities and definitions are specified below.

4.1.1 Class   EXPRESS-GMapping table

A Class is a number of things considered together.

NOTE 1   In this part of ISO 10303, the term 'class' and 'set' are synonyms.

NOTE 2   A class can consist of all things with a particular set of properties. Hence information about the consequences of possessing the set of properties can be assigned to the class.

If a thing is classified as being a member of such a class, then a set of properties possessed by the thing can be deduced.

NOTE 3   This entity may be instantiated as a compound instance involving another entity from ISO 10303.

Each Class is a Class_by_extension or a Class_by_intension

NOTE 4   The distinction between a Class_by_extension and a Class_by_intension can be imprecise. For example, the set of items produced by a particular production run could be regarded as either. The entity type class is not specified as abstract, so an application protocol or application module can decide to ignore the distinction.

EXPRESS specification:

*)
ENTITY Class
  SUPERTYPE OF (ONEOF (Class_by_extension,
                       Class_by_intension));
  id : STRING;
  name : STRING;
  description : OPTIONAL STRING;
END_ENTITY;
(*

Attribute definitions:

id: the identifier that distinguishes the Class.

name: the word or words by which the Class is known.

description: the text that provides further information about the Class. The value of this attribute need not be specified.

4.1.2 Class_by_extension   EXPRESS-GMapping table

A Class_by_extension is a type of Class that is a set that is defined by means of a criterion that does not enumerate the members.

EXPRESS specification:

*)
ENTITY Class_by_extension
  SUBTYPE OF (Class);
END_ENTITY;
(*

4.1.3 Class_by_intension   EXPRESS-GMapping table

A Class_by_intension is a type of Class that is a set that is defined by enumerating the members.

EXPRESS specification:

*)
ENTITY Class_by_intension
  SUBTYPE OF (Class);
END_ENTITY;
(*



*)
END_SCHEMA;  -- Class_arm
(*


© ISO 2014 — All rights reserved