Application module: Information rights ISO/TS 10303-1241:2019(E)
© ISO

Cover page
Table of contents
Copyright
Foreword
Introduction
1 Scope
2 Normative references
3 Terms, definitions and abbreviated terms
    3.1 Terms and definitions
    3.2 Abbreviated terms

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

A MIM short names
B Information object registration
C ARM EXPRESS-G   EXPRESS-G
D MIM EXPRESS-G   EXPRESS-G
E Computer interpretable listings
F Change history
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:

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

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:

This section is omitted when the keywords PATH or IDENTICAL MAPPING or NO MAPPING EXTENSION PROVIDED 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:

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;
!{} section enclosed by {} indicates a negative constraint placed on the mapping.
The definition and use of mapping templates are not supported in the present version of the application modules. However, use of predefined templates /MAPPING_OF/, /SUBTYPE/, and /SUPERTYPE/ is supported.

5.1.1 Applied_information_usage_right

MIM element: applied_usage_right
Source: ISO 10303-1047
Reference path:   applied_usage_right <=
action_assignment

5.1.1.1 Applied_information_usage_right to activity_item (as item)

MIM element: PATH
Reference path:   applied_usage_right.items[i] ->
ir_usage_item = action_items

5.1.1.2 Applied_information_usage_right to Information_usage_right (as right_applied)

MIM element: PATH
Reference path:   applied_usage_right <= action_assignment
action_assignment
action_assignment.assigned_action -> action
action.chosen_method -> action_method
{action_method.purpose = 'information usage right'}

5.1.2 Approval_assignment

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

5.1.2.1 Approval_assignment to Applied_information_usage_right (as items)

MIM element: PATH
Reference path:   applied_approval_assignment.items[i] -> approval_item
mri_approval_item *> ir_approval_item
ir_approval_item = applied_usage_right

5.1.3 Approval_assignment

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

5.1.3.1 Approval_assignment to Information_usage_right (as items)

MIM element: PATH
Reference path:   applied_approval_assignment.items[i] -> approval_item
mri_approval_item *> ir_approval_item
ir_approval_item = information_usage_right

5.1.4 Contract_assignment

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

5.1.4.1 Contract_assignment to Information_usage_right (as items)

MIM element: PATH
Reference path:   applied_contract_assignment.items[i] -> contract_item
contract_item *> ir_contract_item
ir_contract_item = information_usage_right

5.1.5 Date_or_date_time_assignment

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

5.1.5.1 Date_or_date_time_assignment to Information_usage_right (as items)

#1:   if the assigned_date is a Calendar_date

MIM element: PATH
Reference path:   (date_assignment=>
applied_date_assignment
applied_date_assignment.items[i] -> date_item
mri_date_item *> ir_date_item
ir_date_item = information_usage_right)

#2:   if the assigned_date is a Date_time

MIM element: PATH
Reference path:   (date_and_time_assignment=>
applied_date_and_time_assignment
applied_date_and_time_assignment.items[i] -> date_and_time_item
mri_date_and_time_item *> ir_date_and_time_item
ir_date_and_time_item = information_usage_right)

5.1.6 Information_right

MIM element: information_right
Source: ISO 10303-1241
Reference path:   information_right <=
action_method
{action_method.purpose='information right'}

5.1.6.1 description

MIM element: PATH
Reference path:   information_right <=
action_method
action_method.description

5.1.6.2 id

MIM element: PATH
Reference path:   information_right <- applied_identification_assignment.items[i]
applied_identification_assignment <=
identification_assignment
{identification_assignment.role -> identification_role
identification_role.name = 'identifier'}
identification_assignment.assigned_id

5.1.6.3 name

MIM element: PATH
Reference path:   information_right <=
action_method
action_method.name

5.1.6.4 restriction

MIM element: PATH
Reference path:   information_right <=
action_method
action_method.consequence

5.1.7 Information_usage_right

MIM element: information_usage_right
Source: ISO 10303-1241
Reference path:   information_usage_right <=
action_method
{action_method.purpose='information usage right'}

5.1.7.1 comment

MIM element: PATH
Reference path:   information_usage_right <=
action_method
action_method.consequence

5.1.7.2 id

MIM element: PATH
Reference path:   information_usage_right <- applied_identification_assignment.items[i]
applied_identification_assignment <=
identification_assignment
{identification_assignment.role -> identification_role
identification_role.name = 'identifier'}
identification_assignment.assigned_id

5.1.7.3 name

MIM element: PATH
Reference path:   information_usage_right <=
action_method
action_method.name

5.1.7.4 Information_usage_right to Information_right (as grants_right)

MIM element: PATH
Reference path:   information_usage_right <- action_method_relationship.relating_method
action_method_relationship
{action_method_relationship.name = 'right to usage association'}
action_method_relationship.related_method -> action_method
action_method
{action_method.purpose = 'information right'}

5.1.8 Information_usage_right_relationship

MIM element: usage_association
Source: ISO 10303-1241
Reference path:   usage_association <=
action_method_relationship
{action_method_relationship.name='information usage right relationship'}

5.1.8.1 relation_type

MIM element: PATH
Reference path:   usage_association <=
action_method_relationship
action_method_relationship.description

5.1.8.2 Information_usage_right_relationship to Information_usage_right (as related)

MIM element: PATH
Reference path:   usage_association <=
action_method_relationship
action_method_relationship.related_method ->
action_method

5.1.8.3 Information_usage_right_relationship to Information_usage_right (as relating)

MIM element: PATH
Reference path:   usage_association <=
action_method_relationship
action_method_relationship.relating_method ->
action_method

5.1.9 Organization_or_person_in_organization_assignment

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

5.1.9.1 Organization_or_person_in_organization_assignment to Information_usage_right (as items)

#1:   if assigned_entity is an Organization

MIM element: PATH
Reference path:   (applied_organization_assignment.items[i] -> organization_item
mri_organization_item *> ir_organization_item
ir_organization_item = information_usage_right)

#2:   if assigned_entity is a Person_in_organization

MIM element: PATH
Reference path:   (applied_person_and_organization_assignment.items[i] -> person_and_organization_item
mri_person_and_organization_item *> ir_person_and_organization_item
ir_person_and_organization_item = information_usage_right)


© ISO 2019 — All rights reserved