Org.Sdmx.Resources.SdmxMl.Schemas.V20 8.18.6

• .NETStandard 2.0

  • XObjects (>= 8.18.6)

# Changelog

## 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 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)
-