ISO/TS 10303-1123:2004 Document definition


Application module: Document definition	ISO/TS 10303-1123:2004(E) © ISO

Cover page
Table of contents
Copyright
Foreword
Introduction
1 Scope
2 Normative references
3 Terms, definitions and abbreviations

4 Information requirements
4.1 Required AM ARMs
4.2 ARM type definition
4.3 ARM entity definitions
4.4 ARM rule definition
5 Module interpreted model
5.1 Mapping specification
5.2 MIM EXPRESS short listing
5.2.1 MIM type definition

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

5.1 Mapping specification

In the following, "Application element" designates any entity data type defined in Clause 4, any of its explicit attributes and any subtype constraint. "MIM element" designates any entity data type defined in Clause 5.2 or imported with a USE FROM statement, from another EXPRESS schema, any of its attributes and any subtype constraint defined in Clause 5.2 or imported with a USE FROM statement.

This clause contains the mapping specification that defines how each application element of this part of ISO 10303 (see Clause 4) maps to one or more MIM elements (see Clause 5.2).

The mapping for each application element is specified in a separate subclause below. The mapping specification of an attribute of an ARM entity is a subclause of the clause that contains the mapping specification of this entity. Each mapping specification subclause contains up to five elements.

Title: The clause title contains:

the name of the considered ARM entity or subtype constraint, or
the name of the considered ARM entity atribute when this attribute refers to a type that is not an entity data type or a SELECT type that contains or may contain entity data types, or
a composite expression, <attribute name> to <referred type>, when this attribute refers to a type that is not an entity data type or a SELECT type that contains or may contain entity data types.

MIM element: This section contains, depending on the considered application element:

the name of one or more MIM entity data types;
the name of a MIM entity attribute, presented with the syntax <entity name>.<attribute name>, when the considered ARM attribute refers to a type that is not an entity data type or a SELECT type that contains or may contain entity data types;
the term PATH, when the considered ARM entity attribute refers to an entity data type or to a SELECT type that contains or may contain entity data types;
the term IDENTICAL MAPPING, when both application objects involved in an application assertion map to the same instance of a MIM entity data type;
the syntax /SUPERTYPE(<supertype name>)/, when the considered ARM entity is mapped as its supertype;
one or more constructs /SUBTYPE(<subtype name>)/, when the mapping of the considered ARM entity is the union of the mapping of its subtypes.

When the mapping of an application element involves more than one MIM element, each of these MIM elements is presented on a separate line in the mapping specification, enclosed between parentheses or brackets.

Source: This section contains:

the ISO standard number and part number in which the MIM element is defined, for those MIM elements that are defined in a common resource document;
the ISO standard number and part number of this part of ISO 10303, for those MIM elements that are defined in the MIM schema of this part.

This section is omitted when the keywords PATH or IDENTICAL MAPPING are used in the MIM element section.

Rules: This section contains the name of one or more global rules that apply to the population of the MIM entity data types listed in the MIM element section or in the reference path. When no rule applies, this section is omitted.

A reference to a global rule may be followed by a reference to the subclause in which the rule is defined.

Constraint: This section contains the name of one or more subtype constraints that apply to the population of the MIM entity data types listed in the MIM element section or in the reference path. When no subtype constraint applies, this section is omitted.

A reference to a subtype constraint may be followed by a reference to the subclause in which the subtype constraint is defined.

Reference path: This section contains:

the reference path to its supertypes in the common resources, for each MIM element created within this part of ISO 10303;
the specification of the relationships between MIM elements, when the mapping of an application element requires to relate instances of several MIM entity data types. In such a case, each line in the reference path documents the role of a MIM element relative to the referring MIM element or to the next referred MIM element.

For the expression of reference paths and of the constraints between MIM elements, the following notational conventions apply:

