How are codes and literals handled and why?
The source data requirements that were analyzed and found to be inconsistent in their use of codes. For components with the same meaning, some sources used codes while others used literals. When codes were used, they were not always drawn from the same code table. Some code tables are specific to local jurisdictions. In order to provide maximum flexibility, the Global JXDM usually provides both a code type element and a text type element (that may contain a literal). There are particular code tables that are always common, such as those published by the National Criminal Information Center (NCIC)-2000 and the American Association of Motor Vehicle Administrators (AAMVA). Therefore, the GXSTF provided a mechanism to use codes from other namespaces. This enables the use of standards without restriction to a single internal set of values. This also does not require a change to the Global JXDM namespace every time external standards change. For example, the GXSTF has created an NCIC-2000 sc
The source data requirements that were analyzed were not consistent in their use of codes. For components with the same meaning, some sources used codes, others used literals. When codes were used, they were not always drawn from the same code table. Some code tables are specific to local jurisdictions. In order to provide maximum flexibility, GJXDD v3 usually provides both a code type element and a text type element (that may contain a literal). There are particular code tables that are always common, for example NCIC-2000 and the American Association of Motor Vehicle Administrators (AAMVA). Therefore, the XML Structure Task Force (XSTF) provided a mechanism to use codes from other namespaces. This enables the use of standards without restriction to a single internal set of values. This also does not require a change to the justice data model namespace when every time external standards change. For example, the XSTF has created an NCIC-2000 schema in its own namespace that contains th
