Merge pull request #261 from sdmx-twg/develop

Publish version 2.2.2

Author: sosna

api/sdmx-rest.yaml

@@ -1,7 +1,7 @@
 openapi: 3.0.0
 info:
-  version: '2.2.1'
-  title: 'SDMX RESTful API, v2.2.1'
+  version: '2.2.2'
+  title: 'SDMX RESTful API, v2.2.2'
   description: |
     The RESTful API for SDMX 3.1.
     
@@ -868,6 +868,15 @@ components:
     "200":
       description: OK
       content:
+        application/vnd.sdmx.data+json;version=2.1.0:
+          schema:
+            type: string
+        application/vnd.sdmx.data+csv;version=2.1.0:
+          schema:
+            type: string
+        application/vnd.sdmx.data+xml;version=3.1.0:
+          schema:
+            type: string
         application/vnd.sdmx.data+json;version=2.0.0:
           schema:
             type: string
@@ -898,6 +907,18 @@ components:
     "200-schemas":
       description: OK
       content:
+        application/vnd.sdmx.schema+xml;version=3.1.0:
+          schema:
+            type: string
+        application/vnd.sdmx.schema+json;version=2.1.0:
+          schema:
+            type: string
+        application/vnd.sdmx.structure+xml;version=3.1.0:
+          schema:
+            type: string
+        application/vnd.sdmx.structure+json;version=2.1.0:
+          schema:
+            type: string
         application/vnd.sdmx.schema+xml;version=3.0.0:
           schema:
             type: string
@@ -919,6 +940,12 @@ components:
     "200-struct":
       description: OK
       content:
+        application/vnd.sdmx.structure+xml;version=3.1.0:
+          schema:
+            type: string
+        application/vnd.sdmx.structure+json;version=2.1.0:
+          schema:
+            type: string
         application/vnd.sdmx.structure+xml;version=3.0.0:
           schema:
             type: string
@@ -934,6 +961,15 @@ components:
     "200-meta":
       description: OK
       content:
+        application/vnd.sdmx.metadata+json;version=2.1.0:
+          schema:
+            type: string
+        application/vnd.sdmx.metadata+xml;version=3.1.0:
+          schema:
+            type: string
+        application/vnd.sdmx.metadata+csv;version=2.1.0:
+          schema:
+            type: string
         application/vnd.sdmx.metadata+json;version=2.0.0:
           schema:
             type: string

doc/availability.md

@@ -46,7 +46,7 @@ Operators appear as prefix to the component value(s) and are separated from it b
 As already mentioned, the response from the Data Availability API is an SDMX AvailabilityConstraint containing a CubeRegion which defines the distinct Values for each Dimension of the data. These distinct values contained in the CubeRegion are determined by the server based on the data query presented to this API.  The meaning of the distinct values depends on the response mode.
 
 > [!TIP]
-> Some servers treat square brackets (`[` and `]`) as invalid characters in URLs. If the issue occurs, please encode them using `%5B` and `%5D` respectively.    
+> Some servers treat square brackets (`[` and `]`) as invalid characters in URLs. If the issue occurs, please encode them using `%5B` and `%5D` respectively.
 
 ### Response Mode
 
@@ -139,9 +139,11 @@ Included references are:
 
 ## Response types
 
-The following media types can be used with _availability_ queries:
+The following media types can be used with *availability* queries:
 
-- **application/vnd.sdmx.structure+json;version=2.0.0**
+- **application/vnd.sdmx.structure+json;version=2.1.0**
+- application/vnd.sdmx.structure+xml;version=3.1.0
+- application/vnd.sdmx.structure+json;version=2.0.0
 - application/vnd.sdmx.structure+xml;version=3.0.0
 
 The default format is highlighted in **bold**.