[]	enclosed section constrains multiple MIM elements or sections of the reference path are required to satisfy an information requirement;
()	enclosed section constrains multiple MIM elements or sections of the reference path are identified as alternatives within the mapping to satisfy an information requirement;
{}	enclosed section constrains the reference path to satisfy an information requirement;
<>	enclosed section constrains at one or more required reference path;
\|\|	enclosed section constrains the supertype entity;
->	the attribute, whose name precedes the -> symbol, references the entity or select type whose name follows the -> symbol;
<-	the entity or select type, whose name precedes the <- symbol, is referenced by the entity attribute whose name follows the <- symbol;
[i]	the attribute, whose name precedes the [i] symbol, is an aggregate; any element of that aggregate is referred to;
[n]	the attribute, whose name precedes the [n] symbol, is an ordered aggregate; member n of that aggregate is referred to;
=>	the entity, whose name precedes the => symbol, is a supertype of the entity whose name follows the => symbol;
<=	the entity, whose name precedes the <= symbol, is a subtype of the entity whose name follows the <= symbol;
=	the string, select, or enumeration type is constrained to a choice or value;
\	the reference path expression continues on the next line;
*	one or more instances of the relationship entity data type may be assembled in a relationship tree structure. The path between the relationship entity and the related entities, is enclosed with braces;
--	the text following is a comment or introduces a clause reference;
*>	the select or enumeration type, whose name precedes the > symbol, is extended into the select or enumeration type whose name follows the > symbol;
<*	the select or enumeration type, whose name precedes the <* symbol, is an extension of the select or enumeration type whose name follows the <* symbol.

The definition and use of mapping templates is not supported in the present version of the application modules. However, use of predefined templates /SUBTYPE/ and /SUPERTYPE/ is supported.

5.1.1 Document_definition

MIM element:	product_definition
Source:	ISO 10303-41
Rules:	restrict_document_definition_category
Reference path:	{product_definition product_definition.frame_of_reference -> product_definition_context <= application_context_element (application_context_element.name = 'digital document definition') (application_context_element.name = 'physical document definition')}

5.1.1.1 Document_definition to Document_version (as associated_document_version)

MIM element:

PATH

Reference path:

product_definition
{product_definition.frame_of_reference ->
product_definition_context <=
application_context_element
(application_context_element.name = 'digital document definition')
(application_context_element.name = 'physical document definition')}
{product_definition.formation -> product_definition_formation
product_definition_formation.of_product ->
product <-
product_related_product_category.products
product_related_product_category <=
product_category
product_category.name='document'}

5.1.2 Digital_document_definition

MIM element:	product_definition
Source:	ISO 10303-41
Reference path:	{product_definition product_definition.frame_of_reference -> product_definition_context <= application_context_element application_context_element.name = 'digital document definition'}

5.1.2.1 Digital_document_definition to Digital_file (as files)

MIM element:	PATH
Reference path:	product_definition => product_definition_with_associated_documents product_definition_with_associated_documents.documentation_ids[i] -> document {document <- document_representation_type.represented_document document_representation_type.name = 'digital'} document => document_file

5.1.3 Physical_document_definition

MIM element:	product_definition
Source:	ISO 10303-41
Reference path:	{product_definition product_definition.frame_of_reference -> product_definition_context <= application_context_element application_context_element.name = 'physical document definition'}

5.1.3.1 Physical_document_definition to Hardcopy (as components)

MIM element:	PATH
Reference path:	product_definition => product_definition_with_associated_documents product_definition_with_associated_documents.documentation_ids[i] -> document {document <- document_representation_type.represented_document document_representation_type.name = 'physical'} document => document_file

5.1.4 Document_location_identification

MIM element:

/SUPERTYPE(External_source_identification)/

5.1.5 External_source_identification

This application object, External_source_identification, is defined in the module external_item_identification_assignment. This mapping section extends the mapping of External_source_identification, to include assertions defined in this module.

5.1.5.1 External_source_identification to Document_definition (as item)

MIM element:	PATH
Reference path:	applied_external_identification_assignment.items[i]-> external_identification_item external_identification_item *> document_location_select document_location_select = product_definition