Issue raised against: assigning_codes

No explicit resources exist in AP239 to support exchange of codes in a robust manner. The proposed idea of populating Class.name with the code value may not be fully satisfactory. Some inputs to this discussion are forwarded by document 20050818_Codes and descriptors.doc (distributed by e-mail), and an alternative approach is indicated.

Suggest 2 para reworded.

Was:

Codes are often used to simplify the classification or characterization of a specific type of object. Each code is a shorthand for a specific term defined within a classification system. This type of codes are often used in legacy applications where the number of characters used were absolutly crucial. The amount of codes used by existing applications are to extencive to be expected to be defined in reference data libraries, prior to the realization of data exchanges including these codes.

Codes are often used to simplify the classification or characterization of a specific type of object. Each code is shorthand for a specific term defined within a classification system. This type of codes are often used in legacy applications where the code has a fixed character length and the different fields in the code have meaning.

Each individual code value used by existing applications could be defined in a reference data library prior to any data exchange. However, the number of codes in use is likely to make this prohibitive. Consequently the coded value will be exchanged and reference data used to define the type of the code.

Comment: (Leif Gyllstrom 05-10-10)
Change done according the proposal above.

I think that there is room for confusion between codes used as a classification and codes used for identification. A part number may well be a code. When it is used to identify a part, identification assignment should be used. I think that this needs to be stated in this capability. I also think that an example showing the classification of the part number should also be provided.

Suggest including something along the lines of:

Codes are strings that are structured according to some convention. Often different sets of characters within the string carry a particular meaning. For example, part numbers are sometimes made up of a set of strings, with each set carrying some meaning. For example, product function, manufacturing plant etc. Structured codes are traditionally used for two purposes:

Identification - the code provides an identifier for something. For example a part number or serial number.

Classification - the content and structure of a code provides information about the classification of whatever the code is assigned to. For example, the first 4 characters in a part number may indicate the function of the part. NATO Stock Numbers are examples where this is the case.

Where the code is being used for identification, the capability C001: assigning_identifiers should be used.

This capability, assigning_codes, should only be used

Comment: (Leif Gyllstrom 05-10-10)
Clarification provided within the additional usage section.

Comment: (Leif Gyllstrom 05-10-10)
Changed the template name to assigning_code.

Comment: (Leif Gyllstrom 05-10-04)
Done.