Application module: Resource item | ISO/TS 10303-1268:2010-03(E) © ISO |
This clause specifies the information requirements for the Resource item 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 Resource_item_arm schema and identifies the necessary external references.
EXPRESS specification:
*)
SCHEMA Resource_item_arm;
(*
The following EXPRESS interface statements specify the elements imported from the ARMs of other application modules.
EXPRESS specification:
*)
USE FROM
Classification_assignment_arm;
--
ISO/TS 10303-1114
USE FROM
Value_with_unit_arm;
--
ISO/TS 10303-1054
(*
NOTE 1 The schemas referenced above are specified in the following part of ISO 10303:
Classification_assignment_arm ISO/TS 10303-1114 Value_with_unit_arm ISO/TS 10303-1054
NOTE 2 See Annex C, Figures C.1and C.2 for a graphical representation of this schema.
This subclause specifies the ARM types for this application module. The ARM types and definitions are specified below.
The resource_assignment_item type is an extensible list of alternate data types. Additional alternate data types are specified in select data types that extend the resource_assignment_item type.
NOTE This empty extensible select requires extension in a further module to ensure that entities that refer to it have at least one valid instantiation.
EXPRESS specification:
*)
TYPE
resource_assignment_item =
EXTENSIBLE
GENERIC_ENTITY
SELECT;
END_TYPE;
(*
The resource_item_classification_item type is an extension of the classification_item type. It adds the data types Resource_item, Resource_item_assignment and Resource_item_relationship to the list of alternate data types.
NOTE The list of entity data types may be extended in application modules that use the constructs of this module.
EXPRESS specification:
*)
TYPE
resource_item_classification_item =
EXTENSIBLE
GENERIC_ENTITY
SELECT
BASED_ON
classification_item
WITH
(Resource_item,
Resource_item_assignment,
Resource_item_relationship);
END_TYPE;
(*
The resource_item_select type is an extensible list of alternate data types. Additional alternate data types are specified in select data types that extend the resource_item_select type.
NOTE This empty extensible select requires extension in a further module to ensure that entities that refer to it have at least one valid instantiation.
EXPRESS specification:
*)
TYPE
resource_item_select =
EXTENSIBLE
GENERIC_ENTITY
SELECT;
END_TYPE;
(*
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.
EXAMPLE 1 The relationship between a tool set and a mallet could be classified as "Contains".
EXAMPLE 2 The relationship between a facility and compressed air could be classified as "Provides".
EXPRESS specification:
*)
ENTITY Resource_group_relationship
SUBTYPE OF (Resource_item_relationship);
quantity :
OPTIONAL
Value_with_unit;
END_ENTITY;
(*
Attribute definitions:
quantity: the measure of the amount of related Resource_item. The value of the attribute need not be specified.
EXAMPLE A Resource_item may be classified as "Facility", "Replaceble unit", or "Package".
EXPRESS specification:
*)
ENTITY Resource_item;
name : STRING;
description :
OPTIONAL
STRING;
END_ENTITY;
(*
Attribute definitions:
name: the words by which the Resource_item is known.
description: the text that provides further information about the Resource_item. The value of the attribute need not be specified.
A Resource_item_assignment is an association of a resource item with some product information. The role of the assignment is determined by classification.
EXAMPLE The assignment can be classified as "applicable to" or "acquired for".
EXPRESS specification:
*)
ENTITY Resource_item_assignment;
assigned_resource : Resource_item;
item : resource_assignment_item;
END_ENTITY;
(*
Attribute definitions:
assigned_resource: the resource item that is to be associated with an item.
item: the resource assignment item to which the resource item is assigned.
A Resource_item_realization is a specification of how a resource item may be associated with an item that serves as the resource.
EXAMPLE A product may serve as a resource.
EXPRESS specification:
*)
ENTITY Resource_item_realization;
item : resource_item_select;
resource_item : Resource_item;
END_ENTITY;
(*
Attribute definitions:
item: the item that is to be associated with the resource that it serves as.
resource_item: the resource that is to be associated with an item that serves as that resource.
A Resource_item_relationship is a specification of how a resource item may be associated with another resource item. The role of the relationship is determined by classification.
EXAMPLE The relationship between a product and a package can be classified as "Preferred".
EXPRESS specification:
*)
ENTITY Resource_item_relationship;
name : STRING;
description :
OPTIONAL
STRING;
relating : Resource_item;
related : Resource_item;
END_ENTITY;
(*
Attribute definitions:
name: the word or words by which the Resource_item_relationship is known.
description: the text that provides further information about the resource item relationship. The value of the attribute need not be specified.
relating: one of the instances of Resource_item that is a part of the relationship.
related: the other instance of Resource_item that is a part of the relationship. If one element of the relationship is dependent upon the other, this attribute shall be the dependent one.
*)
END_SCHEMA; -- Resource_item_arm
(*
© ISO 2009 — All rights reserved