|
|
Application module:
Document structure |
ISO/TS 10303-1124:2004(E)
© ISO
|
This clause specifies the information requirements for the
Document structure
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_structure_arm
schema and identifies the necessary external references.
EXPRESS specification:
*)
SCHEMA Document_structure_arm;
(*
The following EXPRESS interface statements specify the elements
imported from the ARMs of other application modules.
EXPRESS specification:
*)
USE FROM
Document_definition_arm;
--
ISO/TS 10303-1123
USE FROM
File_identification_arm;
--
ISO/TS 10303-1127
(*
NOTE 1
The schemas referenced above are specified in the following
part of ISO 10303:
| Document_definition_arm |
ISO/TS 10303-1123 |
| File_identification_arm |
ISO/TS 10303-1127 |
NOTE 2
See Annex C,
Figures
C.1and C.2
for a graphical representation of this schema.
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.
A Document_definition_relationship is a relationship between two instances of Document_definition.
EXPRESS specification:
*)
ENTITY Document_definition_relationship;
relation_type : STRING;
description :
OPTIONAL
STRING;
relating_document_definition : Document_definition;
related_document_definition : Document_definition;
WHERE
WR1: relating_document_definition :<>: related_document_definition;
END_ENTITY;
(*
Attribute definitions:
relation_type:
the relation_type
specifies the meaning of the relationship.
Where applicable the following values shall be used:
- 'addition': The application object specifies that the related document provides supplementary or collateral information with
regard to the information provided by the relating document;
- 'copy': The application object defines a relationship where the related Document_definition is a copy of the relating Document_definition;
- 'decomposition': The application object defines a relationship where the related Document_definition is one of potentially more sub documents of the relating Document_definition;
EXAMPLE 1
The decomposition of a document into clauses is an example for the use of this value.
- 'derivation': The application object defines a relationship where the related Document_definition is derived from the relating Document_definition;
EXAMPLE 2
A raster image may be derived from a 3D CAD model.
EXAMPLE 3
A html version may be derived from a text document as an alternative.
- 'peer': The application object specifies that the related document provides required information with regard to that provided
by the relating document. The peer document is essential for a complete understanding;
- 'reference': The application object defines a relationship where the related document is referenced from the relating;
EXAMPLE 4
A hyperlink is an example for a 'reference'.
- 'sequence': The application object defines a logical sequence where the related Document_definition comes after the relating Document_definition;
EXAMPLE 5
A sequence of clauses.
- 'substitution': The application object defines a relationship where the related Document_definition replaces the relating Document_definition;
- 'translation': The Document_definition_relationship specifies that the related document is generated through a translation process from the relating document.
description:
the text that provides further information about the Document_definition_relationship.
The value of this attribute need not be specified.
relating_document_definition:
one of the instances of Document_definitionthat participate in the relationship.
related_document_definition:
the other instance of Document_definition that participates in the relationship.
If one element of the relationship is dependent upon the other, this attribute shall be the dependent one.
Formal propositions:
WR1:
A
Document_definition
shall not be related to itself.
A File_relationship is a relationship between two instances of File.
EXAMPLE 1
A service manual may contain graphics for explanatory reasons.
In this case, the File objects that contain the graphics are referenced as related from the File object that contains the
body of the service manual with relation_type 'reference'.
EXPRESS specification:
*)
ENTITY File_relationship;
relation_type : STRING;
description :
OPTIONAL
STRING;
relating_document_file : File;
related_document_file : File;
WHERE
WR1: relating_document_file:<>: related_document_file;
END_ENTITY;
(*
Attribute definitions:
relation_type:
the relation_type
is the meaning of the relationship.
Where applicable the following values shall be used:
- 'addition': The application object specifies that the related document provides supplementary or collateral information with
regard to the information provided by the relating document;
EXAMPLE 2
The recommended practices for this part of ISO 10303 may be an addition.
- 'copy': The application object defines a relationship where the related File is a copy of the relating File;
- 'decomposition': The application object defines a relationship where the related File is one of potentially more sub documents of the relating File;
EXAMPLE 3
The decomposition of a document into clauses or into several CAD models is an example for 'decomposition'.
- 'derivation': The application object defines a relationship where the related File is derived from the relating File;
EXAMPLE 4
The derivation of a hypertext document from an text document is an example for 'derivation'.
- 'peer': The application object specifies that the related document provides required information with regard to that provided
by the relating document. The peer document is essential for a complete understanding;
- 'reference': The application object defines a relationship where the related document is referenced from the relating one;
EXAMPLE 5
The link in a hypertext document may be a reference.
- 'sequence': The application object defines a logical sequence where the related File comes after the relating File;
EXAMPLE 6
A sequence of clauses is an example for 'sequence'.
- 'substitution': The application object defines a relationship where the related File replaces the relating File;
- 'translation': The application object specifies that the related document is generated through a translation process from
the relating document.
The values 'addition', 'decomposition', and 'peer' are used for the purpose of creating logical structures of documents.
These values shall only be used for the relation_type of Document_definition, if the referenced File objects do not participate in a Document_definition.
In the latter case, Document_definition_relationship shall be used instead.
description:
the
text that provides further information about the Document_definition. The value of this attribute need not be specified.
relating_document_file:
one instance of Filethat participates in the relationship.
related_document_file:
the other instance of File that participates in the relationship.
If one element of the relationship is dependent upon the other, this attribute shall be the dependent one.
Formal propositions:
WR1:
A File
shall not be related to itself.
*)
END_SCHEMA; -- Document_structure_arm
(*
© ISO 2004 — All rights reserved
