ISO/TS 10303-1020:2006 Product version relationship


Application module: Product version relationship	ISO/TS 10303-1020:2006(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 ARM
4.2 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
D MIM EXPRESS-G
E Computer interpretable listings
Bibliography
Index

4 Information requirements

This clause specifies the information requirements for the Product version relationship 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 Product_version_relationship_arm schema and identifies the necessary external references.

EXPRESS specification:




         *)

            SCHEMA Product_version_relationship_arm;
(*

4.1 Required AM ARM

The following EXPRESS interface statement specifies the elements imported from the ARM of another application module.

EXPRESS specification:

*) USE FROM Product_version_arm; -- ISO/TS 10303-1018 (*

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

Product_version_arm ISO/TS 10303-1018

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

4.2 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.2.1 Product_version_relationship

A Product_version_relationship is an association between two versions of Product.

NOTE A relationship may exist between Product_version of different Products or between different versions of the same Product.

EXPRESS specification:

*) ENTITY Product_version_relationship; relation_type : OPTIONAL STRING; description : OPTIONAL STRING; relating_version : Product_version; related_version : Product_version; WHERE WR1: relating_version :<>: related_version; WR2: EXISTS(relation_type) OR (TYPEOF(SELF\Product_version_relationship) <> TYPEOF(SELF)); END_ENTITY; (*

Attribute definitions:

relation_type: the string that specifies the meaning of the Product_version_relationship.

Where applicable, the following values shall be used:

'derivation': the instance defines a deriving relationship where the related Product_version is based on the relating Product_version which is an earlier version of the same or of a different Product;
'hierarchy': the instance defines a hierarchical relationship where the related Product_version is a subordinate version of the relating Product_version;
EXAMPLE 1 'Rev. 1.1' and 'rev. 1.2' are subordinates of 'version 1'.
'sequence': the instance defines a version sequence where the relating Product_version is the preceding version of the related Product_version that is the following version. For a given Product_version, there shall be at most one Product_version_relationship of this relation_type referring to this Product_version as 'relating' and at most one Product_version_relationship of this relation_type referring as 'related'.

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

relating_version: the first instance of Product_version that is a part of the relationship.

related_version: the other instance of Product_version that is a part of the relationship. If one element of the relationship is dependent up on the other, this attribute shall be the dependent one.

Formal propositions:

WR1: the related instances of Product_version shall be distinct.

WR2: If SELF is exact instance of Product_version_relationship, then relation_type shall be provided.

4.2.2 Supplied_part_relationship

A Supplied_part_relationship is a type of Product_version_relationship that relates two instances of Product_version that represent the same object in different organizational contexts.

One of the organizations is the supplier of the object to the other organization.

This entity is applicable for part versions and document versions.

NOTE 1 This entity enables to represent the fact that two organizations may use distinct identifiers to identify their Products and their versions.

NOTE 2 This mechanism can only be used in an information system or in exchange files where the content of the id attribute of instances of Product is not constrained by a particular identification scheme.

NOTE 3 The module Alias identification provides a more general mechanism that can be used to track alias identifiers for any entity data type that has an id attribute.

EXPRESS specification:

*) ENTITY Supplied_part_relationship SUBTYPE OF (Product_version_relationship); WHERE WR1: SELF\Product_version_relationship.relation_type IN ['supplied item', 'supplied document']; END_ENTITY; (*

Formal propositions:

WR1: the relation_type shall be 'supplied item' for parts and 'supplied document' for documents.

Informal propositions:

IP1: the related_version and the relating_version shall identify objects of the same kind.




         *)

         END_SCHEMA;  -- Product_version_relationship_arm
(*