representing_organizational

NOTE The template has been defined in the context of the capability representing_location which provides an overall description of the relevant parts of the ISO 10303-239 information model and a description of related templates.

NOTE An explanation of a template and the associated instantiation path is provided in the Template overview section.

This template describes the representation of an organization based location. It instantiates the Organization_based_location_representation, Organizational_location_identification, Organization instances within this template.

The following input parameters are defined for this template:

The following reference parameters are defined for this template:

For example, to create additional identifiers for an instance of Organizational_location_identification which has been defined for the Organization_based_location_representation entity. E.g.

          -- The template assigning_organization_location has an external reference
                     -- org_loc_id. Bind this to the local external reference
                     -- Organizational_location_identification. It can now be the target for assignments 
                     %^org_loc_id = $assigning_organization_location.Organizational_location_identification%
                     -- assign 'DRDL_QGJD' to the location in the role of "Location_identification_code"
                     /assigning_identification_with_no_organization(items=^org_loc_id, 
                     id='DRDL_QGJD', 
                     id_class_name='Location_identification_code',
                     id_ecl_id='urn:plcs:rdl:std')/

The instantiation path shown below specifies the entities that are to be instantiated by the template.

A description of templates and the syntax for the instantiation path is provided in the Templates Help/Information section.

-- Create Organization
%^organization = Organization%
Organization.name = '/IGNORE'
Organization.id = '/IGNORE'

-- assign an identifier and classify it with input params'.
-- (Note not specifying class to enable id or name allotment)
/assigning_identification_with_no_organization(
    items=Organization,
    id=@org_name,
    id_class_name=@org_name_class,
    id_ecl_id=@org_name_ecl_id)/

-- Create Organizational_location_identification
%^org_loc_id = Organizational_location_identification%
Organizational_location_identification.identification_type = '/IGNORE'
Organizational_location_identification.location_value = '/IGNORE'

-- assign an identifier and classify it with input params'.
-- (Note not specifying class to enable id or name allotment)
/assigning_identification_with_no_organization(
    items=Organizational_location_identification,
    id=@loc_val,
    id_class_name=@loc_id_type,
    id_ecl_id=@loc_id_type_ecl_id)/

-- Organization_based_location_representation
%^org_loc_rep = Organization_based_location_representation%
Organization_based_location_representation.organization_for_location -> Organization

-- Create links to organization location identification
Organization_based_location_representation.location_identifications -> Organizational_location_identification

-- end.

The following entities are instantiated with attributes as specified:

Entity in path	Value	Inherited from
Organization.name	'/IGNORE'	—
Organization.id	'/IGNORE'	—
Organizational_location_identification.identification_type	'/IGNORE'	—
Organizational_location_identification.location_value	'/IGNORE'	—

The following section details how the representing_organizational_location template can be optionally characterized by assigning other constructs to it. These are characterizations commonly applied to the template. The ISO 10303-239 EXPRESS model may enable other assignments to the entities instantiated by the template.

The following characterizations may apply:

Characterization Assigning date

NOTE this characterization is optional.

Where the representation is defined in the context of an alternative location representation, it is recommended that dates be associated with the main Location for which this is an alternative. However, where specifically required dates can be associated with the Organization_based_location_representation instantiated by the template as shown below.

Figure 5 — Template Configuration with Optional Calendar Date Assignment.

Note this requires the use of the reference parameter $representing_organizational_location.org_loc_rep to identify the Organization_based_location_representation instantiated by the template representing_organizational_location.

/assigning_calendar_date(items='$representing_organizational_location.org_loc_rep', date_class_name='Date_actual_observation', date_ecl_id='urn:plcs:rdl:std', year='2005', month='05', day='04')/

Characterization Assigning identifiers with no organization

NOTE this characterization is optional.

Organizational_based_location_representation -
An identifier can be associated with the instance of Organizational_based_location_representation by using the template assigning_identification_with_no_organization. Where required an [Organizational_based_location_identification_code]
Error RDL1: The class Organizational_based_location_identification_code does not exist in RDL at URI urn:plcs:rdl:std. Check the dexlib/data/refdata/rdl_index.xml
- (i.e. the location within the context of the relevant Organization) can be assigned to an instance of Organization_based_location_representation. This should be done when more than one instance of Organization_based_location_representation is referenced in the context of an alternative location.
Organizational_location_identification -
The model allows for a list of [0:?] Organizational_location_identification instances to be created. The template forces one instance of Organizational_location_identification to be created and one instance of identification_assignment to carry the location and identification type. However, because the location identification instance is accessible outside of the template, any number of assignments can be made to the Organizational_location_identification, if required using the template assigning_identification_with_no_organization. This makes creating a separate instance of for each one superfluous. Thus, it is recommended to create only a single Organizational_location_identification for each representation. There may be 1 or many location and identification types assigned using assigning_identification_with_no_organization for each organization represented.

NOTE The identifier type should be of class "Organizational location identification code" (urn:plcs:rdl:std:Organizational location identification code).
Organization -
Further identifiers can be associated with the instance of Organization by using the template assigning_identification_with_no_organization. This might include additional organization id codes that can be assigned to an instance of Organization, if required (e.g. CAGE Code, UID..). The assignment should be classified as a type of "Organization identification code" (urn:plcs:rdl:std:Organization identification code) or "Organization name" (urn:plcs:rdl:std:Organization name).