4 Information requirements

This clause specifies the information requirements for the Person organization 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 Person organization schema.

4.1 ARM type definition

This subclause specifies the ARM type for this application module. The ARM type and definition is specified below.

4.1.1 organization_or_person_in_organization_select   

The organization_or_person_in_organization_select type allows for the designation of the data types Organization and Person_in_organization.

EXPRESS specification:

*)
TYPE organization_or_person_in_organization_select = SELECT
   (Organization,
    Person_in_organization);
END_TYPE;
(*

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 Address   

EXPRESS specification:

*)
ENTITY Address;
  name : OPTIONAL STRING;
  street_number : OPTIONAL STRING;
  street : OPTIONAL STRING;
  postal_box : OPTIONAL STRING;
  town : OPTIONAL STRING;
  region : OPTIONAL STRING;
  postal_code : OPTIONAL STRING;
  country : OPTIONAL STRING;
  internal_location : OPTIONAL STRING;
  facsimile_number : OPTIONAL STRING;
  telephone_number : OPTIONAL STRING;
  electronic_mail_address : OPTIONAL STRING;
  telex_number : OPTIONAL STRING;
  url : OPTIONAL STRING;
WHERE
  WR1: (EXISTS (street_number) OR EXISTS (street) OR EXISTS (postal_box) OR EXISTS (town) OR EXISTS (region) OR EXISTS (postal_code) OR EXISTS (country) OR EXISTS (internal_location) OR EXISTS (facsimile_number) OR EXISTS (telephone_number) OR EXISTS (electronic_mail_address) OR EXISTS (telex_number));
END_ENTITY;
(*

Attribute definitions:

name: the words by which the Address is known. It specifies the name of the location identified by the address. The value of this attribute need not be specified.

EXAMPLE    "White House", "Buckingham Palace", and "North Pole" are examples of address name.

street_number: the number of a location on a street. The value of this attribute need not be specified.

street: the name of a street. The value of this attribute need not be specified.

postal_box: the number of a postal box. The value of this attribute need not be specified.

town: the name of a town. The value of this attribute need not be specified.

region: the name of a region. The value of this attribute need not be specified.

postal_code: the code that is used by the country's postal service. The value of this attribute need not be specified.

country: the name of a country. The value of this attribute need not be specified.

internal_location: an organization-defined address for internal mail delivery. The value of this attribute need not be specified.

facsimile_number: the number to which facsimiles may be sent. The value of this attribute need not be specified.

telephone_number: the number at which telephone calls may be received. The value of this attribute need not be specified.

electronic_mail_address: the electronic address to which electronic mail may be sent. The value of this attribute need not be specified.

telex_number: the number where telex messages may be received. The value of this attribute need not be specified.

url: the text that specifies the Uniform Resource Locator associated with the address. The value of this attribute need not be specified.

Formal propositions:

WR1: At least one of the attributes shall have a value.

4.2.2 Address_assignment   

EXPRESS specification:

*)
ENTITY Address_assignment;
  address_type : OPTIONAL STRING;
  assigned_address : Address;
  located_person_organizations : SET[1:?] OF organization_or_person_in_organization_select;
END_ENTITY;
(*

Attribute definitions:

address_type: the string that specifies the type of the Address. The value of this attribute need not be specified.

EXAMPLE    'postal address' and 'visitor address' are examples of address types that may be used to characterize addresses of an organization.

assigned_address: the Address that is provided.

located_person_organizations: the Organization or the Person_in_organization that is located with the Address.

4.2.3 Organization   

EXPRESS specification:

*)
ENTITY Organization;
  id : OPTIONAL STRING;
  name : STRING;
END_ENTITY;
(*

Attribute definitions:

id: the identifier that distinguishes the Organization. The value of this attribute need not be specified.

name: the words by which the Organization is known.

4.2.4 Organization_relationship   

EXAMPLE    A team belongs to a department which itself belongs to a company. Such an organizational structure can be described up using instances of Organization_relationship.

EXPRESS specification:

*)
ENTITY Organization_relationship;
  relation_type : STRING;
  description : OPTIONAL STRING;
  relating_organization : Organization;
  related_organization : Organization;
END_ENTITY;
(*

Attribute definitions:

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

Where applicable the following values shall be used:

• 'hierarchy': The related Organization is a sub organization of the relating Organization;
• 'legal succession': The related Organization is the legal successor of the relating Organization;
• 'reorganization': The related Organization is the successor of the relating Organization due to an organizational transfer of responsibility.

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

relating_organization: one of the instances of Organization that is a part of the relationship.

related_organization: the other instance of Organization that is part of the relationship. If one element of the relationship is dependent upon the other, this attribute shall be the dependent one.

4.2.5 Person   

EXPRESS specification:

*)
ENTITY Person;
  last_name : STRING;
  first_name : OPTIONAL STRING;
  middle_names : OPTIONAL LIST[1:?] OF STRING;
  prefix_titles : OPTIONAL LIST[1:?] OF STRING;
  suffix_titles : OPTIONAL LIST[1:?] OF STRING;
END_ENTITY;
(*

Attribute definitions:

last_name: the Person's name.

first_name: the first element of the Person's list of forenames. The value of this attribute need not be specified.

middle_names: the Person's other forenames. The value of this attribute need not be specified.

prefix_titles: the text that specifies the Person's social or professional standing and appear before his or her names. The value of this attribute need not be specified.

EXAMPLE 1   "Mr.", "Ms", "Dr." and combinations are examples of prefix_titles.

suffix_titles: the text that specifies the Person's social or professional standing and appear after his or her names. The value of this attribute need not be specified.

EXAMPLE 2   "Ph.D." and "Esquire" are examples of suffix_titles.

4.2.6 Person_in_organization   

EXPRESS specification:

*)
ENTITY Person_in_organization;
  concerned_person : Person;
  containing_organization : Organization;
  role : STRING;
END_ENTITY;
(*

Attribute definitions:

concerned_person: the Person who is related with an Organization.

containing_organization: the Organization to which a Person is related.

role: the text that designates the role of the Person in the related Organization.

© ISO 2004 — All rights reserved