4 Information requirements

This clause specifies the information requirements for the Document definition 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.

The following EXPRESS specification begins the Document_definition_arm schema and identifies the necessary external references.

4.1 Required AM ARMs

The following EXPRESS interface statements specify the elements imported from the ARMs of other application modules.

EXPRESS specification:

*)
USE FROM Document_and_version_identification_arm;    --  ISO/TS 10303-1121



USE FROM External_item_identification_assignment_arm;    --  ISO/TS 10303-1128



USE FROM File_identification_arm;    --  ISO/TS 10303-1127



USE FROM Product_view_definition_arm;    --  ISO/TS 10303-1019
(*



NOTE 1   The schemas referenced above are specified in the following part of ISO 10303:

Document_and_version_identification_arm	ISO/TS 10303-1121
External_item_identification_assignment_arm	ISO/TS 10303-1128
File_identification_arm	ISO/TS 10303-1127
Product_view_definition_arm	ISO/TS 10303-1019

NOTE 2   See Annex C, Figures C.1and C.2 for a graphical representation of this schema.

4.2 ARM type definition

This subclause specifies the ARM type for this application module. The ARM type and definition is specified below.

4.2.1 document_location_select   

The document_location_select type is an extension of the external_identification_item type. It adds the data type Document_definition to the list of alternate data types.

EXPRESS specification:

*)
TYPE document_location_select = SELECT BASED_ON external_identification_item WITH
   (Document_definition);
END_TYPE;
(*

4.3 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.3.1 Digital_document_definition   

EXPRESS specification:

*)
ENTITY Digital_document_definition
  SUBTYPE OF (Document_definition);
  files : SET[0:?] OF Digital_file;
END_ENTITY;
(*

Attribute definitions:

files: the set of instances of Digital_file that provides the content of the digital document.

4.3.2 Document_definition   

A Document_definition is a type of Product_view_definition that is a Document_version in a particular format.

NOTE 1   A Document_version may have more than one representation.

EXAMPLE    A version of a logical document, which contains a shape model, may be represented in the native formats of different CAD systems.

Each Document_definition is a Digital_document_definition or a Physical_document_definition.

NOTE 2   Aspects of the representation may not be known at the time the identification is established.

EXPRESS specification:

*)
ENTITY Document_definition
  SUPERTYPE OF (ONEOF (Digital_document_definition,
                       Physical_document_definition))
  SUBTYPE OF (Product_view_definition);
  SELF\Product_view_definition.name RENAMED description : OPTIONAL STRING;
  SELF\Product_view_definition.defined_version RENAMED associated_document_version : Document_version;
END_ENTITY;
(*

Attribute definitions:

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

associated_document_version: the version of the logical document that is being represented.

4.3.3 Document_location_identification   

EXAMPLE 1   An HTML file that includes a picture may be represented as a Document_definition made of two components:

• the HTML file;
• the binary file that contains the picture.

If these files were located within the same directory or relatively to the same directory, the source_id attribute would convey the directory name.

EXAMPLE 2   Examples of source_type are:

• 'URL' - for a web page;
• 'FTP' - for an FTP address;
• 'ISBN' - for physical documents.

EXPRESS specification:

*)
ENTITY Document_location_identification
  SUBTYPE OF (External_source_identification);
WHERE
  WR1: 'DOCUMENT_DEFINITION_ARM.DOCUMENT_DEFINITION' IN TYPEOF(SELF\External_source_identification.item);
END_ENTITY;
(*

Formal propositions:

WR1: The identified external item shall be of type Document_definition.

4.3.4 Physical_document_definition   

EXAMPLE    Paper plots of technical drawings, micro fiche, or paper documents such as calculations or test reports are examples of Physical_document_definition.

EXPRESS specification:

*)
ENTITY Physical_document_definition
  SUBTYPE OF (Document_definition);
  components : SET[0:?] OF Hardcopy;
END_ENTITY;
(*

Attribute definitions:

components: the set of instances of Hardcopy that form the physical document.

4.4 ARM rule definition

This subclause specifies the ARM rule for this module. The ARM rule and definition is specified below.

4.4.1 document_definition_constraint

EXPRESS specification:

Argument definitions:

Product_view_definition : the set of all instances of Product_view_definition.

Formal propositions:

WR1: Every Product_view_definition referencing a Document_version is a Document_definition.

© ISO 2004 — All rights reserved