Estat.SdmxSource.SdmxParseBase 8.18.8

• .NETStandard 2.0

  • Estat.SdmxSource.SdmxAPI (>= 8.18.8)
  • Estat.SdmxSource.SdmxMlConstants (>= 8.18.8)
  • Estat.SdmxSource.SdmxObjects (>= 8.18.8)

# Changelog

## sdmxsource.net-dotstat v8.18.8 (2024-02-09)

### Details v8.18.8

1. Fixed the bug at the textual values with double quotes (") making the JSON response invalid, as they are not properly escaped in the extracted SDMX-JSON format. The escaping was applied to all textual values, thus un-coded dimensions and textual observation and attribute values. The issue doesn't occur in SDMX-CSV or SDMX-ML.
1. Fixed the json error "409 : Could not find code '' in codelist" caused by empty values.
1. Fixed escaping issues encountered at observation values in JSON data messages.

### Tickets v8.18.8

The following bugs have been corrected:

- SDMXRI-2296 Properly escape double quotes in text values in SDMX-JSON exports
- SDMXRI-2307 Fix unnecessary json error 409 Could not find code in codelist
- SDMXRI-2363 Use native json writer methods to escape observation value for non-numerical measure

## sdmxsource.net-dotstat v8.18.7 (2023-11-20)

### Details v8.18.7

1. Fix 'Unable to generate SQL' bug which occurs when range header is used and metadata should also be returned (either availability or actual metadata)
1. Added a new constructor to DatasetHeaderCore that has structureUsage parameter
1. Added support of `labels=name` option in SDMX-CSV 2.0

### Tickets v8.18.7

The following new features added:

- SDMXRI-2182 Fix STRUCTURE_NAME column with metadata queries
- SDMXRI-2285 Added a new constructor to DatasetHeaderCore that has structureUsage parameter

The following bugs have been corrected:

- SDMXRI-2220 Msd populated when range header is used

## sdmxsource.net-dotstat v8.18.5 (2023-10-13)

### Details v8.18.5

1. SDMX-CSV 2.0.0 improvements
  1. Validity period columns
  1. Multile structures

### Tickets v8.18.5

The following new features added:

- SDMXRI-2256: IncludeHistory parameter should return extra columns for validFromDate and validToDate values in CSV v2.0 (OECD,PULL_REQUEST)
- SDMXRI-2223: Update csv 2.0 reader to allow multiple structures in a source file (OECD)

## sdmxsource.net v8.18.4 (2023-09-08)

### Details v8.18.4

### Tickets v8.18.4

The following new features added:

- SDMXRI-2217: Only the value property should be used for non-coded components in the structure part of SDMX-JSON 2.0 data messages (OECD,PULL_REQUEST)
- SDMXRI-2213: Introduce asOf parameter in NSIWS that will return historical data present at the given time (OECD,PULL_REQUEST)
- SDMXRI-2215: Fix vulnerabilities of NSI WS docker image revealed by docker scout (OECD,PULL_REQUEST)

## sdmxsource.net v8.18.0 (2023-08-01)

### Details v8.18.0

1. Support for SDMX-CSV 2.0.0 `labels=name`
1. Output UTC date in some cases related to embargo date attribute
1. Fix typo in namespace for SDMX 2.1 data files
1. Use [central package management](https://learn.microsoft.com/en-us/nuget/consume-packages/central-package-management), versions of dependencies from all projects are stored in `Directory.Packages.props`.

### Tickets v8.18.0

The following new features added:

- SDMXRI-2161: Publish pre-release nuget packages to nuget.org (OECD)
- SDMXRI-2182: Implement SDMX-CSV 2.0 `labels=name` option (OECD,PULL_REQUEST)
- SDMXRI-2180: Restricted access to confidential or embargoed data (OECD,PULL_REQUEST)

The following bugs have been corrected:

- SDMXRI-2145: Malformed smdx.org URL when using structurespecificdata query param

## sdmxsource.net v8.17.0 (2023-06-07)

### Details v8.17.0

1. SDMX-JSON data writer enhancements
  1. allow use of special characters (`~`, `*`) in metadata response
  1. Changes in HCL support in data
1. SDMX-JSON Data changes in HCL support
1. Align with final standard approach agreed in SDMX-TWG.

|Format|Numeric types: float, double|Text types|
|------|----------------------------|----------|
|XML|NaN|#N/A|
|JSON|NaN|#N/A|
|CSV|NaN|#N/A|

- Change the NSIWS data-writers to return these special values accordingly.
 - For Text types there should not be any special treatement because they should be already stored and returned from the data database as {{#N/A}}
 - For float and double, make sure that {{NaN}} can be parsed accordingly to all three formats. Specially to JSON.
- Remove from NSIWS the config. setting [useIntentionallyMissingMeasures|https://gitlab.com/sis-cc/.stat-suite/dotstatsuite-core-sdmxri-nsi-ws/-/blob/develop/config/Properties.json] which is not used anymore

### Tickets v8.17.0

The following new features added:

- SDMXRI-2164: Update json 2.0 writer to use special characters (~,*) in metadata response (OECD,PULL_REQUEST)
- SDMXRI-2163: NaN managed as intentionally missing value (OECD,PULL_REQUEST)
- SDMXRI-1924: Add a new HTTP X-Level option to get the referential metadata only at the current level (2021.0333-QTM5,OECD,PULL_REQUEST)
- SDMXRI-2157: HCL parents output in SDMX-json,  use first localised HCL definition from AnnotationText and then non-localised HCL from