Used to cover residual information not contained in other categories of the code list (in some _O Other contexts, e.g. classifications, referred to as n.e.s., not elsewhere specified, n.e.c., not elsewhere classified, etc.) _S Subtotal Used for expressing intermediate totals _T Total Used for expressing totals Failure to obtain a measurement (e.g. non _U No data/unknown response, no data available, information not known by the respondent unit, etc.) Used where the value for a particular variable falls outside the expected range. An example could be the failure to allocate a classification to _X Not allocated/unspecified a particular unit due to insufficient information, and/or if further breakdown over any related items mentioned in code list not available Used in cases where the coding of a concept is technically required (dimension or mandatory attribute), but does not have a statistical meaning for a specific series or observation. Examples of relevant usages of _Z are: In a survey that has questions on Status” and of Partner”, “Marital “Sex for a response of Marital Status: Single, the relevant response for Sex of Partner is applicable” (_Z) “Not In a labour statistics reporting framework that has a dimension Labour Force Reason”. If the “Outside observation entity is inside of the labour force, the response for Outside Labour Force Reason is “Not applicable” (_Z) In macro-economic statistics, a DSD may contain a dimension for breakdowns of economic activity. _Z Not applicable Some series cannot be broken down by economic activity (e.g. statistical discrepancy between GDP approaches, certain taxes and subsidies, producer price index). They could be coded as applicable” (_Z) “Not for the activity dimension in the data message. The code _Z should be used sparsely, since it may complicate validation and transformation formulas or pivot visualisations based on SDMX messages. The code _T (Total) should be used instead in cases where the applicability of the concept is not entirely clear, and where the concept may be relevant only under certain circumstances, or where the applicability of a concept for a certain series or dataflow depends on the context (e.g. a tax breakdown that exists in one country but not in another) in order to simplify the coding across data flows and countries.
_O Other Used to cover residual information not contained in other categories of the code list (in some contexts, e.g. classifications, referred to as n.e.s., not elsewhere specified, n.e.c., not elsewhere classified, etc.) _S Subtotal Used for expressing intermediate totals _T Total Used for expressing totals _U No data/unknown Failure to obtain a measurement (e.g. non response, no data available, information not known by the respondent unit, etc.) _X Not allocated/unspecified Used where the value for a particular variable falls outside the expected range. An example could be the failure to allocate a classification to a particular unit due to insufficient information, and/or if further breakdown over any related items mentioned in code list not available _Z Not applicable Used in cases where the coding of a concept is technically required (dimension or mandatory attribute), but does not have a statistical meaning for a specific series or observation. Examples of relevant usages of _Z are: In a survey that has questions on “Marital Status” and “Sex of Partner”, for a response of Marital Status: Single, the relevant response for Sex of Partner is “Not applicable” (_Z) In a labour statistics reporting framework that has a dimension “Outside Labour Force Reason”. If the observation entity is inside of the labour force, the response for Outside Labour Force Reason is “Not applicable” (_Z) In macro-economic statistics, a DSD may contain a dimension for breakdowns of economic activity. Some series cannot be broken down by economic activity (e.g. statistical discrepancy between GDP approaches, certain taxes and subsidies, producer price index). They could be coded as “Not applicable” (_Z) for the activity dimension in the data message. The code _Z should be used sparsely, since it may complicate validation and transformation formulas or pivot visualisations based on SDMX messages. The code _T (Total) should be used instead in cases where the applicability of the concept is not entirely clear, and where the concept may be relevant only under certain circumstances, or where the applicability of a concept for a certain series or dataflow depends on the context (e.g. a tax breakdown that exists in one country but not in another) in order to simplify the coding across data flows and countries.