4 Information requirements

This clause specifies the information requirements for the Information rights 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.

This clause defines the information requirements to which implementations shall conform using the EXPRESS language as defined in ISO 10303-11. The following begins the Information_rights_arm schema and identifies the necessary external references.

4.1 Required AM ARMs

The following EXPRESS interface statements specify the elements imported from the ARMs of other application modules.

EXPRESS specification:

*)
USE FROM Activity_arm;    --  ISO/TS 10303-1047



USE FROM Contract_arm;    --  ISO/TS 10303-1062



USE FROM Management_resource_information_arm;    --  ISO/TS 10303-1288
(*



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

Activity_arm	ISO/TS 10303-1047
Contract_arm	ISO/TS 10303-1062
Management_resource_information_arm	ISO/TS 10303-1288

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

4.2 ARM type definitions

This subclause specifies the ARM types for this application module. The ARM types and definitions are specified below.

4.2.1 right_approval_item   

The right_approval_item type is an extension of the mri_approval_item type. It adds the data types Applied_information_usage_right and Information_usage_right 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 right_approval_item = EXTENSIBLE GENERIC_ENTITY SELECT BASED_ON mri_approval_item WITH
   (Applied_information_usage_right,
    Information_usage_right);
END_TYPE;
(*

4.2.2 right_contract_item   

The right_contract_item type is an extension of the contract_item type. It adds the data type Information_usage_right 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 right_contract_item = EXTENSIBLE GENERIC_ENTITY SELECT BASED_ON contract_item WITH
   (Information_usage_right);
END_TYPE;
(*

4.2.3 right_date_item   

The right_date_item type is an extension of the mri_date_or_date_time_item type. It adds the data type Information_usage_right 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 right_date_item = EXTENSIBLE GENERIC_ENTITY SELECT BASED_ON mri_date_or_date_time_item WITH
   (Information_usage_right);
END_TYPE;
(*

4.2.4 right_person_organization_item   

The right_person_organization_item type is an extension of the mri_organization_or_person_in_organization_item type. It adds the data type Information_usage_right 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 right_person_organization_item = EXTENSIBLE GENERIC_ENTITY SELECT BASED_ON mri_organization_or_person_in_organization_item WITH
   (Information_usage_right);
END_TYPE;
(*

4.3 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.3.1 Applied_information_usage_right   

NOTE    If an approval is applied to this entity, it carries the meaning that the specific set of items is approved for the given usage. In general, this approval indicates that the approval is exceptional, for example, where the information belongs to another project, and that project agrees to share some specific items of information. There is a further implication that the set of entities should not be changed once the approval is given.

EXPRESS specification:

*)
ENTITY Applied_information_usage_right;
  item : SET[1:?] OF activity_item;
  right_applied : Information_usage_right;
END_ENTITY;
(*

Attribute definitions:

item: the set of information usage right items to which the usage right applies.

right_applied: the right which is applied to the items

4.3.2 Information_right   

An Information_right is a definition of what may or may not be done with information in the sense of legal rights and obligations.

NOTE 1   This a general-purpose definition of a right that may be applied to many things. The usage of the Information_right is represented by Information_usage_right. The application of that right to information is represented by Applied_information_usage_right.

EXAMPLE 1   Copyright is an Information_right.

EXAMPLE 2   For the purposes of developing a new system, details of government furnished equipment may be made available to a specific project team. The team may copy and use the information internally, but may not pass it on, either to a third part, or to another team, and must destroy the information at the end of the contract.

EXPRESS specification:

*)
ENTITY Information_right;
  id : STRING;
  name : STRING;
  description : OPTIONAL STRING;
  restriction : OPTIONAL STRING;
END_ENTITY;
(*

Attribute definitions:

id: an identifier for the right.

NOTE 2   The identifier should be unique, however there is no meaningful way of specifying the scope over which it is unique.

name: the word or words by which the right is known.

description: the text that provides further information about what the right allows the user to do, and what is not permitted. The value of this attribute need not be specified.

restriction: the text that describes any conditions and limitations that apply to the exercise of the right. The value of this attribute need not be specified.

EXAMPLE 3   The description of the right states that copying is permitted within the project team only, whereas the restriction notes the additional constraint that the information must be destroyed at the end of the project.

4.3.3 Information_usage_right   

NOTE 1   One view of the distinction between an Information_right and an Information_usage_right is that the Information_right represents a standard clause in a contract, whereas an Information_usage_right represents the fact that the clause is used in a specific contract.

NOTE 2   The context for the usage can be defined through the contract which defines the right, the organization that grants the right, the person or organization which is granted the right, and any dates such as the starting or ending dates for the right. The meaning of each association is identified through the roles of the assignments, and these are defined through reference data.

NOTE 3   The Approval of an Information_usage_right carries the meaning that the right is granted to all information items in the relevant context, as opposed to the approval of an Applied_information_usage_right which is limited to specific items.

NOTE 4   Information_usage_right provides a mechanism for recording significant rights within a product database. The legal significance of the presence or absence of a right is outside the scope of this part of ISO 10303

EXPRESS specification:

*)
ENTITY Information_usage_right;
  id : STRING;
  name : STRING;
  comment : OPTIONAL STRING;
  grants_right : SET[1:?] OF Information_right;
END_ENTITY;
(*

Attribute definitions:

id: the identifier of the Information_usage_right.

name: the word or words by which the Information_usage_right is known.

comment: the additional information to be recorded about the Information_usage_right. The value of this attribute need not be specified.

grants_right: the set of Information_rights granted under this usage.

4.3.4 Information_usage_right_relationship   

EXPRESS specification:

*)
ENTITY Information_usage_right_relationship;
  relating : Information_usage_right;
  related : Information_usage_right;
  relation_type : STRING;
END_ENTITY;
(*

Attribute definitions:

relating: one of the instances of Information_usage_right that is a part of the relationship.

related: the other instance of Information_usage_rights that is a part of the relationship. If one Information_usage_right participating in the relationship is dependent upon the other, this attribute shall be the dependent one.

relation_type: a role that defines the behaviour of the relationship.

© ISO 2019 — All rights reserved