Template:— assigning_identification (asg_id) Date: 2008/02/12 06:27:54
Revision: 1.23
CoverContentsDescriptionModel diags.Input params.Ref. params.Instantiation pathInstance diags.CharacterizationsIssues

Issue raised against: assigning_identification

GENERAL issues

Closed issue Issue: DNV-01 by Sylvia Schwab on behalf of DNV (07-02-26) minor_technical issue
Resolution: Accept. Status: closed

The name of the organization (owner_org_name) as input parameter seems to be missing in the OASIS assigning_identification template. It turns out that it can be assigned optionally allowing both identifier and name to be assigned. The expressG graphic doesn't provide this information.

Add the optional parameter to graphical representation of the template (relates to assigning_organization/C094 parameter list)

Comment: (TJT 2008/01/23)
The parameter org_id_class_name is not optional. However, it caters for EITHER a class of Organization_identification_code OR a class of Organization_name to be provided. It is of course, possible to assign another Organization in another context to the identification_assignment which will be added to the characterization section.

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

An identifier (e.g. task_code) may not be unique inside an organization with a cage code. The uniqueness may only be ensured inside a division or department, or even for a project or for a product type or an individual product.

Proposal: In C001, add optional relation (to identify division/department, project, product type and individual product) to the template relating to the organization with the cage code. This can be done by:

  1. Relating an organization with division/department identification code to the Organization with Cage_code through template assigning_organization_relationship (see issue reported to assigning_organization (C094).
  2. Assign Product_as_individual_effectivity to Identification_assignment (see DNV-45 reported as part of assigning_effectivity (C006). Effectivity_assignment can be classified with "Identifier_context".
  3. Consider extending the effectivity template to relate the effectivity_assignment classified as "Identifier_context" to e.g. project and product_type.
Comment: (TJT 2008/01/23)
The handling of uniqueness is to be done within the context of its application, not as part of this template, as described by RBN-5. The concluding statement in that issue is "rather than changing the model, the Unique constraint should be removed and then applied when using the IDENTIFICATION_ASSIGNMENT". Additional organizations may be assigned to an identification_assignment as described in comment to DNV-01. The use of organization relationships for a purpose as specific as this may require a business template or a specialization of this 'generic' template, and/or adding to the capability for such usage.

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

There is a need to identify product and support data both with an identifier code and the associated name as a pair since an entity instance may hold more than one identifier type (see DNV-01 above).

Proposal: Use template representing_code as proposed by DNV-40.

Comment: (TJT 2008/01/23)
The issue DNV-40 cannot be found in the context of issues raised against this template, or in any checklist. There is also no 'representing_code' template. Editor assumes that it is meant to refer to 'assigning_code'. There is nothing to stop a user from using BOTH an instance of the templates assigning_identification AND assigning_code to a product or support item to meet the stated requirement in the issue. An alternative is to create a new template drawn from both for this specific purpose. However, there is no need to change the existing template to meet this requirement.

Closed issue Issue: DNV-46 by Sylvia Schwab on behalf of DNV (07-03-07) editorial issue
Resolution: Accept. Status: closed

Parameter org_id is missing in the graphic 5.2 template summary (graphical parameter list)

Comment: (TJT 2008/01/23)
Fixed.

Closed issue Issue: RBN-1 by Rob Bodington (07-04-03) minor_technical issue
Resolution: Accept. Status: closed

The identification_assignment must be unique. This requires a uniqueness rule.
Comment: (Rob Bodington 07-04-03)
Added uniqueness rule

Closed issue Issue: RBN-2 by Rob Bodington (07-04-18) minor_technical issue
Resolution: Accept. Status: closed

There should be a description of how to handle situations where the identification is unknown. For example, PLCS mandates that a part has a version, but the company may not version parts - just use the latest version. This is discussed in the representing_part capability and template where /NULL is used for the identification
Comment: (TJT 2008/01/23)
Agree - usage added as a boxed note.

Closed issue Issue: RBN-3 by Rob Bodington (07-08-06) minor_technical issue
Resolution: Accept. Status: closed

The path states: Identification_assignment.description = '$' It should be: Identification_assignment.description = '/IGNORE'
Comment: (TJT 2008/01/23)
Updated.

Closed issue Issue: RBN-4 by Rob Bodington (07-08-06) minor_technical issue
Resolution: Accept. Status: closed

Figure 1 Template Configuration for Assigning Identification Identification_assignment.role should be set to '/IGNORE'
Comment: (TJT 2008/01/23)
Updated.

Closed issue Issue: RBN-5 by Rob Bodington (07-08-06) minor_technical issue
Resolution: Accept. Status: closed

The template contains the Unique constraint Unique constraint: Unique identifier There shall be at most one instance of the entity (Identification_assignment) within the data set uniquely identified by a combination of the following template parameters: id, id_class_name, id_ecl_id, org_id, org_id_class_name, org_id_ecl_id. The instance is referenced by the following template parameter: id_assgn. This constraint is over restrictive. For example, if you have two PARTs A and B, each which have a PART_VERSION at version 1. The constraint means that there will be one instance of IDENTIFICATION_ASSIGNMENT assigned to both PART_VERSIONs E.g. #42083=IDENTIFICATION_ASSIGNMENT('version 1','/IGNORE','$',(#128690,#130652)) Whilst correct according to the model, it means that you cannot assign any dates or effectivity to the IDENTIFICATION_ASSIGNMENT. It would be better if the IDENTIFICATION_ASSIGNMENT entity was split into the Identifier and the assignment of the identifier. As it stands it does both. Rather than changing the model, the Unique constraint should be removed and then applied when using the IDENTIFICATION_ASSIGNMENT. For example, there should be a unique constraint in the Template representing_part that states Unique constraint: Unique part version There shall be at most one instance of the entity (Part_version) within the data set uniquely identified by a combination of the following template parameters: part_id, part_id_class_name, part_id_ecl_id, part_org_id, part_org_id_class_name, part_vn_id, part_vn_id_class_name, part_vn_id_ecl_id, part_vn_org_id, part_vn_org_id_class_name. The instance is referenced by the following template parameter: version. This rule means that there can be only one version (Part_version) of a part (Part) with any given identifier.
Comment: (TJT 2008/01/23)
Agree that usage constraint needs to be applied when/where used. Have commented out the rules. Did not remove in case required elsewhere..
Comment: (Rob Bodington 08-02-11)
Actually, we do need a uniqueness constraint on the template. As it stands the same item can have the same identification assigned multiple times. E.g. Part no 23 can be assigned multiple times to the same part. The way around this is to add a constraint that ensures that an identifier can only be assigned once to an item. I.e. include the "items" parameter in the constraint. The uniqueness constraint needs to state: Unique constraint: Unique identifier There shall be at most one instance of the entity (Identification_assignment) within the data set uniquely identified by a combination of the following parameters on this template (assigning_identification) namely: id, id_class_name, id_ecl_id, org_id, org_id_class_name, org_id_ecl_id, items. The instance is referenced by the following template parameter: id_assgn.
Comment: (TJT 2008/02/11)
Rule(s) added as described.

Closed issue Issue: GYL-1 by Leif Gyllstrom (07-11-20) minor_technical issue
Resolution: Accept. Status: closed

Add Document_assignment to the Characterization section. This allows for a reference to a document that contains a description on the encoding system used for the assigned identification. The issue is a result of the DEX3 Harmonization Workshops.(2007).
Comment: (TJT 2008/01/23)
Agreed

Closed issue Issue: RBN-6 by Rob Bodington (07-11-21) minor_technical issue
Resolution: Accept. Status: closed

When the sending system does not know or manage the value of the identifier, the it should default to /NULL. This should be documented in this template
Comment: (TJT 2008/01/23)
Identical to RBN-2

Closed issue Issue: LOGSA-RI-1 by , LOGSA (2007-10-25) editorial issue
Resolution: Accept. Status: closed

Issue file: D:\users\rbn\projects\010937_DNV_dexlib\docs\review\LOGSA Template Reviews\template_issues.xls Template: assigning_identification Check list clause: "inst_tmpl.png" missing ing "images' folder
Comment: (TJT 2008/01/23)
Fixed.

Closed issue Issue: LOGSA-RI-2 by , LOGSA (2007-10-25) editorial issue
Resolution: Accept. Status: closed

Issue file: D:\users\rbn\projects\010937_DNV_dexlib\docs\review\LOGSA Template Reviews\template_issues.xls Template: assigning_identification Check list clause: All images are missing the reference to their master file
Comment: (TJT 2008/01/23)
Fixed.

Closed issue Issue: LOGSA-RI-3 by , LOGSA (2007-10-25) editorial issue
Resolution: Accept. Status: closed

Issue file: D:\users\rbn\projects\010937_DNV_dexlib\docs\review\LOGSA Template Reviews\template_issues.xls Template: assigning_identification Check list clause: All figures are compiled into 2 editable source files instead of separate files for each figure.
Comment: (TJT 2008/01/23)
Fixed.

Closed issue Issue: LOGSA-RI-4 by , LOGSA (2007-10-25) editorial issue
Resolution: Accept. Status: closed

Issue file: D:\users\rbn\projects\010937_DNV_dexlib\docs\review\LOGSA Template Reviews\template_issues.xls Template: assigning_identification Check list clause: Reviewers not identified
Comment: (TJT 2008/01/23)
Current identification of company to carry out reviews are sufficient.

Closed issue Issue: LOGSA-RI-5 by , LOGSA (2007-10-25) major_technical issue
Resolution: Accept. Status: closed

Issue file: D:\users\rbn\projects\010937_DNV_dexlib\docs\review\LOGSA Template Reviews\template_issues.xls Template: assigning_identification Check list clause: Major technical issues are open.
Comment: (TJT 2008/01/23)
Fixed.

Closed issue Issue: LOGSA-RI-6 by , LOGSA (2007-10-25) editorial issue
Resolution: Accept. Status: closed

Issue file: D:\users\rbn\projects\010937_DNV_dexlib\docs\review\LOGSA Template Reviews\template_issues.xls Template: assigning_identification Check list clause: Found parentheses, not brackets
Comment: (TJT 2008/01/23)
Cannot locate issue from description provided - need more information.

Closed issue Issue: LOGSA-RI-7 by , LOGSA (2007-10-25) minor_technical issue
Resolution: Accept. Status: closed

Issue file: D:\users\rbn\projects\010937_DNV_dexlib\docs\review\LOGSA Template Reviews\template_issues.xls Template: assigning_identification Check list clause: Not in plcs_registered.owl
Comment: (TJT 2008/01/23)
Cannot locate issue from description provided - need more information.

Closed issue Issue: DNV-80 by Fredrik Lied Larsen, DNV (2007-11-15) editorial issue
Resolution: Accept. Status: closed

Issue file: D:\users\rbn\projects\010937_DNV_dexlib\docs\review\checklists_12_07\template_issues_Frell_temp.xls Template: Assigning_identification Check list clause: 5 Missing assgn_id_inst.png and assgn_id_inst_tmpl.png
Comment: (TJT 2008/01/23)
Fixed.

Closed issue Issue: DNV-81 by Fredrik Lied Larsen, DNV (2007-11-15) minor_technical issue
Resolution: Accept. Status: closed

Issue file: D:\users\rbn\projects\010937_DNV_dexlib\docs\review\checklists_12_07\template_issues_Frell_temp.xls Template: Assigning_identification Check list clause: 6 No master attribute is found within the figure tag
Comment: (TJT 2008/01/23)
Fixed.

Closed issue Issue: DNV-82 by Fredrik Lied Larsen, DNV (2007-11-15) minor_technical issue
Resolution: Accept. Status: closed

Issue file: D:\users\rbn\projects\010937_DNV_dexlib\docs\review\checklists_12_07\template_issues_Frell_temp.xls Template: Assigning_identification Check list clause: 8 There are no editable files for the figure images.
Comment: (TJT 2008/01/23)
Fixed.

Closed issue Issue: DNV-83 by Fredrik Lied Larsen, DNV (2007-11-15) minor_technical issue
Resolution: Accept. Status: closed

Issue file: D:\users\rbn\projects\010937_DNV_dexlib\docs\review\checklists_12_07\template_issues_Frell_temp.xls Template: Assigning_identification Check list clause: 16 Figures are hyperlinked in the html page but the links are wrong, they do not lead to the correct figure. Also the template.xml file is missing figure_ref.
Comment: (TJT 2008/01/23)
Infrastructure issue - raised http://www.eurostep.fi/bugs/show_bug.cgi?id=1184

Closed issue Issue: DNV-84 by Fredrik Lied Larsen, DNV (2007-11-15) major_technical issue
Resolution: Accept. Status: closed

Issue file: D:\users\rbn\projects\010937_DNV_dexlib\docs\review\checklists_12_07\template_issues_Frell_temp.xls Template: Assigning_identification Check list clause: 21 2 major technical issues and 1 editorial issue open
Comment: (TJT 2008/01/23)
Fixed.

Closed issue Issue: DNV-85 by Fredrik Lied Larsen, DNV (2007-11-15) major_technical issue
Resolution: Accept. Status: closed

Issue file: D:\users\rbn\projects\010937_DNV_dexlib\docs\review\checklists_12_07\template_issues_Frell_temp.xls Template: Assigning_identification Check list clause: 22 1 major technical issue open
Comment: (TJT 2008/01/23)
Capabilities are not the subject of standardisation, nor are they in scope for editing at this time.

Closed issue Issue: DNV-86 by Fredrik Lied Larsen, DNV (2007-11-15) editorial issue
Resolution: Accept. Status: closed

Issue file: D:\users\rbn\projects\010937_DNV_dexlib\docs\review\checklists_12_07\template_issues_Frell_temp.xls Template: Assigning_identification Check list clause: 37 The URN "urn:plcs:rdl:std" has not been used consistently throughout the model diagram section, Org_assg_ecl_id='http://www.plcsinc.org'
Comment: (TJT 2008/01/23)
Fixed.

Closed issue Issue: DNV-87 by Fredrik Lied Larsen, DNV (2007-11-15) editorial issue
Resolution: Accept. Status: closed

Issue file: D:\users\rbn\projects\010937_DNV_dexlib\docs\review\checklists_12_07\template_issues_Frell_temp.xls Template: Assigning_identification Check list clause: 40 The attribute 'role' has not been given appropriate value.
Comment: (TJT 2008/01/23)
Fixed.

Closed issue Issue: DNV-88 by Fredrik Lied Larsen, DNV (2007-11-15) editorial issue
Resolution: Accept. Status: closed

Issue file: D:\users\rbn\projects\010937_DNV_dexlib\docs\review\checklists_12_07\template_issues_Frell_temp.xls Template: Assigning_identification Check list clause: 60 Values for attributes 'role' and 'description' are not consistent with drawing.
Comment: (TJT 2008/01/23)
Fixed.

Closed issue Issue: DNV-89 by Fredrik Lied Larsen, DNV (2007-11-15) editorial issue
Resolution: Accept. Status: closed

Issue file: D:\users\rbn\projects\010937_DNV_dexlib\docs\review\checklists_12_07\template_issues_Frell_temp.xls Template: Assigning_identification Check list clause: 67 Example is duplicated
Comment: (TJT 2008/01/23)
Fixed.

Closed issue Issue: DNV-90 by Fredrik Lied Larsen, DNV (2007-11-15) editorial issue
Resolution: Accept. Status: closed

Issue file: D:\users\rbn\projects\010937_DNV_dexlib\docs\review\checklists_12_07\template_issues_Frell_temp.xls Template: Assigning_identification Check list clause: 70 Entity 'Part' has not been marked with grey
Comment: (TJT 2008/01/23)
Fixed.

Closed issue Issue: DNV-91 by Fredrik Lied Larsen, DNV (2007-11-15) editorial issue
Resolution: Accept. Status: closed

Issue file: D:\users\rbn\projects\010937_DNV_dexlib\docs\review\checklists_12_07\template_issues_Frell_temp.xls Template: Assigning_identification Check list clause: 74 Rectangle filled white and has black border lines and arrow
Comment: (TJT 2008/01/23)
Fixed.

Closed issue Issue: DNV-92 by Fredrik Lied Larsen, DNV (2007-11-15) editorial issue
Resolution: Accept. Status: closed

Issue file: D:\users\rbn\projects\010937_DNV_dexlib\docs\review\checklists_12_07\template_issues_Frell_temp.xls Template: Assigning_identification Check list clause: 79 Black arrow is used for template in example
Comment: (TJT 2008/01/23)
Fixed.

Closed issue Issue: DNV-93 by Fredrik Lied Larsen, DNV (2007-11-15) editorial issue
Resolution: Accept. Status: closed

Issue file: D:\users\rbn\projects\010937_DNV_dexlib\docs\review\checklists_12_07\template_issues_Frell_temp.xls Template: Assigning_identification Check list clause: 82 The reference items from identification_assignment refers to Part #2 but in example it says #1
Comment: (TJT 2008/01/23)
Fixed.

Closed issue Issue: DNV-94 by Fredrik Lied Larsen, DNV (2007-11-15) editorial issue
Resolution: Accept. Status: closed

Issue file: D:\users\rbn\projects\010937_DNV_dexlib\docs\review\checklists_12_07\template_issues_Frell_temp.xls Template: Assigning_identification Check list clause: 83 Rectangle filled white and has black border lines
Comment: (TJT 2008/01/23)
Fixed.

Closed issue Issue: DNV-95 by Fredrik Lied Larsen, DNV (2007-11-15) editorial issue
Resolution: Accept. Status: closed

Issue file: D:\users\rbn\projects\010937_DNV_dexlib\docs\review\checklists_12_07\template_issues_Frell_temp.xls Template: Assigning_identification Check list clause: 85 Black arrow is used for template in example
Comment: (TJT 2008/01/23)
Fixed.

Closed issue Issue: DNV-96 by Fredrik Lied Larsen, DNV (2007-11-15) minor_technical issue
Resolution: Accept. Status: closed

Issue file: D:\users\rbn\projects\010937_DNV_dexlib\docs\review\checklists_12_07\template_issues_Frell_temp.xls Template: Assigning_identification Check list clause: 90 Many faults, missing EXPRESS-G, wrong drawing form for example.
Comment: (TJT 2008/01/23)
Updated.

Closed issue Issue: RBN-7 by Rob Bodington (07-11-20) minor_technical issue
Resolution: Accept. Status: closed

There should be some text explaining what to do when the id is not know - or is not provided - for example versions of a part may not be known. The suggestion is to use /NULL etc as specified in dexlib/help/dex/impl_trans.htm
Comment: (TJT 2008/01/23)
Identical to RBN-2 and RBN-6