Org.Sdmx.Resources.SdmxMl.Schemas.V20 8.17.3-rc

• .NETStandard 2.0

  • XObjects (>= 8.17.3-rc)

# Changelog

## 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 AnnotationTitle, followup of SDMXRI-2136 (OECD,PULL_REQUEST)
- SDMXRI-2155: add parameter to add "-" and '*' as wildcard symbols to DataQueryImpl filter  (OECD,PULL_REQUEST)

## sdmxsource.net v8.16.0 (2023-05-04)

### Details v8.16.0

1. This release contains fixes and enhancements from OECD
  1. In OECD  for referential metadata the string `-` is used as an intentionally missing value for dimension (normal and time dimension) and has a different treatment to an empty string when imported. But during writing the passed string for a Time dimension was tried to be parsed as SDMX time and was throwing an exception. This change is to avoid an exception and allow the minus symbol the same as an empty string.
  1. SDMX-JSON 2.0.0 better handle datasets with delete action and metadata attribute usage, e.g. in data requests with `updatedAfter`.
  1. Support a special annotation that emulates SDMX 3.0.0 Hierarchical association that allows including hierarchical codelist in SDMX-JSON data

### Tickets v8.16.0

The following new features added:

- SDMXRI-2146: Treat "-" as an empty string when parsing datetime with DateUtil (OECD,PULL_REQUEST)
- SDMXRI-2141: Support metadata output in json/csv with updatedAfter parameter (multiple datasets) (OECD,PULL_REQUEST)
- SDMXRI-2138: write deleted observations as single datasets when updatedAfter parameter is used (OECD,PULL_REQUEST)
- SDMXRI-2136: SDMX-JSON data: Return definition of parents when child items have data, use hierachical codelist through annotation definition. Addon to SDMXRI-2037 (OECD,PULL_REQUEST)
- SDMXRI-2045: Retrieve empty textual intentionally missing measures in xml

The following bugs have been corrected:

- SDMXRI-2051: Json writer throws an error for DSD with a single non-time dimension (OECD,PULL_REQUEST)

## sdmxsource.net v8.15.1 (2023-02-22)

### Details v8.15.1

1. Add a conditional parameter to JsonWriter 2.0 and NSI to include parent codes without data , that have children with data. Use parent-child relation from a hierarchical codelist, that might be attached to DSD/Dataflow through an annotation.

### Tickets v8.15.1

The following new features added:

- SDMXRI-2037: SDMX-JSON data: Return definition of parents when child items have data, use hierachical codelist through annotation definition. (OECD,PULL_REQUEST)

## sdmxsource.net v8.15.0 (2023-01-26)

### Details v8.15.0

1. Support dimensions with missing values in json format
1. Text format data type `Count` should be considered numeric data type.
1. Ignore duplicate key/attribute values entries in Cube Regions

### Tickets v8.15.0

The following new features added:

- SDMXRI-2023: Support dimensions with NULL values in JSON writer (OECD needs to output wildcarded observations) (OECD,PULL_REQUEST)
- SDMXRI-2029: Update textType Count as numeric (OECD,PULL_REQUEST)
- SDMXRI-2025: Retrieve intentionally missing values (OECD,PULL_REQUEST)

The following bugs have been corrected:

- SDMXRI-2028: Expecting error when uploading content constraint with duplicated codes in a repeated concept

## sdmxsource.net v8.13.0 (2022-11-25)

### Details v8.13.0

1. Improve complete stub support via REST
1. Support multiple multiple actions in SDMX-CSV
1. SDMX-CSV can use now culture specific decimal separator
1. Extension HTTP header `X-Range` for Range requests.
1. Updated 3rd party dependencies.

##