EDCS Reference Manual
Concept Mapping from FACC 2.1 to EDCS 4.4 Types FACC_2p1_Mapping_Type_Code |
---|
/* * REGISTERABLE ENUM: FACC_2p1_Mapping_Type_Code * * Specifies the type and multiplicity of a given forward * mapping. */ typedef EDCS_Integer FACC_2p1_Mapping_Type_Code;
Enumerant | Definition | Value |
---|---|---|
FACC_MAP_TYP_ONE_TO_ZERO | There is no forward mapping for the given concept. In any mapping data structure with an entry list, the entry list will be null. Check the information field for relevant information. |
1 |
FACC_MAP_TYP_ONE_TO_ONE | The given concept has an exact mapping to a single concept in the target version of EDCS. In any mapping data structure with an entry list, there will be exactly one unique replacement entry in the list. There may or may not be information in the information field for this case. |
2 |
FACC_MAP_TYP_ONE_TO_ONE_QUALIFIED | The given concept has been mapped to two or more concepts in the target version of EDCS. This occurs only within mapping data structures that have entry lists. In this case, the entry list will have more than 1 entry, and the information field may have relevant information. Examples:
|
3 |
FACC_MAP_TYP_ONE_TO_ONE_CONDITIONAL | The given concept has a single exact replacement, but it is either the old concept was an EA whose enumerants did not all map to the same EA, or it mapped to a different concept. Examples:
|
4 |
FACC_MAP_TYP_CHANGE_IN_DATATYPE | The concept has a one-to-one mapping, but the datatype used to realize the concept has changed. Examples:
|
5 |
FACC_MAP_TYP_CHANGE_TO_CHARACTERISTIC | The concept has a one-to-one mapping, but the new concept is an EDCS Value Characteristic Concept. Examples:
|
6 |
FACC_MAP_TYP_SPECIAL_CASE | The mapping from this concept is not implemented in the code but the description of the mapping will be in the information field of the mapping structure. There will be no mapping entries in the list. |
7 |
|