representing_location

Capability (C027):— representing_location

Date: 2005/08/15 08:20:35 :
Revision: 1.28

Cover Contents Intro.Overview Info. model Templates Ref. data Issues

Issue raised against: representing_location

GENERAL issues

Issue: RBN-1 by Rob Bodington (05-06-24) minor_technical issue
Resolution: Accept. Status: open

I think that you should include the Location_assignment in this capability. After all, you need to use the location in conjunction with something.

Issue: RBN-2 by Rob Bodington (05-06-24) minor_technical issue
Resolution: Accept. Status: open

I think that we need to clarify when to use address-assignment and when to use location_assignment when representing the address of an organization. I propose that we only use location_assignment

Issue: RBN-3 by Rob Bodington (05-06-24) minor_technical issue
Resolution: Accept. Status: open

I would have expected reference data to have been developed for this capability. For example, country codes.

Issue: RBN-12 by Rob Bodington (05-09-21) minor_technical issue
Resolution: Accept. Status: open

The capability representing_location should be merged with representing_product_location. The capability should have a template for assigning each of the different types of location. E.g. assigning_address_location, assigning_organization_location etc.

Issue: NSW-1 by Nigel Shaw (05-11-01) major_technical issue
Resolution: Accept. Status: open

The instruction to remove the Organzation entity is incorrect. It is required by the ENTITY Organization_based_location_representation.

Issue: RBN-13 by Rob Bodington (05-11-23) minor_technical issue
Resolution: Accept. Status: open

Add TEMPLATE: assigning_location which contains ENtities Location Location_assignment With location being classified and identified You would need to explain in the template that the representation for the location is in effect optional. And then the set of representing location templates for the sub types of Location_representation

Issue: PBM-1 by Peter Bergstrom (2006-02-10) minor_technical issue
Resolution: Accept. Status: open

Template Assigning_organization_location has a number of in-parameters that belongs to optional assigning_calendar_date templates. This makes it necessary to give dates when using the template.The in-parameters should be removed, and assignment of dates should be covered in the characterization section of the template.

Issue: PBM-2 by Peter Bergstrom (2006-02-10) minor_technical issue
Resolution: Accept. Status: open

Definitions of several in-parameters in template Assigning_organization_location are incorrect or insufficient:
loc_id_class_name: Propose: 'The name of the class used to classify the location identifier and so provide the role or reason for the identification', or even better: 'The name of the class used to classify the location identifier and so provide the type of identifier used',
org_name: Propose: 'Name or id of the organization in which the location identifier is meaningful.'
org_class_name: Propose: 'The name of the class used to classify the identifier of the organization and so provide the type of identifier used',
org_name_ecl_id: Definition incorrect (refers to start date).
loc_val: propose 'The location value (location identifier) being assigned.'
loc_id_type_acl_id: Definition incorrect (refers to start date).

Issue: RBN-14 by Rob Bodington (06-02-13) minor_technical issue
Resolution: Accept. Status: open

The path in the template assigning_location is incorrect. It will result in two location entities being instantiated. Furthermore, it does not assign anything, i.e. the entity_for_location attribute is not assigned. It should be: Location -- Mark the Location entity as -- referable when this template is used by binding it to the reference -- parameter location %^location = Location% Location.description = '/IGNORE' Location.name = '/IGNORE' -- assign an identifier and classify it with input params' /assigning_identification_with_no_organization(items=^location, id=@loc_id, id_class_name=@loc_id_class_name, id_ecl_id=@loc_id_ecl_id)/ Location_assignment -- Mark the location_assignment entity as -- referable when this template is used by binding it to the reference -- parameter id_assgn %^locn_asst = Location_assignment% Location_assignment.description = '/IGNORE' Location_assignment.role = '/IGNORE' Location_assignment.location_for_assignment -> ^location Location_assignment.entity_for_location -> @entity_for_location -- provide the role of the identification by classifying the location_assignment /assigning_reference_data(items=^locn_asst, class_name=@la_class_name, ecl_id=@la_ecl_id)/

Issue: RBN-15 by Rob Bodington (06-02-13) minor_technical issue
Resolution: Accept. Status: open

The entity in Location shown in the EXPRESS-G diagram "Figure 5.1 Template Configuration for Assigning Location" is incorrect - the attribute alternative_location_representations is missing - this would be helpful in understanding the template assigning_organization_location

Issue: RBN-16 by Rob Bodington (06-06-21) minor_technical issue
Resolution: Accept. Status: open

A number of the templates are incomplete. they are missing the EXPRESS-G diagrams and instance diagrams. E,g, Template: representing_grid_location representing_address_location representing_product_location

Issue: DNV-31 by Sylvia Schwab on behalf of DNV (07-03-07) major_technical issue
Resolution: Accept. Status: open

A template is required to relate a product based location to its parent product.

Proposal: Add NEW template representing_product_based_location (rep_p_based_locn), containing Product_based_location_identification with one identifier and one classification.

The general issue about templates at entity granularity arises and it needs to be considered.

Issue: DNV-32 by Sylvia Schwab on behalf of DNV (07-03-07) major_technical issue
Resolution: Accept. Status: open

Representing_location (C027) and assigning_location (C049) are represented as two differenet capabilities.

Proposal: Consider integrating them into representing_location (C027) and use assigning_location as a template.

GENERAL issues

Issue: MWD-1 by Mike Ward (2004-10-20) minor_technical issue
Resolution: Accept. Status: closed

Need to add (and prune) person_organization module to usage.

Comment: (Mike Ward 2004-10-19)
Done

Issue: RBN-17 by Rob Bodington (06-06-23) minor_technical issue
Resolution: Accept. Status: closed

The assigning_organization_location can be deprecated. It would be better to use assigning_location and representing_organizational_location. This allows a single location to have multiple representations. Note: the actual entities instantiated are the same, it is just the organization of templates that has changed

Comment: (Rob Bodington 06-06-23)
The template has been deleted

Issue: RBN-18 by Rob Bodington (07-08-09) minor_technical issue
Resolution: Accept. Status: closed

Moved template representing_product_location to NDLO/templates