diff --git a/.github/workflows/docs.yml b/.github/workflows/docs.yml
index 4e8f4f28..83dbed5b 100644
--- a/.github/workflows/docs.yml
+++ b/.github/workflows/docs.yml
@@ -5,22 +5,21 @@ on:
   push:
     branches:
       - draft
-      - draft-2.0
       - master
 jobs:
   deploy:
     runs-on: ubuntu-latest
     steps:
       - name: Inject env variables
-        uses: rlespinasse/github-slug-action@v3.x
-      - uses: actions/setup-node@v3
+        uses: rlespinasse/github-slug-action@v4
+      - uses: actions/setup-node@v4
         with:
           node-version: 'lts/*'
-      - uses: actions/checkout@v3
+      - uses: actions/checkout@v4
       - run: |
           npm install
           npm run generate
-        working-directory: tests
+        working-directory: dev
       - name: clone gh-pages and clean-up
         if: ${{ env.GITHUB_REF_SLUG == 'master' }}
         run: |
@@ -32,8 +31,8 @@ jobs:
         if: ${{ env.GITHUB_REF_SLUG != 'master' }}
         run: mkdir gh-pages
       - run: |
-          cp tests/docs.html index.html
-          cp tests/processes.json processes.json
+          cp dev/docs.html index.html
+          cp dev/processes.json processes.json
           rsync -vrm --include='*.json' --include='*.html' --include='meta/***' --include='proposals/***' --exclude='*' . gh-pages
       - name: deploy to root (master)
         uses: peaceiris/actions-gh-pages@v3
diff --git a/.github/workflows/tests.yml b/.github/workflows/tests.yml
index b108eb18..8781b1fa 100644
--- a/.github/workflows/tests.yml
+++ b/.github/workflows/tests.yml
@@ -4,12 +4,12 @@ jobs:
   deploy:
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/setup-node@v3
+      - uses: actions/setup-node@v4
         with:
           node-version: 'lts/*'
-      - uses: actions/checkout@v3
-      - name: Run tests
+      - uses: actions/checkout@v4
+      - name: Run linter
         run: |
           npm install
-          npm run test
-        working-directory: tests
\ No newline at end of file
+          npm test
+        working-directory: dev
\ No newline at end of file
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 407447dc..fd7f315f 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -6,8 +6,48 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## Unreleased / Draft
 
+### Added
+
+- New processes in proposal state:
+    - `combine_cubes`
+
+- Implementation guide for implementing OGC API - Processes in openEO
+- `export_collection`
+- `export_workspace`
+- `run_ogcapi`
+- `run_ogcapi_externally`
+- `stac_modify`
+
+### Changed
+
+- `clip`: Throw an exception if min > max [#472](https://github.com/Open-EO/openeo-processes/issues/472)
+- `save_results`: Returns the STAC resource instead of boolean `true` [API#376](https://github.com/Open-EO/openeo-api/issues/376)
+- Added a uniqueness contraint to various array-typed parameters (e.g. lists of dimension names or labels)
+- Renamed `create_data_cube` to `create_cube`. [#68](https://github.com/Open-EO/openeo-processes/issues/68)
+- `apply_polygon`: Renamed `polygons` parameter to `geometries` for better alignment with other geometry handling processes. [#511](https://github.com/Open-EO/openeo-processes/issues/511)
+
+### Fixed
+
+- Clarified for various mathematical functions the defined input and output ranges. Mention that `NaN` is returned outside of the defined input range where possible.
+- `apply_polygon`: Replaced outdated usage of `raster-cube` subtype with `datacube` and dimensions. [#524](https://github.com/Open-EO/openeo-processes/issues/524)
+- `aggregate_temporal` and `aggregate_temporal_period`: Clarified that the process throws a `DimensionNotAvailable` exception when no temporal dimension exists.
+- `aggregate_temporal_period`: Removed unused exception `DistinctDimensionLabelsRequired`
+- `aggregate_temporal_period`: Clarified that the definition of weeks follows ISO 8601
+- `cummax`, `cummin`, `cumproduct`, `cumsum`: Clarified the descriptions around the `ignore_nodata` parameter.
+- `divide`: Clarified behavior for division by 0
+- `between`: Clarify that `null` is passed through.
+- `eq` and `neq`: Explicitly set the minimum value for the `delta` parameter.
+- `filter_bbox`, `load_collection`, `load_stac`: Clarified that the bounding box is reprojected to the CRS of the spatial data cube dimensions if required.
+- `filter_spatial`: Clarified that masking is applied using the given geometries. [#469](https://github.com/Open-EO/openeo-processes/issues/469)
+- `mod`: Clarified behavior for y = 0
+- `sqrt`: Clarified that NaN is returned for negative numbers.
+
 ## [2.0.0-rc.1] - 2023-05-25
 
+### Fixed
+
+- `array_append`: Added `number` type for labels to be consistent with other processes. Default to numerical index instead of string. Clarify that the `label` parameter only applies to labeled arrays.
+
 ### Added
 
 - New processes in proposal state:
diff --git a/README.md b/README.md
index 24c28899..621276b6 100644
--- a/README.md
+++ b/README.md
@@ -35,7 +35,7 @@ This repository contains a set of files formally describing the openEO Processes
 * [implementation.md](meta/implementation.md) in the `meta` folder provide some additional implementation details for back-ends. For back-end implementors, it's highly recommended to read them.
 * [subtype-schemas.json](meta/subtype-schemas.json) in the `meta` folder defines common data types (`subtype`s) for JSON Schema used in openEO processes.
 * Previously, an `examples` folder contained examples of user-defined processes. These have been migrated to the [openEO Community Examples](https://github.com/Open-EO/openeo-community-examples/tree/main/processes) repository.
-* The [`tests`](tests/) folder can be used to test the process specification for validity and consistent "style". It also allows rendering the processes in a web browser. Check the [tests documentation](tests/README.md) for details.
+* The [`dev`](dev/) folder can be used to test the process specification for validity and consistent "style". It also allows rendering the processes in a web browser. Check the [development documentation](dev/README.md) for details.
 
 ## Process
 
diff --git a/absolute.json b/absolute.json
index 3b6e91dc..c6a3713d 100644
--- a/absolute.json
+++ b/absolute.json
@@ -1,7 +1,7 @@
 {
     "id": "absolute",
     "summary": "Absolute value",
-    "description": "Computes the absolute value of a real number `x`, which is the \"unsigned\" portion of x and often denoted as *|x|*.\n\nThe no-data value `null` is passed through and therefore gets propagated.",
+    "description": "Computes the absolute value of a real number `x`, which is the \"unsigned\" portion of `x` and often denoted as *|x|*.\n\nThe no-data value `null` is passed through and therefore gets propagated.",
     "categories": [
         "math"
     ],
@@ -95,4 +95,4 @@
             "result": true
         }
     }
-}
\ No newline at end of file
+}
diff --git a/aggregate_temporal.json b/aggregate_temporal.json
index ad1d560b..2c66e0f2 100644
--- a/aggregate_temporal.json
+++ b/aggregate_temporal.json
@@ -128,6 +128,7 @@
             "description": "Distinct labels for the intervals, which can contain dates and/or times. Is only required to be specified if the values for the start of the temporal intervals are not distinct and thus the default labels would not be unique. The number of labels and the number of groups need to be equal.",
             "schema": {
                 "type": "array",
+                "uniqueItems": true,
                 "items": {
                     "type": [
                         "number",
@@ -140,7 +141,7 @@
         },
         {
             "name": "dimension",
-            "description": "The name of the temporal dimension for aggregation. All data along the dimension is passed through the specified reducer. If the dimension is not set or set to `null`, the data cube is expected to only have one temporal dimension. Fails with a `TooManyDimensions` exception if it has more dimensions. Fails with a `DimensionNotAvailable` exception if the specified dimension does not exist.",
+            "description": "The name of the temporal dimension for aggregation. All data along the dimension is passed through the specified reducer. If the dimension is not set or set to `null`, the data cube is expected to only have one temporal dimension. Fails with a `TooManyDimensions` exception if it has more dimensions. Fails with a `DimensionNotAvailable` exception if the specified dimension does not exist or no temporal dimension is available.",
             "schema": {
                 "type": [
                     "string",
@@ -228,7 +229,7 @@
             "message": "The data cube contains multiple temporal dimensions. The parameter `dimension` must be specified."
         },
         "DimensionNotAvailable": {
-            "message": "A dimension with the specified name does not exist."
+            "message": "A dimension with the specified name does not exist or no temporal dimension is available."
         },
         "DistinctDimensionLabelsRequired": {
             "message": "The dimension labels have duplicate values. Distinct labels must be specified."
diff --git a/aggregate_temporal_period.json b/aggregate_temporal_period.json
index bdaea43e..446afa8d 100644
--- a/aggregate_temporal_period.json
+++ b/aggregate_temporal_period.json
@@ -23,7 +23,7 @@
         },
         {
             "name": "period",
-            "description": "The time intervals to aggregate. The following pre-defined values are available:\n\n* `hour`: Hour of the day\n* `day`: Day of the year\n* `week`: Week of the year\n* `dekad`: Ten day periods, counted per year with three periods per month (day 1 - 10, 11 - 20 and 21 - end of month). The third dekad of the month can range from 8 to 11 days. For example, the third dekad of a year spans from January 21 till January 31 (11 days), the fourth dekad spans from February 1 till February 10 (10 days) and the sixth dekad spans from February 21 till February 28 or February 29 in a leap year (8 or 9 days respectively).\n* `month`: Month of the year\n* `season`: Three month periods of the calendar seasons (December - February, March - May, June - August, September - November).\n* `tropical-season`: Six month periods of the tropical seasons (November - April, May - October).\n* `year`: Proleptic years\n* `decade`: Ten year periods ([0-to-9 decade](https://en.wikipedia.org/wiki/Decade#0-to-9_decade)), from a year ending in a 0 to the next year ending in a 9.\n* `decade-ad`: Ten year periods ([1-to-0 decade](https://en.wikipedia.org/wiki/Decade#1-to-0_decade)) better aligned with the anno Domini (AD) calendar era, from a year ending in a 1 to the next year ending in a 0.",
+            "description": "The time intervals to aggregate. The following pre-defined values are available:\n\n* `hour`: Hour of the day\n* `day`: Day of the year\n* `week`: Week of the year as defined in [ISO 8601](https://en.wikipedia.org/wiki/ISO_8601#Week_dates)\n* `dekad`: Ten day periods, counted per year with three periods per month (day 1 - 10, 11 - 20 and 21 - end of month). The third dekad of the month can range from 8 to 11 days. For example, the third dekad of a year spans from January 21 till January 31 (11 days), the fourth dekad spans from February 1 till February 10 (10 days) and the sixth dekad spans from February 21 till February 28 or February 29 in a leap year (8 or 9 days respectively).\n* `month`: Month of the year\n* `season`: Three month periods of the calendar seasons (December - February, March - May, June - August, September - November).\n* `tropical-season`: Six month periods of the tropical seasons (November - April, May - October).\n* `year`: Proleptic years\n* `decade`: Ten year periods ([0-to-9 decade](https://en.wikipedia.org/wiki/Decade#0-to-9_decade)), from a year ending in a 0 to the next year ending in a 9.\n* `decade-ad`: Ten year periods ([1-to-0 decade](https://en.wikipedia.org/wiki/Decade#1-to-0_decade)) better aligned with the anno Domini (AD) calendar era, from a year ending in a 1 to the next year ending in a 0.",
             "schema": {
                 "type": "string",
                 "enum": [
@@ -78,7 +78,7 @@
         },
         {
             "name": "dimension",
-            "description": "The name of the temporal dimension for aggregation. All data along the dimension is passed through the specified reducer. If the dimension is not set or set to `null`, the source data cube is expected to only have one temporal dimension. Fails with a `TooManyDimensions` exception if it has more dimensions. Fails with a `DimensionNotAvailable` exception if the specified dimension does not exist.",
+            "description": "The name of the temporal dimension for aggregation. All data along the dimension is passed through the specified reducer. If the dimension is not set or set to `null`, the source data cube is expected to only have one temporal dimension. Fails with a `TooManyDimensions` exception if it has more dimensions. Fails with a `DimensionNotAvailable` exception if the specified dimension does not exist or no temporal dimension is available.",
             "schema": {
                 "type": [
                     "string",
@@ -115,10 +115,7 @@
             "message": "The data cube contains multiple temporal dimensions. The parameter `dimension` must be specified."
         },
         "DimensionNotAvailable": {
-            "message": "A dimension with the specified name does not exist."
-        },
-        "DistinctDimensionLabelsRequired": {
-            "message": "The dimension labels have duplicate values. Distinct labels must be specified."
+            "message": "A dimension with the specified name does not exist or no temporal dimension is available."
         }
     },
     "links": [
diff --git a/and.json b/and.json
index c24ce95b..3b28c8ef 100644
--- a/and.json
+++ b/and.json
@@ -1,7 +1,7 @@
 {
     "id": "and",
     "summary": "Logical AND",
-    "description": "Checks if **both** values are true.\n\nEvaluates parameter `x` before `y` and stops once the outcome is unambiguous. If any argument is `null`, the result will be `null` if the outcome is ambiguous.\n\n**Truth table:**\n\n```\na \\ b || null  | false | true\n----- || ----- | ----- | -----\nnull  || null  | false | null\nfalse || false | false | false\ntrue  || null  | false | true\n```",
+    "description": "Checks if **both** values are true.\n\nEvaluates parameter `x` before `y` and stops once the outcome is unambiguous. If any argument is `null`, the result will be `null` if the outcome is ambiguous.\n\n**Truth table:**\n\n```\nx \\ y || null  | false | true\n----- || ----- | ----- | -----\nnull  || null  | false | null\nfalse || false | false | false\ntrue  || null  | false | true\n```",
     "categories": [
         "logic"
     ],
@@ -90,4 +90,4 @@
             "result": true
         }
     }
-}
\ No newline at end of file
+}
diff --git a/arccos.json b/arccos.json
index 5ffbce35..4cd498a7 100644
--- a/arccos.json
+++ b/arccos.json
@@ -1,29 +1,32 @@
 {
     "id": "arccos",
     "summary": "Inverse cosine",
-    "description": "Computes the arc cosine of `x`. The arc cosine is the inverse function of the cosine so that *`arccos(cos(x)) = x`*.\n\nWorks on radians only.\nThe no-data value `null` is passed through and therefore gets propagated.",
+    "description": "Computes the arc cosine of `x`. The arc cosine is the inverse function of the cosine so that *`arccos(cos(x)) = x`*.\n\nWorks on radians only.\nThe no-data value `null` is passed through and therefore gets propagated. `NaN` is returned for values outside of the allowed range.",
     "categories": [
         "math > trigonometric"
     ],
     "parameters": [
         {
             "name": "x",
-            "description": "A number.",
+            "description": "A number in the range *[-1, 1]*.",
             "schema": {
                 "type": [
                     "number",
                     "null"
-                ]
+                ],
+                "minimum": -1,
+                "maximum": 1
             }
         }
     ],
     "returns": {
-        "description": "The computed angle in radians.",
+        "description": "The computed angle in radians in the range *[0, π]*.",
         "schema": {
             "type": [
                 "number",
                 "null"
-            ]
+            ],
+            "minimum": 0
         }
     },
     "examples": [
@@ -41,4 +44,4 @@
             "title": "Inverse cosine explained by Wolfram MathWorld"
         }
     ]
-}
\ No newline at end of file
+}
diff --git a/arcosh.json b/arcosh.json
index 6ed581fe..820b8cd4 100644
--- a/arcosh.json
+++ b/arcosh.json
@@ -1,29 +1,31 @@
 {
     "id": "arcosh",
     "summary": "Inverse hyperbolic cosine",
-    "description": "Computes the inverse hyperbolic cosine of `x`. It is the inverse function of the hyperbolic cosine so that *`arcosh(cosh(x)) = x`*.\n\nWorks on radians only.\nThe no-data value `null` is passed through and therefore gets propagated.",
+    "description": "Computes the inverse hyperbolic cosine of `x`. It is the inverse function of the hyperbolic cosine so that *`arcosh(cosh(x)) = x`*.\n\nThe no-data value `null` is passed through and therefore gets propagated. `NaN` is returned for values outside of the allowed range.",
     "categories": [
         "math > trigonometric"
     ],
     "parameters": [
         {
             "name": "x",
-            "description": "A number.",
+            "description": "A number in the range *[1, +∞)*.",
             "schema": {
                 "type": [
                     "number",
                     "null"
                 ]
-            }
+            },
+            "minimum": 1
         }
     ],
     "returns": {
-        "description": "The computed angle in radians.",
+        "description": "The computed hyperbolic angle in radians in the range *[0, +∞)*.",
         "schema": {
             "type": [
                 "number",
                 "null"
-            ]
+            ],
+            "minimum": 0
         }
     },
     "examples": [
@@ -41,4 +43,4 @@
             "title": "Inverse hyperbolic cosine explained by Wolfram MathWorld"
         }
     ]
-}
\ No newline at end of file
+}
diff --git a/arcsin.json b/arcsin.json
index e37eb2d3..2c772a00 100644
--- a/arcsin.json
+++ b/arcsin.json
@@ -1,24 +1,26 @@
 {
     "id": "arcsin",
     "summary": "Inverse sine",
-    "description": "Computes the arc sine of `x`. The arc sine is the inverse function of the sine so that *`arcsin(sin(x)) = x`*.\n\nWorks on radians only.\nThe no-data value `null` is passed through and therefore gets propagated.",
+    "description": "Computes the arc sine of `x`. The arc sine is the inverse function of the sine so that *`arcsin(sin(x)) = x`*.\n\nWorks on radians only.\nThe no-data value `null` is passed through and therefore gets propagated. `NaN` is returned for values < -1 and > 1.",
     "categories": [
         "math > trigonometric"
     ],
     "parameters": [
         {
             "name": "x",
-            "description": "A number.",
+            "description": "A number in the range *[-1, 1]*.",
             "schema": {
                 "type": [
                     "number",
                     "null"
-                ]
+                ],
+                "minimum": -1,
+                "maximum": 1
             }
         }
     ],
     "returns": {
-        "description": "The computed angle in radians.",
+        "description": "The computed angle in radians in the range *[-π/2, π/2]*.",
         "schema": {
             "type": [
                 "number",
@@ -41,4 +43,4 @@
             "title": "Inverse sine explained by Wolfram MathWorld"
         }
     ]
-}
\ No newline at end of file
+}
diff --git a/arctan.json b/arctan.json
index dc8d5a68..9461eba3 100644
--- a/arctan.json
+++ b/arctan.json
@@ -18,7 +18,7 @@
         }
     ],
     "returns": {
-        "description": "The computed angle in radians.",
+        "description": "The computed angle in radians in the range *(−π/2, π/2)*.",
         "schema": {
             "type": [
                 "number",
@@ -41,4 +41,4 @@
             "title": "Inverse tangent explained by Wolfram MathWorld"
         }
     ]
-}
\ No newline at end of file
+}
diff --git a/array_append.json b/array_append.json
index 80b48d12..f09145d2 100644
--- a/array_append.json
+++ b/array_append.json
@@ -25,15 +25,20 @@
         },
         {
             "name": "label",
-            "description": "If the given array is a labeled array, a new label for the new value should be given. If not given or `null`, the array index as string is used as the label. If in any case the label exists, a `LabelExists` exception is thrown.",
+            "description": "Provides a label for the new value. If not given or `null`, the natural next array index as number is used as the label. If in any case the label exists, a `LabelExists` exception is thrown.\n\nThis parameter only applies if the given array is a labeled array. If a non-null values is provided and the array is not labeled, an `ArrayNotLabeled` exception is thrown.",
             "optional": true,
             "default": null,
-            "schema": {
-                "type": [
-                    "string",
-                    "null"
-                ]
-            }
+            "schema": [
+                {
+                    "type": "number"
+                },
+                {
+                    "type": "string"
+                },
+                {
+                    "type": "null"
+                }
+            ]
         }
     ],
     "returns": {
@@ -48,6 +53,9 @@
     "exceptions": {
         "LabelExists": {
             "message": "An array element with the specified label already exists."
+        },
+        "ArrayNotLabeled": {
+            "message": "A label can't be provided as the given array is not labeled."
         }
     },
     "examples": [
diff --git a/arsinh.json b/arsinh.json
index 37384dcd..2b7942dd 100644
--- a/arsinh.json
+++ b/arsinh.json
@@ -1,7 +1,7 @@
 {
     "id": "arsinh",
     "summary": "Inverse hyperbolic sine",
-    "description": "Computes the inverse hyperbolic sine of `x`. It is the inverse function of the hyperbolic sine so that *`arsinh(sinh(x)) = x`*.\n\nWorks on radians only.\nThe no-data value `null` is passed through and therefore gets propagated.",
+    "description": "Computes the inverse hyperbolic sine of `x`. It is the inverse function of the hyperbolic sine so that *`arsinh(sinh(x)) = x`*.\n\nThe no-data value `null` is passed through and therefore gets propagated.",
     "categories": [
         "math > trigonometric"
     ],
@@ -18,7 +18,7 @@
         }
     ],
     "returns": {
-        "description": "The computed angle in radians.",
+        "description": "The computed hyperbolic angle in radians.",
         "schema": {
             "type": [
                 "number",
@@ -41,4 +41,4 @@
             "title": "Inverse hyperbolic sine explained by Wolfram MathWorld"
         }
     ]
-}
\ No newline at end of file
+}
diff --git a/artanh.json b/artanh.json
index 926b48ea..6308290d 100644
--- a/artanh.json
+++ b/artanh.json
@@ -1,24 +1,26 @@
 {
     "id": "artanh",
     "summary": "Inverse hyperbolic tangent",
-    "description": "Computes the inverse hyperbolic tangent of `x`. It is the inverse function of the hyperbolic tangent so that *`artanh(tanh(x)) = x`*.\n\nWorks on radians only.\nThe no-data value `null` is passed through and therefore gets propagated.",
+    "description": "Computes the inverse hyperbolic tangent of `x`. It is the inverse function of the hyperbolic tangent so that *`artanh(tanh(x)) = x`*.\n\nThe no-data value `null` is passed through and therefore gets propagated. `NaN` is returned for values outside of the allowed range. The computations follow [IEEE Standard 754](https://ieeexplore.ieee.org/document/8766229) whenever the processing environment supports it. Therefore, `x` = 1 results in +infinity and `x` = 0 results in -infinity. Otherwise, an exception is thrown.",
     "categories": [
         "math > trigonometric"
     ],
     "parameters": [
         {
             "name": "x",
-            "description": "A number.",
+            "description": "A number in the range *(-1, 1)*.",
             "schema": {
                 "type": [
                     "number",
                     "null"
-                ]
+                ],
+                "minimumExclusive": -1,
+                "maximumExclusive": 1
             }
         }
     ],
     "returns": {
-        "description": "The computed angle in radians.",
+        "description": "The computed hyperbolic angle in radians.",
         "schema": {
             "type": [
                 "number",
@@ -39,6 +41,11 @@
             "rel": "about",
             "href": "http://mathworld.wolfram.com/InverseHyperbolicTangent.html",
             "title": "Inverse hyperbolic tangent explained by Wolfram MathWorld"
+        },
+        {
+            "rel": "about",
+            "href": "https://ieeexplore.ieee.org/document/4610935",
+            "title": "IEEE Standard 754-2008 for Floating-Point Arithmetic"
         }
     ]
-}
\ No newline at end of file
+}
diff --git a/between.json b/between.json
index b2e59b92..12e37693 100644
--- a/between.json
+++ b/between.json
@@ -8,7 +8,7 @@
     "parameters": [
         {
             "name": "x",
-            "description": "The value to check.",
+            "description": "The value to check.\n\nThe no-data value `null` is passed through and therefore gets propagated.",
             "schema": {
                 "description": "Any data type is allowed."
             }
@@ -38,7 +38,7 @@
         }
     ],
     "returns": {
-        "description": "`true` if `x` is between the specified bounds, otherwise `false`.",
+        "description": "`true` if `x` is between the specified bounds, `null` if `x` is a no-data value, `false` otherwise.",
         "schema": {
             "type": [
                 "boolean",
diff --git a/clip.json b/clip.json
index adbf7eaa..de2a4d1a 100644
--- a/clip.json
+++ b/clip.json
@@ -1,7 +1,7 @@
 {
     "id": "clip",
     "summary": "Clip a value between a minimum and a maximum",
-    "description": "Clips a number between specified minimum and maximum values. A value larger than the maximum value is set to the maximum value, a value lower than the minimum value is set to the minimum value.\n\nThe no-data value `null` is passed through and therefore gets propagated.",
+    "description": "Clips a number between specified minimum and maximum values. A value larger than the maximum value is set to the maximum value, a value lower than the minimum value is set to the minimum value. If the maximum value is smaller than the minimum number, the process throws a `MinMaxSwapped` exception.\n\nThe no-data value `null` is passed through and therefore gets propagated.",
     "categories": [
         "math"
     ],
@@ -40,6 +40,11 @@
             ]
         }
     },
+    "exceptions": {
+        "MinMaxSwapped": {
+            "message": "The minimum value should be lower than or equal to the maximum value."
+        }
+    },
     "examples": [
         {
             "arguments": {
@@ -73,34 +78,5 @@
             },
             "returns": null
         }
-    ],
-    "process_graph": {
-        "min": {
-            "process_id": "min",
-            "arguments": {
-                "data": [
-                    {
-                        "from_parameter": "max"
-                    },
-                    {
-                        "from_parameter": "x"
-                    }
-                ]
-            }
-        },
-        "max": {
-            "process_id": "max",
-            "arguments": {
-                "data": [
-                    {
-                        "from_parameter": "min"
-                    },
-                    {
-                        "from_node": "min"
-                    }
-                ]
-            },
-            "result": true
-        }
-    }
-}
\ No newline at end of file
+    ]
+}
diff --git a/cos.json b/cos.json
index 6e6e4143..0d6229a8 100644
--- a/cos.json
+++ b/cos.json
@@ -18,12 +18,14 @@
         }
     ],
     "returns": {
-        "description": "The computed cosine of `x`.",
+        "description": "The computed cosine in the range *[-1, 1]*.",
         "schema": {
             "type": [
                 "number",
                 "null"
-            ]
+            ],
+            "minimum": -1,
+            "maximum": 1
         }
     },
     "examples": [
@@ -41,4 +43,4 @@
             "title": "Cosine explained by Wolfram MathWorld"
         }
     ]
-}
\ No newline at end of file
+}
diff --git a/cosh.json b/cosh.json
index 975958a4..8b56a222 100644
--- a/cosh.json
+++ b/cosh.json
@@ -1,14 +1,14 @@
 {
     "id": "cosh",
     "summary": "Hyperbolic cosine",
-    "description": "Computes the hyperbolic cosine of `x`.\n\nWorks on radians only.\nThe no-data value `null` is passed through and therefore gets propagated.",
+    "description": "Computes the hyperbolic cosine of `x`.\n\nThe no-data value `null` is passed through and therefore gets propagated.",
     "categories": [
         "math > trigonometric"
     ],
     "parameters": [
         {
             "name": "x",
-            "description": "An angle in radians.",
+            "description": "An hyperbolic angle in radians.",
             "schema": {
                 "type": [
                     "number",
@@ -18,12 +18,13 @@
         }
     ],
     "returns": {
-        "description": "The computed hyperbolic cosine of `x`.",
+        "description": "The computed hyperbolic cosine in the range *[1, +∞)*.",
         "schema": {
             "type": [
                 "number",
                 "null"
-            ]
+            ],
+            "minimum": 1
         }
     },
     "examples": [
@@ -41,4 +42,4 @@
             "title": "Hyperbolic cosine explained by Wolfram MathWorld"
         }
     ]
-}
\ No newline at end of file
+}
diff --git a/create_data_cube.json b/create_cube.json
similarity index 95%
rename from create_data_cube.json
rename to create_cube.json
index 55f0aede..0f8c7ca2 100644
--- a/create_data_cube.json
+++ b/create_cube.json
@@ -1,5 +1,5 @@
 {
-    "id": "create_data_cube",
+    "id": "create_cube",
     "summary": "Create an empty data cube",
     "description": "Creates a new data cube without dimensions. Dimensions can be added with ``add_dimension()``.",
     "categories": [
diff --git a/tests/.gitignore b/dev/.gitignore
similarity index 100%
rename from tests/.gitignore
rename to dev/.gitignore
diff --git a/tests/.words b/dev/.words
similarity index 95%
rename from tests/.words
rename to dev/.words
index a50285ba..a8f3d8a9 100644
--- a/tests/.words
+++ b/dev/.words
@@ -23,6 +23,7 @@ orthorectified
 radiometrically
 reflectances
 reproject
+reprojected
 Reprojects
 resample
 resampled
@@ -47,3 +48,4 @@ Hyndman
 date1
 date2
 favor
+Undeploy
diff --git a/tests/README.md b/dev/README.md
similarity index 100%
rename from tests/README.md
rename to dev/README.md
diff --git a/tests/docs.html b/dev/docs.html
similarity index 92%
rename from tests/docs.html
rename to dev/docs.html
index 23ef98e4..0a7d005e 100644
--- a/tests/docs.html
+++ b/dev/docs.html
@@ -5,7 +5,7 @@
     <meta http-equiv="x-ua-compatible" content="ie=edge">
     <title>openEO API Processes</title>
     <link rel="stylesheet" href="https://fonts.googleapis.com/css?family=Roboto:300,400,400i,700|Roboto+Mono">
-    <script src="https://cdn.jsdelivr.net/npm/vue@2.6"></script>
+    <script src="https://cdn.jsdelivr.net/npm/vue@2.7"></script>
     <script src="https://cdn.jsdelivr.net/npm/@openeo/processes-docgen@1/dist/DocGen.umd.min.js"></script>
     <link rel="stylesheet" href="https://cdn.jsdelivr.net/npm/@openeo/processes-docgen@1/dist/DocGen.css">
     <style>
@@ -113,9 +113,11 @@
         props: {
           document: 'processes.json',
           categorize: true,
-          apiVersion: '1.1.0',
-          title: 'openEO processes (draft)',
-          notice: '**Note:** This is the list of all processes specified by the openEO project. Back-ends implement a varying set of processes. Thus, the processes you can use at a specific back-end may derive from the specification, may include non-standardized processes and may not implement all processes listed here. Please check each back-end individually for the processes they support. The client libraries usually have a function called `listProcesses` or `list_processes` for that.'
+          apiVersion: '1.2.0',
+          title: 'openEO processes (2.0.0-rc.1)',
+          notice: '**Note:** This is the list of all processes specified by the openEO project. Back-ends implement a varying set of processes. Thus, the processes you can use at a specific back-end may derive from the specification, may include non-standardized processes and may not implement all processes listed here. Please check each back-end individually for the processes they support. The client libraries usually have a function called `listProcesses` or `list_processes` for that.',
+          showExperimentalByDefault: true,
+          showDeprecatedByDefault: false,
         }
       })
     });
diff --git a/tests/package.json b/dev/package.json
similarity index 96%
rename from tests/package.json
rename to dev/package.json
index 15f6d2e8..1da8693f 100644
--- a/tests/package.json
+++ b/dev/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@openeo/processes",
-  "version": "2.0.0",
+  "version": "2.0.0-rc.1",
   "author": "openEO Consortium",
   "contributors": [
     {
diff --git a/tests/testConfig.json b/dev/testConfig.json
similarity index 100%
rename from tests/testConfig.json
rename to dev/testConfig.json
diff --git a/divide.json b/divide.json
index 5dd664f1..0c6c254a 100644
--- a/divide.json
+++ b/divide.json
@@ -1,7 +1,7 @@
 {
     "id": "divide",
     "summary": "Division of two numbers",
-    "description": "Divides argument `x` by the argument `y` (*`x / y`*) and returns the computed result.\n\nNo-data values are taken into account so that `null` is returned if any element is such a value.\n\nThe computations follow [IEEE Standard 754](https://ieeexplore.ieee.org/document/8766229) whenever the processing environment supports it. Therefore, a division by zero results in ±infinity if the processing environment supports it. Otherwise, a `DivisionByZero` exception must the thrown.",
+    "description": "Divides argument `x` by the argument `y` (*`x / y`*) and returns the computed result.\n\nNo-data values are taken into account so that `null` is returned if any element is such a value.\n\nThe computations follow [IEEE Standard 754](https://ieeexplore.ieee.org/document/8766229) whenever the processing environment supports it. A division by zero results in:\n\n- +infinity for `x` > 0,\n- -infinity for `x` < 0,\n- `NaN` for `x` = 0,\n- or otherwise, throws a `DivisionByZero` exception if the other options are not supported by the processing environment.",
     "categories": [
         "math"
     ],
@@ -76,4 +76,4 @@
             "title": "IEEE Standard 754-2019 for Floating-Point Arithmetic"
         }
     ]
-}
\ No newline at end of file
+}
diff --git a/eq.json b/eq.json
index e7712399..0c62b42c 100644
--- a/eq.json
+++ b/eq.json
@@ -38,7 +38,8 @@
                 "type": [
                     "number",
                     "null"
-                ]
+                ],
+                "minimumExclusive": 0
             },
             "default": null,
             "optional": true
diff --git a/exp.json b/exp.json
index 5a5e3283..2d551390 100644
--- a/exp.json
+++ b/exp.json
@@ -18,12 +18,13 @@
         }
     ],
     "returns": {
-        "description": "The computed value for *e* raised to the power of `p`.",
+        "description": "The computed value for *e* raised to the power of `p`. Value is in the range of *(0, +∞)*",
         "schema": {
             "type": [
                 "number",
                 "null"
-            ]
+            ],
+            "minimumExclusive": 0
         }
     },
     "examples": [
@@ -65,4 +66,4 @@
             "result": true
         }
     }
-}
\ No newline at end of file
+}
diff --git a/filter_bbox.json b/filter_bbox.json
index 3e2a7485..21b6e8cd 100644
--- a/filter_bbox.json
+++ b/filter_bbox.json
@@ -1,7 +1,7 @@
 {
     "id": "filter_bbox",
     "summary": "Spatial filter using a bounding box",
-    "description": "Limits the data cube to the specified bounding box.\n\n* For raster data cubes, the filter retains a pixel in the data cube if the point at the pixel center intersects with the bounding box (as defined in the Simple Features standard by the OGC). Alternatively, ``filter_spatial()`` can be used to filter by geometry.\n* For vector data cubes, the filter retains the geometry in the data cube if the geometry is fully within the bounding box (as defined in the Simple Features standard by the OGC). All geometries that were empty or not contained fully within the bounding box will be removed from the data cube.\n\nAlternatively, ``filter_vector()`` can be used to filter by geometry.",
+    "description": "Limits the data cube to the specified bounding box.\n\n* For raster data cubes, the filter retains a pixel in the data cube if the point at the pixel center intersects with the bounding box (as defined in the Simple Features standard by the OGC). Alternatively, ``filter_spatial()`` can be used to filter by geometry.\n* For vector data cubes, the filter retains the geometry in the data cube if the geometry is fully within the bounding box (as defined in the Simple Features standard by the OGC). All geometries that were empty or not contained fully within the bounding box will be removed from the data cube.\n\nAlternatively, filter spatially with geometries using ``filter_spatial()`` (on a raster data cube) or ``filter_vector()`` (on a vector data cube).",
     "categories": [
         "cubes",
         "filter"
@@ -39,7 +39,7 @@
         },
         {
             "name": "extent",
-            "description": "A bounding box, which may include a vertical axis (see `base` and `height`).",
+            "description": "A bounding box, which may include a vertical axis (see `base` and `height`).\n\nIf the bounding box is not provided in the coordinate reference system (CRS) of the data cube, the bounding box is reprojected to the CRS of the spatial data cube dimensions.",
             "schema": {
                 "type": "object",
                 "subtype": "bounding-box",
@@ -83,7 +83,7 @@
                         "default": null
                     },
                     "crs": {
-                        "description": "Coordinate reference system of the extent, specified as as [EPSG code](http://www.epsg-registry.org/) or [WKT2 CRS string](http://docs.opengeospatial.org/is/18-010r7/18-010r7.html). Defaults to `4326` (EPSG code 4326) unless the client explicitly requests a different coordinate reference system.",
+                        "description": "Coordinate reference system of the extent, specified as [EPSG code](https://spatialreference.org/ref/epsg/) or [WKT2 CRS string](http://docs.opengeospatial.org/is/18-010r7/18-010r7.html). Defaults to `4326` (EPSG code 4326) unless the client explicitly requests a different coordinate reference system.",
                         "anyOf": [
                             {
                                 "title": "EPSG Code",
@@ -148,8 +148,8 @@
         },
         {
             "rel": "about",
-            "href": "http://www.epsg-registry.org",
-            "title": "Official EPSG code registry"
+            "href": "https://spatialreference.org/ref/epsg",
+            "title": "EPSG code registry"
         },
         {
             "rel": "about",
diff --git a/filter_spatial.json b/filter_spatial.json
index c0c116cd..ed4f7c3f 100644
--- a/filter_spatial.json
+++ b/filter_spatial.json
@@ -1,7 +1,7 @@
 {
     "id": "filter_spatial",
     "summary": "Spatial filter raster data cubes using geometries",
-    "description": "Limits the raster data cube over the spatial dimensions to the specified geometries.\n\n- For **polygons**, the filter retains a pixel in the data cube if the point at the pixel center intersects with at least one of the polygons (as defined in the Simple Features standard by the OGC).\n- For **points**, the process considers the closest pixel center.\n- For **lines** (line strings), the process considers all the pixels whose centers are closest to at least one point on the line.\n\nMore specifically, pixels outside of the bounding box of the given geometry will not be available after filtering. All pixels inside the bounding box that are not retained will be set to `null` (no data).\n\n Alternatively, use ``filter_bbox()`` to filter by bounding box.",
+    "description": "Limits the raster data cube over the spatial dimensions to the specified geometries.\n\n- For **polygons**, the filter retains a pixel in the data cube if the point at the pixel center intersects with at least one of the polygons (as defined in the Simple Features standard by the OGC).\n- For **points**, the process considers the closest pixel center.\n- For **lines** (line strings), the process considers all the pixels whose centers are closest to at least one point on the line.\n\nMore specifically, pixels outside of the bounding box of the given geometries will not be available after filtering. All pixels inside the bounding box that are not retained will be set to `null` (no data).\n\n Alternatively, use ``filter_bbox()`` to filter with a bounding box or ``filter_vector()`` to filter a vector data cube based on geometries. Use ``mask_polygon()`` to mask without changing the spatial extent of your data cube.",
     "categories": [
         "cubes",
         "filter"
@@ -26,7 +26,7 @@
         },
         {
             "name": "geometries",
-            "description": "One or more geometries used for filtering, given as GeoJSON or vector data cube. If multiple geometries are provided, the union of them is used. Empty geometries are ignored.\n\nLimits the data cube to the bounding box of the given geometries. No implicit masking gets applied. To mask the pixels of the data cube use ``mask_polygon()``.",
+            "description": "One or more geometries used for spatial filtering and masking, given as GeoJSON or vector data cube.",
             "schema": [
                 {
                     "title": "Vector Data Cube",
diff --git a/linear_scale_range.json b/linear_scale_range.json
index 172027c9..01f09857 100644
--- a/linear_scale_range.json
+++ b/linear_scale_range.json
@@ -1,7 +1,7 @@
 {
     "id": "linear_scale_range",
     "summary": "Linear transformation between two ranges",
-    "description": "Performs a linear transformation between the input and output range.\n\nThe given number in `x` is clipped to the bounds specified in `inputMin` and `inputMax` so that the underlying formula *`((x - inputMin) / (inputMax - inputMin)) * (outputMax - outputMin) + outputMin`* never returns any value lower than `outputMin` or greater than `outputMax`.\n\nPotential use case include\n\n* scaling values to the 8-bit range (0 - 255) often used for numeric representation of values in one of the channels of the [RGB colour model](https://en.wikipedia.org/wiki/RGB_color_model#Numeric_representations) or\n* calculating percentages (0 - 100).\n\nThe no-data value `null` is passed through and therefore gets propagated.",
+    "description": "Performs a linear transformation between the input and output range.\n\nThe given number in `x` is clipped to the bounds specified in `inputMin` and `inputMax` so that the underlying formula *`((x - inputMin) / (inputMax - inputMin)) * (outputMax - outputMin) + outputMin`* never returns a value outside of the range defined by `outputMin` and `outputMax`.\n\nPotential use case include\n\n* scaling values to the 8-bit range (0 - 255) often used for numeric representation of values in one of the channels of the [RGB colour model](https://en.wikipedia.org/wiki/RGB_color_model#Numeric_representations) or\n* calculating percentages (0 - 100).\n\nThe no-data value `null` is passed through and therefore gets propagated.",
     "categories": [
         "math"
     ],
@@ -166,4 +166,4 @@
             "result": true
         }
     }
-}
\ No newline at end of file
+}
diff --git a/ln.json b/ln.json
index e073c7a2..1663771b 100644
--- a/ln.json
+++ b/ln.json
@@ -1,19 +1,20 @@
 {
     "id": "ln",
     "summary": "Natural logarithm",
-    "description": "The natural logarithm is the logarithm to the base *e* of the number `x`, which equals to using the *log* process with the base set to *e*. The natural logarithm is the inverse function of taking *e* to the power x.\n\nThe no-data value `null` is passed through.\n\nThe computations follow [IEEE Standard 754](https://ieeexplore.ieee.org/document/8766229) whenever the processing environment supports it. Therefore, *`ln(0)`* results in ±infinity if the processing environment supports it or otherwise an exception is thrown.",
+    "description": "The natural logarithm is the logarithm to the base *e* of the number `x`, which equals to using the *log* process with the base set to *e*. The natural logarithm is the inverse function of taking *e* to the power x.\n\nThe no-data value `null` is passed through.\n\nThe computations follow [IEEE Standard 754](https://ieeexplore.ieee.org/document/8766229) whenever the processing environment supports it. Therefore, *`ln(0)`* results in -infinity if the processing environment supports it or otherwise an exception is thrown. `NaN` is returned for values outside of the allowed range.",
     "categories": [
         "math > exponential & logarithmic"
     ],
     "parameters": [
         {
             "name": "x",
-            "description": "A number to compute the natural logarithm for.",
+            "description": "A number to compute the natural logarithm for in the range *[0, +∞)*.",
             "schema": {
                 "type": [
                     "number",
                     "null"
-                ]
+                ],
+                "minimum": 0
             }
         }
     ],
@@ -64,4 +65,4 @@
             "result": true
         }
     }
-}
\ No newline at end of file
+}
diff --git a/load_collection.json b/load_collection.json
index b93c879c..fb78617d 100644
--- a/load_collection.json
+++ b/load_collection.json
@@ -64,7 +64,7 @@
                             "default": null
                         },
                         "crs": {
-                            "description": "Coordinate reference system of the extent, specified as as [EPSG code](http://www.epsg-registry.org/) or [WKT2 CRS string](http://docs.opengeospatial.org/is/18-010r7/18-010r7.html). Defaults to `4326` (EPSG code 4326) unless the client explicitly requests a different coordinate reference system.",
+                            "description": "Coordinate reference system of the extent, specified as [EPSG code](https://spatialreference.org/ref/epsg/) or [WKT2 CRS string](http://docs.opengeospatial.org/is/18-010r7/18-010r7.html). Defaults to `4326` (EPSG code 4326) unless the client explicitly requests a different coordinate reference system. If the bounding box is not provided in the coordinate reference system (CRS) of the data cube, the bounding box is reprojected to the CRS of the spatial data cube dimensions.",
                             "anyOf": [
                                 {
                                     "title": "EPSG Code",
@@ -295,8 +295,8 @@
         },
         {
             "rel": "about",
-            "href": "http://www.epsg-registry.org",
-            "title": "Official EPSG code registry"
+            "href": "https://spatialreference.org/ref/epsg",
+            "title": "EPSG code registry"
         },
         {
             "rel": "about",
diff --git a/log.json b/log.json
index 89500837..67a19ba2 100644
--- a/log.json
+++ b/log.json
@@ -1,19 +1,20 @@
 {
     "id": "log",
     "summary": "Logarithm to a base",
-    "description": "Logarithm to the base `base` of the number `x` is defined to be the inverse function of taking b to the power of x.\n\nThe no-data value `null` is passed through and therefore gets propagated if any of the arguments is `null`.\n\nThe computations follow [IEEE Standard 754](https://ieeexplore.ieee.org/document/8766229) whenever the processing environment supports it. Therefore, `log(0, 2)` results in ±infinity if the processing environment supports it or otherwise an exception is thrown.",
+    "description": "Logarithm to the base `base` of the number `x` is defined to be the inverse function of taking b to the power of x.\n\nThe no-data value `null` is passed through and therefore gets propagated if any of the arguments is `null`.\n\nThe computations follow [IEEE Standard 754](https://ieeexplore.ieee.org/document/8766229) whenever the processing environment supports it. Therefore, having `x` set to `0` with any base results in -infinity if the processing environment supports it or otherwise an exception is thrown. `NaN` is returned for values outside of the allowed range.",
     "categories": [
         "math > exponential & logarithmic"
     ],
     "parameters": [
         {
             "name": "x",
-            "description": "A number to compute the logarithm for.",
+            "description": "A number to compute the logarithm for in the range *[0, +∞)*.",
             "schema": {
                 "type": [
                     "number",
                     "null"
-                ]
+                ],
+                "minimum": 0
             }
         },
         {
@@ -78,4 +79,4 @@
             "title": "IEEE Standard 754-2019 for Floating-Point Arithmetic"
         }
     ]
-}
\ No newline at end of file
+}
diff --git a/meta/implementation.md b/meta/implementation.md
index 65a24430..f9dac17d 100644
--- a/meta/implementation.md
+++ b/meta/implementation.md
@@ -31,16 +31,17 @@ the evaluation should stop and provide the result directly.
 This is basically the same behavior that is also described in the processes `all` and `any`.
 
 For example, the condition `A > 0 or B > 0` should only execute `B > 0` if `A > 0` is false as
-otherwise the result is already unambiguous and will be `true` regardless of the rest of the 
+otherwise the result is already unambiguous and will be `true` regardless of the rest of the
 condition.
 
-Implementing this behavior does not have any negative side-effects so that 
+Implementing this behavior does not have any negative side-effects so that
 comparability and reproducibility of the results is still given.
 
 ## Enums for processing methods
 
 There are numerours processes that provide a predefined set of processing methods.
 For example:
+
 - `ard_surface_reflectance`: `atmospheric_correction_method` and `cloud_detection_method`
 - `athmospheric_correction`: `method`
 - `cloud_detection`: `method`
@@ -63,12 +64,13 @@ This applies similarly to other enums specied in parameter schemas, e.g. the
 
 The processes mentioned above have all at least one parameter for proprietary
 options that can be passed to the corresponsing `methods`:
+
 - `ard_surface_reflectance`: `atmospheric_correction_options` and `cloud_detection_options`
 - `athmospheric_correction`: `options`
 - `cloud_detection`: `options`
 
 By default, the parameters don't allow any value except an empty opject.
-Back-ends have to either remove the parameter or define schema to give user 
+Back-ends have to either remove the parameter or define schema to give user
 details about the supported parameters per supported method.
 
 For example, if you support the methods `iCor` and `FORCE` in `atmospheric_correction`,
@@ -76,40 +78,39 @@ you may define something like the following for the parameter:
 
 ```json
 {
-	"description": "Proprietary options for the atmospheric correction method.",
-	"name": "options",
-	"optional": true,
-	"default": {},
-	"schema": [
-		{
-			"title": "FORCE options",
-			"type": "object",
-			"properties": {
-				"force_option1": {
-					"type": "number",
-					"description": "Description for option 1",
-					"default": 0
-				},
-				"force_option2": {
-					"type": "boolean",
-					"description": "Description for option 1",
-					"default": true
-				}
-			}
-		},
-		{
-			"title": "iCor options",
-			"type": "object",
-			"properties": {
-				"icor_option1": {
-					"type": "string",
-					"description": "Description for option 1",
-					"default": "example"
-				}
-			}
-		}
-
-	]
+  "description": "Proprietary options for the atmospheric correction method.",
+  "name": "options",
+  "optional": true,
+  "default": {},
+  "schema": [
+    {
+      "title": "FORCE options",
+      "type": "object",
+      "properties": {
+        "force_option1": {
+          "type": "number",
+          "description": "Description for option 1",
+          "default": 0
+        },
+        "force_option2": {
+          "type": "boolean",
+          "description": "Description for option 1",
+          "default": true
+        }
+      }
+    },
+    {
+      "title": "iCor options",
+      "type": "object",
+      "properties": {
+        "icor_option1": {
+          "type": "string",
+          "description": "Description for option 1",
+          "default": "example"
+        }
+      }
+    }
+  ]
 }
 ```
 
@@ -149,24 +150,26 @@ Back-ends should not execute the processes for log levels that are not matching
 
 ### Data Types
 
-The process is only useful for users if a common behavior for data types passed into the `data` parameter has been agreed on across implementations. 
+The process is only useful for users if a common behavior for data types passed into the `data` parameter has been agreed on across implementations.
 
 The following chapters include some proposals for common data (sub) types, but it is incomplete and will be extended in the future.
 Also, for some data types a JSON encoding is missing, we'll add more details once agreed upon:
 <https://github.com/Open-EO/openeo-processes/issues/299>
 
 #### Scalars
+
 For the data types boolean, numbers, strings and null it is recommended to log them as given.
 
 #### Arrays
 
 It is recommended to summarize arrays as follows:
-```js
+
+```json5
 {
-	"data": [3,1,6,4,8], // Return a reasonable excerpt of the data, e.g. the first 5 or 10 elements
-	"length": 10, // Return the length of the array, this is important to determine whether the data above is complete or an excerpt
-	"min": 0, // optional: Return additional statstics if possible, ideally use the corresponsing openEO process names as keys
-	"max": 10
+  "data": [3,1,6,4,8], // Return a reasonable excerpt of the data, e.g. the first 5 or 10 elements
+  "length": 10, // Return the length of the array, this is important to determine whether the data above is complete or an excerpt
+  "min": 0, // optional: Return additional statstics if possible, ideally use the corresponsing openEO process names as keys
+  "max": 10
 }
 ```
 
@@ -176,40 +179,40 @@ It is recommended to return them summarized in a structure compliant to the [STA
 If reasonsable, it gives a valuable benefit for users to provide all dimension labels (e.g. individual timestamps for the temporal dimension) instead of values ranges.
 The top-level object and/or each dimension can be enhanced with additional statstics if possible, ideally use the corresponsing openEO process names as keys.
 
-```js
+```json5
 {
-	"cube:dimensions": {
-		"x": {
-			"type": "spatial",
-			"axis": "x",
-			"extent": [8.253, 12.975],
-			"reference_system": 4326
-		},
-		"y": {
-			"type": "spatial",
-			"axis": "y",
-			"extent": [51.877,55.988],
-			"reference_system": 4326
-		},
-		"t": {
-			"type": "temporal",
-			"values": [
-				"2015-06-21T12:56:55Z",
-				"2015-06-23T09:12:14Z",
-				"2015-06-25T23:44:44Z",
-				"2015-06-27T21:11:34Z",
-				"2015-06-30T17:33:12Z"
-			],
-			"step": null
-		},
-		"bands": {
-			"type": "bands",
-			"values": ["NDVI"]
-		}
-	},
-	// optional: Return additional data or statstics for the data cube if possible (see also the chapter for "Arrays" above).
-	"min": -1,
-	"max": 1
+  "cube:dimensions": {
+    "x": {
+      "type": "spatial",
+      "axis": "x",
+      "extent": [8.253, 12.975],
+      "reference_system": 4326
+    },
+    "y": {
+      "type": "spatial",
+      "axis": "y",
+      "extent": [51.877,55.988],
+      "reference_system": 4326
+    },
+    "t": {
+      "type": "temporal",
+      "values": [
+        "2015-06-21T12:56:55Z",
+        "2015-06-23T09:12:14Z",
+        "2015-06-25T23:44:44Z",
+        "2015-06-27T21:11:34Z",
+        "2015-06-30T17:33:12Z"
+      ],
+      "step": null
+    },
+    "bands": {
+      "type": "bands",
+      "values": ["NDVI"]
+    }
+  },
+  // optional: Return additional data or statstics for the data cube if possible (see also the chapter for "Arrays" above).
+  "min": -1,
+  "max": 1
 }
 ```
 
@@ -221,8 +224,96 @@ To improve interoperability openEO processes, version 1.2.0 added details about
 A survey has shown that most libraries implement type 7 and as such this was chosen to be the default.
 
 We have found some libraries that can be used for an implementation:
+
 - Java: [Apache Commons Math Percentile](http://commons.apache.org/proper/commons-math/javadocs/api-3.6/org/apache/commons/math3/stat/descriptive/rank/Percentile.html), choose the [estimation type `R_7`](http://commons.apache.org/proper/commons-math/javadocs/api-3.6/org/apache/commons/math3/stat/descriptive/rank/Percentile.EstimationType.html#R_7)
 - JavaScript: [d3](https://github.com/d3/d3-array/blob/v2.8.0/README.md#quantile), has only type 7 implemented.
 - Julia: [Statistics.quantile](https://docs.julialang.org/en/v1/stdlib/Statistics/#Statistics.quantile!), type 7 is the default.
-- Python: [numpy](https://numpy.org/doc/stable/reference/generated/numpy.quantile.html), [pandas](https://pandas.pydata.org/docs/reference/api/pandas.DataFrame.quantile.html), [xarray](http://xarray.pydata.org/en/stable/generated/xarray.DataArray.quantile.html) - type 7 (called 'linear' for the interpolation parameter) is the default for all of them. 
+- Python: [numpy](https://numpy.org/doc/stable/reference/generated/numpy.quantile.html), [pandas](https://pandas.pydata.org/docs/reference/api/pandas.DataFrame.quantile.html), [xarray](http://xarray.pydata.org/en/stable/generated/xarray.DataArray.quantile.html) - type 7 (called 'linear' for the interpolation parameter) is the default for all of them.
 - R: [quantile](https://stat.ethz.ch/R-manual/R-patched/library/stats/html/quantile.html) - type 7 is the default.
+
+## STAC support
+
+The subtype `stac` is an abstract type that refers to a STAC resource of any type (Catalog, Collection, or Item).
+It can refer to:
+- static STAC resources, e.g. hosted on cloud storage
+- dynamic STAC resources made available via a STAC API
+- a STAC JSON representation embedded as an argument into an openEO user-defined process
+
+### stac_modify
+
+The process `stac_modify` updates a given STAC resource based on
+[RFC 7386: JSON Merge Patch](https://www.rfc-editor.org/rfc/rfc7386.html).
+For static STAC resources, the content of the JSON files shall be updated according to RFC 7386.
+
+If the underlying STAC resource is part of an API, the following HTTP endpoints shall be used for the updates:
+- For STAC Items: `PATCH /collections/{collectionId}/items/{featureId}`
+  according to the [Transaction Extension](https://github.com/stac-api-extensions/transaction)
+- For STAC Collections: `PATCH /collections/{collectionId}`
+  according to the [Collection Transaction Extension](https://github.com/stac-api-extensions/collection-transaction)
+- For STAC Catalogs there is no API support for updates.
+
+## OGC API - Processes
+
+OGC API - Processes and OGC EO Application Packages (AP) can generally be utilized in openEO in three different ways:
+
+1. **openEO process**
+  
+   As a pre-defined process that exposes itself as a normal openEO process.
+   It is not exposed to the user that in the background an AP is invoked.
+2. **Pre-deployment through *OGC API - Processes - Part 2: Deploy, Replace, Undeploy***
+
+   In addition to the openEO API, a provider can offer access to an instance of *OGC API - Processes - Part 2: Deploy, Replace, Undeploy* (OGC DRU).
+   The OGC DRU instance is likely external to the openEO API tree due to the conflicting `GET /processes` endpoint.
+   As such the OGC DRU instance exposes itself in the `GET /` endpoint of the openEO API instance through a link.
+   The link must have the relation type `http://www.opengis.net/def/rel/ogc/1.0/processes`, which points to the `/processes` of the OGC API - Processes endpoint.
+   Users can deploy APs through the OGC DRU instance and use them through the process `run_ogcapi`.
+  
+   If the provider doesn't offer an OGC DRU instance itself, users could also deploy their AP with another provider.
+   In this case use the process `run_ogcapi_externally` instead.
+  
+   Example process node:
+  
+   ```json5
+   {
+     "process_id": "run_ogcapi",
+     "arguments": {
+       "data": ..., // Data, e.g. subtypes datacube or stac
+       "id": "my-ap", // Identifier of the application package in OGC API - Processes
+       "context": { // Parameters as defined in the CWL file
+         "cwl_param1": true,
+         "param2": 99
+       }
+     }
+   }
+   ```
+3. **CWL provided at runtime (UDF runtime)**
+  
+   Providers can also provide a UDF runtime for the language CWL (instead of e.g. Python or R).
+   The runtime is exposed through the endpoint `GET /udf_runtimes`.
+  
+   Example process node:
+  
+   ```json5
+   {
+     "process_id": "run_udf",
+     "arguments": {
+       "data": ..., // Data, e.g. subtypes datacube or stac
+       "udf": "...", // CWL as YAML string/JSON object, URL, or file on the API user workspace
+       "runtime": "cwl", // Assuming the UDF runtime is named "cwl"
+       "context": { // Parameters as defined in the CWL file
+         "cwl_param1": true,
+         "param2": 99
+       }
+     }
+   }
+   ```
+
+Generally, we recommend to use the following types and formats for the CWL inputs and outputs:
+
+- `type`: `File` or `File[]` depending on the capabilities of the CWL workflow
+- `format`: For STAC inputs and outputs either:
+  - `stac`: any of the following STAC entities
+  - `stac-catalog`: STAC Catalog
+  - `stac-collection`: STAC Collection
+  - `stac-item`: STAC Item
+  - `stac-item-collection`: STAC (API) ItemCollection
diff --git a/meta/subtype-schemas.json b/meta/subtype-schemas.json
index 347df234..e64f180b 100644
--- a/meta/subtype-schemas.json
+++ b/meta/subtype-schemas.json
@@ -55,7 +55,7 @@
                     "default": null
                 },
                 "crs": {
-                    "description": "Coordinate reference system of the extent, specified as as [EPSG code](http://www.epsg-registry.org/) or [WKT2 CRS string](http://docs.opengeospatial.org/is/18-010r7/18-010r7.html). Defaults to `4326` (EPSG code 4326) unless the client explicitly requests a different coordinate reference system.",
+                    "description": "Coordinate reference system of the extent, specified as [EPSG code](https://spatialreference.org/ref/epsg/) or [WKT2 CRS string](http://docs.opengeospatial.org/is/18-010r7/18-010r7.html). Defaults to `4326` (EPSG code 4326) unless the client explicitly requests a different coordinate reference system.",
                     "anyOf": [
                         {
                             "$ref": "#/definitions/epsg-code"
@@ -278,6 +278,23 @@
             "description": "A raster data cube, which is a data cube with two dimension of type spatial (x and y). This has been deprecated in favour of `datacube`.",
             "deprecated": true
         },
+        "stac": {
+            "type": "object",
+            "subtype": "stac",
+            "title": "STAC resource",
+            "description": "A STAC Catalog, Collection, or Item, as defined by the [STAC specification](https://stacspec.org) version 0.9.0 or later.",
+            "oneOf": [
+                {
+                    "$ref": "http://schemas.stacspec.org/v1.0.0/catalog-spec/json-schema/catalog.json"
+                },
+                {
+                    "$ref": "http://schemas.stacspec.org/v1.0.0/collection-spec/json-schema/collection.json"
+                },
+                {
+                    "$ref": "http://schemas.stacspec.org/v1.0.0/item-spec/json-schema/item.json"
+                }
+            ]
+        },
         "temporal-interval": {
             "type": "array",
             "subtype": "temporal-interval",
@@ -413,6 +430,13 @@
             "title": "WKT2 definition",
             "description": "Specifies details about cartographic projections as WKT2 string. Refers to the latest WKT2 version (currently [WKT2:2018](http://docs.opengeospatial.org/is/18-010r7/18-010r7.html) / ISO 19162:2018) unless otherwise stated by the process."
         },
+        "workspace-id": {
+            "type": "string",
+            "subtype": "workspace-id",
+            "title": "Workspace ID",
+            "description": "A workspace identifier from the list of available workspaces.",
+            "pattern": "^[\\w\\-\\.~]+$"
+        },
         "year": {
             "type": "integer",
             "subtype": "year",
diff --git a/mod.json b/mod.json
index ca709386..0c8a6ea9 100644
--- a/mod.json
+++ b/mod.json
@@ -1,7 +1,7 @@
 {
     "id": "mod",
     "summary": "Modulo",
-    "description": "Remainder after a division of `x` by `y` for both integers and floating-point numbers.\n\nThe result of a modulo operation has the sign of the divisor. The handling regarding the sign of the result [differs between programming languages](https://en.wikipedia.org/wiki/Modulo_operation#In_programming_languages) and needs careful consideration to avoid unexpected results.\n\nThe no-data value `null` is passed through and therefore gets propagated if any of the arguments is `null`. A modulo by zero results in ±infinity if the processing environment supports it. Otherwise, a `DivisionByZero` exception must the thrown.",
+    "description": "Remainder after a division of `x` by `y` for both integers and floating-point numbers.\n\nThe result of a modulo operation has the sign of the divisor. The handling regarding the sign of the result [differs between programming languages](https://en.wikipedia.org/wiki/Modulo_operation#In_programming_languages) and needs careful consideration to avoid unexpected results.\n\nThe no-data value `null` is passed through and therefore gets propagated if any of the arguments is `null`. If `y` is set to 0 this results in:\n\n- +infinity for `x` > 0,\n- -infinity for `x` < 0,\n- `NaN` for `x` = 0,\n- or otherwise, throws a `DivisionByZero` exception if the other options are not supported by the processing environment.",
     "categories": [
         "math"
     ],
@@ -92,4 +92,4 @@
             "title": "Modulo explained by Wikipedia"
         }
     ]
-}
\ No newline at end of file
+}
diff --git a/neq.json b/neq.json
index ff6bc9fd..0e22b347 100644
--- a/neq.json
+++ b/neq.json
@@ -38,7 +38,8 @@
                 "type": [
                     "number",
                     "null"
-                ]
+                ],
+                "minimumExclusive": 0
             },
             "default": null,
             "optional": true
diff --git a/or.json b/or.json
index 5964a341..4a83a63e 100644
--- a/or.json
+++ b/or.json
@@ -1,7 +1,7 @@
 {
     "id": "or",
     "summary": "Logical OR",
-    "description": "Checks if **at least one** of the values is true. Evaluates parameter `x` before `y` and stops once the outcome is unambiguous. If a component is `null`, the result will be `null` if the outcome is ambiguous.\n\n**Truth table:**\n\n```\na \\ b || null | false | true\n----- || ---- | ----- | ----\nnull  || null | null  | true\nfalse || null | false | true\ntrue  || true | true  | true\n```",
+    "description": "Checks if **at least one** of the values is true. Evaluates parameter `x` before `y` and stops once the outcome is unambiguous. If a component is `null`, the result will be `null` if the outcome is ambiguous.\n\n**Truth table:**\n\n```\nx \\ y || null | false | true\n----- || ---- | ----- | ----\nnull  || null | null  | true\nfalse || null | false | true\ntrue  || true | true  | true\n```",
     "categories": [
         "logic"
     ],
@@ -90,4 +90,4 @@
             "result": true
         }
     }
-}
\ No newline at end of file
+}
diff --git a/proposals/aggregate_spatial_window.json b/proposals/aggregate_spatial_window.json
index 747db151..9e5dce4a 100644
--- a/proposals/aggregate_spatial_window.json
+++ b/proposals/aggregate_spatial_window.json
@@ -75,7 +75,7 @@
         },
         {
             "name": "boundary",
-            "description": "Behavior to apply if the number of values for the axes `x` and `y` is not a multiple of the corresponding value in the `size` parameter. Options are:\n\n- `pad` (default): pad the data cube with the no-data value `null` to fit the required window size.\n\n- `trim`: trim the data cube to fit the required window size.\n\nSet the parameter `align` to specifies to which corner the data is aligned to.",
+            "description": "Behavior to apply if the number of values for the axes `x` and `y` is not a multiple of the corresponding value in the `size` parameter. Options are:\n\n- `pad` (default): pad the data cube with the no-data value `null` to fit the required window size.\n\n- `trim`: trim the data cube to fit the required window size.\n\nUse the parameter `align` to align the data to the desired corner.",
             "schema": {
                 "type": "string",
                 "enum": [
diff --git a/proposals/apply_polygon.json b/proposals/apply_polygon.json
index 735226a1..e50527f7 100644
--- a/proposals/apply_polygon.json
+++ b/proposals/apply_polygon.json
@@ -12,11 +12,20 @@
             "description": "A data cube.",
             "schema": {
                 "type": "object",
-                "subtype": "raster-cube"
+                "subtype": "datacube",
+                "dimensions": [
+                    {
+                        "type": "spatial",
+                        "axis": [
+                            "x",
+                            "y"
+                        ]
+                    }
+                ]
             }
         },
         {
-            "name": "polygons",
+            "name": "geometries",
             "description": "A vector data cube containing at least one polygon. The provided vector data can be one of the following:\n\n* A `Polygon` or `MultiPolygon` geometry,\n* a `Feature` with a `Polygon` or `MultiPolygon` geometry, or\n* a `FeatureCollection` containing at least one `Feature` with `Polygon` or `MultiPolygon` geometries.\n* Empty geometries are ignored.",
             "schema": {
                 "type": "object",
@@ -44,7 +53,16 @@
                         "description": "A sub data cube of the original data cube. The sub data cubes provided cover the smallest possible grid-aligned extent of the corresponding polygon and all pixels outside of the polygon are replaced with the value given in `mask_value`.",
                         "schema": {
                             "type": "object",
-                            "subtype": "raster-cube"
+                            "subtype": "datacube",
+                            "dimensions": [
+                                {
+                                    "type": "spatial",
+                                    "axis": [
+                                        "x",
+                                        "y"
+                                    ]
+                                }
+                            ]
                         }
                     },
                     {
@@ -63,7 +81,16 @@
                         "description": "A data cube.",
                         "schema": {
                             "type": "object",
-                            "subtype": "raster-cube"
+                            "subtype": "datacube",
+                            "dimensions": [
+                                {
+                                    "type": "spatial",
+                                    "axis": [
+                                        "x",
+                                        "y"
+                                    ]
+                                }
+                            ]
                         }
                     }
                 }
@@ -103,7 +130,16 @@
         "description": "A data cube with the newly computed values and the same dimensions. The dimension properties (name, type, labels, reference system and resolution) remain unchanged.",
         "schema": {
             "type": "object",
-            "subtype": "raster-cube"
+            "subtype": "datacube",
+            "dimensions": [
+                {
+                    "type": "spatial",
+                    "axis": [
+                        "x",
+                        "y"
+                    ]
+                }
+            ]
         }
     },
     "exceptions": {
diff --git a/proposals/ard_surface_reflectance.json b/proposals/ard_surface_reflectance.json
index 01328f10..c0fd7268 100644
--- a/proposals/ard_surface_reflectance.json
+++ b/proposals/ard_surface_reflectance.json
@@ -33,9 +33,7 @@
             "description": "The atmospheric correction method to use.",
             "name": "atmospheric_correction_method",
             "schema": {
-                "type": [
-                    "string"
-                ],
+                "type": "string",
                 "enum": [
                     "FORCE",
                     "iCOR"
@@ -46,9 +44,7 @@
             "description": "The cloud detection method to use.\n\nEach method supports detecting different atmospheric disturbances such as clouds, cloud shadows, aerosols, haze, ozone and/or water vapour in optical imagery.",
             "name": "cloud_detection_method",
             "schema": {
-                "type": [
-                    "string"
-                ],
+                "type": "string",
                 "enum": [
                     "Fmask",
                     "s2cloudless",
diff --git a/proposals/array_create_labeled.json b/proposals/array_create_labeled.json
index 8b5d2034..f83d6559 100644
--- a/proposals/array_create_labeled.json
+++ b/proposals/array_create_labeled.json
@@ -19,6 +19,7 @@
             "description": "An array of labels to be used.",
             "schema": {
                 "type": "array",
+                "uniqueItems": true,
                 "items": {
                     "type": [
                         "number",
@@ -43,4 +44,4 @@
             "message": "The number of values in the parameters `data` and `labels` don't match."
         }
     }
-}
\ No newline at end of file
+}
diff --git a/proposals/atmospheric_correction.json b/proposals/atmospheric_correction.json
index d366f1ed..c3f9ac30 100644
--- a/proposals/atmospheric_correction.json
+++ b/proposals/atmospheric_correction.json
@@ -33,9 +33,7 @@
             "name": "method",
             "schema": [
                 {
-                    "type": [
-                        "string"
-                    ],
+                    "type": "string",
                     "enum": [
                         "FORCE",
                         "iCOR"
diff --git a/proposals/cloud_detection.json b/proposals/cloud_detection.json
index d695720e..01df9cc6 100644
--- a/proposals/cloud_detection.json
+++ b/proposals/cloud_detection.json
@@ -33,9 +33,7 @@
             "name": "method",
             "schema": [
                 {
-                    "type": [
-                        "string"
-                    ],
+                    "type": "string",
                     "enum": [
                         "Fmask",
                         "s2cloudless",
diff --git a/proposals/combine_cubes.json b/proposals/combine_cubes.json
new file mode 100644
index 00000000..8d732aaf
--- /dev/null
+++ b/proposals/combine_cubes.json
@@ -0,0 +1,99 @@
+{
+    "id": "combine_cubes",
+    "summary": "Combine two data cubes with a process",
+    "description": "The process combines two 'compatible' data cubes with a process.\n\nThe data cubes have to be compatible, which means that they must share a common subset of equal dimensions. To conveniently get to such a subset of equal dimensions, the process tries to align the horizontal spatial dimensions (axes `x` and `y`) implicitly with ``resample_cube_spatial()`` if required. `cube1` is the target data cube for resampling and the default parameters of ``resample_cube_spatial()`` apply. The equality for geometries follows the definition in the Simple Features standard by the OGC.\n\nAll overlapping dimensions share the same properties, such as name, type, reference system, and resolution. Dimensions can have disjoint or overlapping labels. The combine process is applied to all labels from both cubes. If there are dimension labels that exist in only one cube, the other cube will be considered as no-data at this label. It is up to the combine process to handle these no-data values.\nIf one cube contains a dimension not present in the other cube, the combine process will be applied for each label in this dimension and the result will contain this dimension with the original labels.\n\nIt is not possible to combine a vector and a raster data cube. Combining vector data cubes with different base geometry types (points, lines/line strings, polygons) is not possible and throws the `IncompatibleGeometryTypes` exception. The base geometry types can be combined with their corresponding multi geometry types.\n\nAfter the combination, the dimensions with a natural/inherent label order (with a reference system this is each spatial and temporal dimensions) still have all dimension labels sorted. For other dimensions without inherent order, including bands, the dimension labels keep the order in which they are present in the original data cubes, and the dimension labels of `cube2` get appended to the dimension labels of `cube1`.\n\nUse this process when you want to combine two cubes with a process on each label, e.g. multiply two cubes with the same extents to calculate indices. Use ``merge_cubes()`` when you want to merge two cubes with a reduction operator on overlapping labels, e.g. creating a cube with bands from two different sources or merging cubes with different (possibly overlapping) extents.",
+    "categories": [
+        "cubes"
+    ],
+    "experimental": true,
+    "parameters": [
+        {
+            "name": "cube1",
+            "description": "The base data cube.",
+            "schema": {
+                "type": "object",
+                "subtype": "datacube"
+            }
+        },
+        {
+            "name": "cube2",
+            "description": "The other data cube to be combined with the base data cube.",
+            "schema": {
+                "type": "object",
+                "subtype": "datacube"
+            }
+        },
+        {
+            "name": "process",
+            "description": "A combine operator that takes two values. The combiner must return a value of the same data type as the input values are. The combine operator may be a single process such as ``multiply()`` or consist of multiple sub-processes.",
+            "schema": {
+                "type": "object",
+                "subtype": "process-graph",
+                "parameters": [
+                    {
+                        "name": "x",
+                        "description": "The overlapping value from the base data cube `cube1`.",
+                        "schema": {
+                            "description": "Any data type."
+                        }
+                    },
+                    {
+                        "name": "y",
+                        "description": "The overlapping value from the other data cube `cube2`.",
+                        "schema": {
+                            "description": "Any data type."
+                        }
+                    },
+                    {
+                        "name": "context",
+                        "description": "Additional data passed by the user.",
+                        "schema": {
+                            "description": "Any data type."
+                        },
+                        "optional": true,
+                        "default": null
+                    }
+                ],
+                "returns": {
+                    "description": "The value to be set in the combined data cube.",
+                    "schema": {
+                        "description": "Any data type."
+                    }
+                }
+            }
+        },
+        {
+            "name": "context",
+            "description": "Additional data to be passed to the overlap resolver.",
+            "schema": {
+                "description": "Any data type."
+            },
+            "optional": true,
+            "default": null
+        }
+    ],
+    "returns": {
+        "description": "The combined data cube. See the process description for details regarding the dimensions and dimension properties (name, type, labels, reference system and resolution).",
+        "schema": {
+            "type": "object",
+            "subtype": "datacube"
+        }
+    },
+    "exceptions": {
+        "IncompatibleGeometryTypes": {
+            "message": "The geometry types are not compatible and can't be combined."
+        }
+    },
+    "links": [
+        {
+            "rel": "about",
+            "href": "https://en.wikipedia.org/wiki/Reduction_Operator",
+            "title": "Background information on reduction operators (binary reducers) by Wikipedia"
+        },
+        {
+            "href": "http://www.opengeospatial.org/standards/sfa",
+            "rel": "about",
+            "title": "Simple Features standard by the OGC"
+        }
+    ]
+}
diff --git a/proposals/cummax.json b/proposals/cummax.json
index 69580459..8cacc00e 100644
--- a/proposals/cummax.json
+++ b/proposals/cummax.json
@@ -1,7 +1,7 @@
 {
     "id": "cummax",
     "summary": "Cumulative maxima",
-    "description": "Finds cumulative maxima of an array of numbers. Every computed element is equal to the bigger one between the current element and the previously computed element. The returned array and the input array have always the same length.\n\nBy default, no-data values are skipped, but stay in the result. Setting the `ignore_nodata` flag to `true` makes that once a no-data value (`null`) is reached all following elements are set to `null` in the result.",
+    "description": "Finds cumulative maxima of an array of numbers. Every computed element is equal to the bigger one between the current element and the previously computed element. The returned array and the input array have always the same length.\n\nBy default, no-data values are skipped, but stay in the result. Setting the `ignore_nodata` flag to `false` makes that once a no-data value (`null`) is reached all following elements are set to `null` in the result.",
     "categories": [
         "math > cumulative"
     ],
@@ -22,7 +22,7 @@
         },
         {
             "name": "ignore_nodata",
-            "description": "Indicates whether no-data values are ignored or not and ignores them by default. Setting this flag to `false` considers no-data values so that `null` is set for all the following elements.",
+            "description": "Indicates whether no-data values are ignored or not. Ignores them by default. Setting this flag to `false` considers no-data values so that `null` is set for all the following elements.",
             "schema": {
                 "type": "boolean"
             },
diff --git a/proposals/cummin.json b/proposals/cummin.json
index d84612e3..a76e9c99 100644
--- a/proposals/cummin.json
+++ b/proposals/cummin.json
@@ -1,7 +1,7 @@
 {
     "id": "cummin",
     "summary": "Cumulative minima",
-    "description": "Finds cumulative minima of an array of numbers. Every computed element is equal to the smaller one between the current element and the previously computed element. The returned array and the input array have always the same length.\n\nBy default, no-data values are skipped, but stay in the result. Setting the `ignore_nodata` flag to `true` makes that once a no-data value (`null`) is reached all following elements are set to `null` in the result.",
+    "description": "Finds cumulative minima of an array of numbers. Every computed element is equal to the smaller one between the current element and the previously computed element. The returned array and the input array have always the same length.\n\nBy default, no-data values are skipped, but stay in the result. Setting the `ignore_nodata` flag to `false` makes that once a no-data value (`null`) is reached all following elements are set to `null` in the result.",
     "categories": [
         "math > cumulative"
     ],
@@ -22,7 +22,7 @@
         },
         {
             "name": "ignore_nodata",
-            "description": "Indicates whether no-data values are ignored or not and ignores them by default. Setting this flag to `false` considers no-data values so that `null` is set for all the following elements.",
+            "description": "Indicates whether no-data values are ignored or not. Ignores them by default. Setting this flag to `false` considers no-data values so that `null` is set for all the following elements.",
             "schema": {
                 "type": "boolean"
             },
diff --git a/proposals/cumproduct.json b/proposals/cumproduct.json
index f5e6ae1b..1c4a1f47 100644
--- a/proposals/cumproduct.json
+++ b/proposals/cumproduct.json
@@ -1,7 +1,7 @@
 {
     "id": "cumproduct",
     "summary": "Cumulative products",
-    "description": "Computes cumulative products of an array of numbers. Every computed element is equal to the product of the current and all previous values. The returned array and the input array have always the same length.\n\nBy default, no-data values are skipped, but stay in the result. Setting the `ignore_nodata` flag to `true` makes that once a no-data value (`null`) is reached all following elements are set to `null` in the result.",
+    "description": "Computes cumulative products of an array of numbers. Every computed element is equal to the product of the current and all previous values. The returned array and the input array have always the same length.\n\nBy default, no-data values are skipped, but stay in the result. Setting the `ignore_nodata` flag to `false` makes that once a no-data value (`null`) is reached all following elements are set to `null` in the result.",
     "categories": [
         "math > cumulative"
     ],
@@ -22,7 +22,7 @@
         },
         {
             "name": "ignore_nodata",
-            "description": "Indicates whether no-data values are ignored or not and ignores them by default. Setting this flag to `false` considers no-data values so that `null` is set for all the following elements.",
+            "description": "Indicates whether no-data values are ignored or not. Ignores them by default. Setting this flag to `false` considers no-data values so that `null` is set for all the following elements.",
             "schema": {
                 "type": "boolean"
             },
diff --git a/proposals/cumsum.json b/proposals/cumsum.json
index 717999e5..fc08a391 100644
--- a/proposals/cumsum.json
+++ b/proposals/cumsum.json
@@ -1,7 +1,7 @@
 {
     "id": "cumsum",
     "summary": "Cumulative sums",
-    "description": "Computes cumulative sums of an array of numbers. Every computed element is equal to the sum of current and all previous values. The returned array and the input array have always the same length.\n\nBy default, no-data values are skipped, but stay in the result. Setting the `ignore_nodata` flag to `true` makes that once a no-data value (`null`) is reached all following elements are set to `null` in the result.",
+    "description": "Computes cumulative sums of an array of numbers. Every computed element is equal to the sum of current and all previous values. The returned array and the input array have always the same length.\n\nBy default, no-data values are skipped, but stay in the result. Setting the `ignore_nodata` flag to `false` makes that once a no-data value (`null`) is reached all following elements are set to `null` in the result.",
     "categories": [
         "math > cumulative"
     ],
@@ -22,7 +22,7 @@
         },
         {
             "name": "ignore_nodata",
-            "description": "Indicates whether no-data values are ignored or not and ignores them by default. Setting this flag to `false` considers no-data values so that `null` is set for all the following elements.",
+            "description": "Indicates whether no-data values are ignored or not. Ignores them by default. Setting this flag to `false` considers no-data values so that `null` is set for all the following elements.",
             "schema": {
                 "type": "boolean"
             },
diff --git a/proposals/export_collection.json b/proposals/export_collection.json
new file mode 100644
index 00000000..e5014811
--- /dev/null
+++ b/proposals/export_collection.json
@@ -0,0 +1,45 @@
+{
+    "id": "export_collection",
+    "summary": "Export data to an openEO collection",
+    "description": "Exports the given processing results made available through a STAC resource (e.g., a STAC Collection or Item) to the given openEO collection. The STAC resource itself is exported with all STAC resources and assets underneath.",
+    "categories": [
+        "export",
+        "stac"
+    ],
+    "experimental": true,
+    "parameters": [
+        {
+            "name": "data",
+            "description": "The data to export to the openEO collection.",
+            "schema": {
+                "type": "object",
+                "subtype": "stac"
+            }
+        },
+        {
+            "name": "collection",
+            "description": "The identifier of the collection to export to. If the collection **exists**, the data will be added to the collection. If the collection **does not exist** yet, it will be created based on the given STAC metadata.",
+            "schema": [
+                {
+                    "title": "New Collection",
+                    "type": "string",
+                    "pattern": "^[A-Za-z0-9_\\-\\.~/]+$"
+                },
+                {
+                    "title": "Existing Collection",
+                    "type": "string",
+                    "subtype": "collection-id",
+                    "pattern": "^[A-Za-z0-9_\\-\\.~/]+$"
+                }
+            ]
+        }
+    ],
+    "returns": {
+        "description": "Returns the collection identifier.",
+        "schema": {
+            "type": "string",
+            "subtype": "collection-id",
+            "pattern": "^[A-Za-z0-9_\\-\\.~/]+$"
+        }
+    }
+}
diff --git a/proposals/export_workspace.json b/proposals/export_workspace.json
new file mode 100644
index 00000000..c469254f
--- /dev/null
+++ b/proposals/export_workspace.json
@@ -0,0 +1,48 @@
+{
+    "id": "export_workspace",
+    "summary": "Export data to a cloud user workspace",
+    "description": "Exports the given processing results made available through a STAC resource (e.g., a STAC Collection) to the given user workspace. The STAC resource itself is exported with all STAC resources and assets underneath.",
+    "categories": [
+        "export",
+        "stac"
+    ],
+    "experimental": true,
+    "parameters": [
+        {
+            "name": "data",
+            "description": "The data to export to the user workspace as a STAC resource.",
+            "schema": {
+                "type": "object",
+                "subtype": "stac"
+            }
+        },
+        {
+            "name": "workspace",
+            "description": "The identifier of the workspace to export to.",
+            "schema": {
+                "type": "string",
+                "pattern": "^[\\w\\-\\.~]+$",
+                "subtype": "workspace-id"
+            }
+        },
+        {
+            "name": "merge",
+            "description": "Provides a cloud-specific path identifier to a STAC resource to merge the given STAC resource into. If not provided, the STAC resource is kept separate from any other STAC resources in the workspace.",
+            "schema": {
+                "type": [
+                    "string",
+                    "null"
+                ]
+            },
+            "optional": true,
+            "default": null
+        }
+    ],
+    "returns": {
+        "description": "Returns the potentially updated STAC resource.",
+        "schema": {
+            "type": "object",
+            "subtype": "stac"
+        }
+    }
+}
diff --git a/proposals/filter_vector.json b/proposals/filter_vector.json
index 349f8d0f..1bb33c86 100644
--- a/proposals/filter_vector.json
+++ b/proposals/filter_vector.json
@@ -1,7 +1,7 @@
 {
     "id": "filter_vector",
     "summary": "Spatial vector filter using geometries",
-    "description": "Limits the vector data cube to the specified geometries. The process works on geometries as defined in the Simple Features standard by the OGC. All geometries that were empty or become empty will be removed from the data cube. Alternatively, use ``filter_bbox()`` to filter by bounding box.",
+    "description": "Limits the vector data cube to the specified geometries. The process works on geometries as defined in the Simple Features standard by the OGC. All geometries that were empty or become empty will be removed from the data cube. Alternatively, use ``filter_bbox()`` to filter with a bounding box or ``filter_spatial()`` to filter a raster data cube based on geometries.",
     "categories": [
         "cubes",
         "filter",
diff --git a/proposals/flatten_dimensions.json b/proposals/flatten_dimensions.json
index da3647ab..1c02bf39 100644
--- a/proposals/flatten_dimensions.json
+++ b/proposals/flatten_dimensions.json
@@ -20,6 +20,7 @@
             "description": "The names of the dimension to combine. The order of the array defines the order in which the dimension labels and values are combined (see the example in the process description). Fails with a `DimensionNotAvailable` exception if at least one of the specified dimensions does not exist.",
             "schema": {
                 "type": "array",
+                "uniqueItems": true,
                 "items": {
                     "type": "string"
                 }
diff --git a/proposals/load_stac.json b/proposals/load_stac.json
index c71d3a80..f58d1126 100644
--- a/proposals/load_stac.json
+++ b/proposals/load_stac.json
@@ -67,7 +67,7 @@
                             "default": null
                         },
                         "crs": {
-                            "description": "Coordinate reference system of the extent, specified as as [EPSG code](http://www.epsg-registry.org/) or [WKT2 CRS string](http://docs.opengeospatial.org/is/18-010r7/18-010r7.html). Defaults to `4326` (EPSG code 4326) unless the client explicitly requests a different coordinate reference system.",
+                            "description": "Coordinate reference system of the extent, specified as [EPSG code](https://spatialreference.org/ref/epsg/) or [WKT2 CRS string](http://docs.opengeospatial.org/is/18-010r7/18-010r7.html). Defaults to `4326` (EPSG code 4326) unless the client explicitly requests a different coordinate reference system. If the bounding box is not provided in the coordinate reference system (CRS) of the data cube, the bounding box is reprojected to the CRS of the spatial data cube dimensions.",
                             "anyOf": [
                                 {
                                     "title": "EPSG Code",
@@ -307,8 +307,8 @@
         },
         {
             "rel": "about",
-            "href": "http://www.epsg-registry.org",
-            "title": "Official EPSG code registry"
+            "href": "https://spatialreference.org/ref/epsg",
+            "title": "EPSG code registry"
         },
         {
             "rel": "about",
diff --git a/proposals/predict_curve.json b/proposals/predict_curve.json
index 479b7fec..ef3e9596 100644
--- a/proposals/predict_curve.json
+++ b/proposals/predict_curve.json
@@ -68,6 +68,7 @@
                 },
                 {
                     "type": "array",
+                    "uniqueItems": true,
                     "items": {
                         "anyOf": [
                             {
diff --git a/proposals/run_ogcapi.json b/proposals/run_ogcapi.json
new file mode 100644
index 00000000..9b54eb65
--- /dev/null
+++ b/proposals/run_ogcapi.json
@@ -0,0 +1,47 @@
+{
+    "id": "run_ogcapi",
+    "summary": "Run a OGC API process",
+    "description": "Runs an OGC API - Processes process that the service provider offers through an instance of OGC API - Processes - Part 2 (Deploy, Replace, Undeploy).",
+    "categories": [
+        "cubes",
+        "import",
+        "udf"
+    ],
+    "experimental": true,
+    "parameters": [
+        {
+            "name": "data",
+            "description": "The data to be passed to the OGC API process.\n\nThe data must be given in a way that the external process can understand it.",
+            "schema": {
+                "description": "A value of any data type."
+            }
+        },
+        {
+            "name": "id",
+            "description": "The identifier of the OGC API process.",
+            "schema": {
+                "type": "string"
+            }
+        },
+        {
+            "name": "context",
+            "description": "Additional parameters as defined by the OGC API process.",
+            "schema": {
+                "type": "object"
+            },
+            "default": {},
+            "optional": true
+        }
+    ],
+    "exceptions": {
+        "InvalidOgcApiProcess": {
+            "message": "The specified OGC API process identifier does not exist."
+        }
+    },
+    "returns": {
+        "description": "The data processed by the OGC API process. The returned value can be of any data type and is exactly what the OGC API process returns.",
+        "schema": {
+            "description": "Any data type."
+        }
+    }
+}
diff --git a/proposals/run_ogcapi_externally.json b/proposals/run_ogcapi_externally.json
new file mode 100644
index 00000000..76b40fcc
--- /dev/null
+++ b/proposals/run_ogcapi_externally.json
@@ -0,0 +1,57 @@
+{
+    "id": "run_ogcapi_externally",
+    "summary": "Run an externally hosted OGC API process",
+    "description": "Runs an OGC API - Processes process that is either externally hosted by a service provider or running on a local machine of the user.",
+    "categories": [
+        "cubes",
+        "import",
+        "udf"
+    ],
+    "experimental": true,
+    "parameters": [
+        {
+            "name": "data",
+            "description": "The data to be passed to the external process.\n\nThe data must be given in a way that the external process can understand it.",
+            "schema": {
+                "description": "A value of any data type."
+            }
+        },
+        {
+            "name": "url",
+            "description": "Absolute URL to the OGC API - Processes landing page.",
+            "schema": {
+                "type": "string",
+                "format": "uri",
+                "subtype": "uri",
+                "pattern": "^https?://"
+            }
+        },
+        {
+            "name": "id",
+            "description": "The identifier of the OGC API process.",
+            "schema": {
+                "type": "string"
+            }
+        },
+        {
+            "name": "context",
+            "description": "Additional parameters as defined by the OGC API process.",
+            "schema": {
+                "type": "object"
+            },
+            "default": {},
+            "optional": true
+        }
+    ],
+    "exceptions": {
+        "InvalidOgcApiProcess": {
+            "message": "The specified OGC API process does not exist."
+        }
+    },
+    "returns": {
+        "description": "The data processed by the OGC API process. The returned value can be of any data type and is exactly what the OGC API process returns.",
+        "schema": {
+            "description": "Any data type."
+        }
+    }
+}
diff --git a/proposals/stac_modify.json b/proposals/stac_modify.json
new file mode 100644
index 00000000..8377c8a8
--- /dev/null
+++ b/proposals/stac_modify.json
@@ -0,0 +1,41 @@
+{
+    "id": "stac_modify",
+    "summary": "Updates an existing STAC resource",
+    "description": "Modifies the given STAC resource (e.g., a STAC Collection or Item) based on the given changeset.",
+    "categories": [
+        "stac"
+    ],
+    "experimental": true,
+    "parameters": [
+        {
+            "name": "data",
+            "description": "The existing STAC resource.",
+            "schema": {
+                "type": "object",
+                "subtype": "stac"
+            }
+        },
+        {
+            "name": "changes",
+            "description": "A potentially incomplete STAC resource that should be merged with the existing STAC resource. It follows the [RFC 7386: JSON Merge Patch](https://www.rfc-editor.org/rfc/rfc7386.html) specification.",
+            "schema": {
+                "type": "object"
+            }
+        }
+    ],
+    "returns": {
+        "description": "Returns the modified STAC resource.",
+        "schema": {
+            "type": "object",
+            "subtype": "stac"
+        }
+    },
+    "links": [
+        {
+            "href": "https://www.rfc-editor.org/rfc/rfc7386.html",
+            "title": "RFC 7386: JSON Merge Patch",
+            "type": "text/html",
+            "rel": "about"
+        }
+    ]
+}
diff --git a/proposals/unflatten_dimension.json b/proposals/unflatten_dimension.json
index 990e7469..a5a4bb6d 100644
--- a/proposals/unflatten_dimension.json
+++ b/proposals/unflatten_dimension.json
@@ -27,6 +27,7 @@
             "description": "The names of the new target dimensions. New dimensions will be created with the given names and type `other` (see ``add_dimension()``). Fails with a `TargetDimensionExists` exception if any of the dimensions exists.\n\nThe order of the array defines the order in which the dimensions and dimension labels are added to the data cube (see the example in the process description).",
             "schema": {
                 "type": "array",
+                "uniqueItems": true,
                 "minItems": 2,
                 "items": {
                     "type": "string"
diff --git a/proposals/vector_reproject.json b/proposals/vector_reproject.json
index d5a099c9..8a0e37b5 100644
--- a/proposals/vector_reproject.json
+++ b/proposals/vector_reproject.json
@@ -24,7 +24,7 @@
         },
         {
             "name": "projection",
-            "description": "Coordinate reference system to reproject to. Specified as an [EPSG code](http://www.epsg-registry.org/) or [WKT2 CRS string](http://docs.opengeospatial.org/is/18-010r7/18-010r7.html).",
+            "description": "Coordinate reference system to reproject to. Specified as [EPSG code](https://spatialreference.org/ref/epsg/) or [WKT2 CRS string](http://docs.opengeospatial.org/is/18-010r7/18-010r7.html).",
             "schema": [
                 {
                     "title": "EPSG Code",
@@ -85,8 +85,8 @@
         },
         {
             "rel": "about",
-            "href": "http://www.epsg-registry.org",
-            "title": "Official EPSG code registry"
+            "href": "https://spatialreference.org/ref/epsg",
+            "title": "EPSG code registry"
         },
         {
             "rel": "about",
diff --git a/rename_labels.json b/rename_labels.json
index 2042737d..de4f07da 100644
--- a/rename_labels.json
+++ b/rename_labels.json
@@ -26,6 +26,7 @@
             "description": "The new names for the labels.\n\nIf a target dimension label already exists in the data cube, a `LabelExists` exception is thrown.",
             "schema": {
                 "type": "array",
+                "uniqueItems": true,
                 "items": {
                     "type": [
                         "number",
@@ -39,6 +40,7 @@
             "description": "The original names of the labels to be renamed to corresponding array elements in the parameter `target`. It is allowed to only specify a subset of labels to rename, as long as the `target` and `source` parameter have the same length. The order of the labels doesn't need to match the order of the dimension labels in the data cube. By default, the array is empty so that the dimension labels in the data cube are expected to be enumerated.\n\nIf the dimension labels are not enumerated and the given array is empty, the `LabelsNotEnumerated` exception is thrown. If one of the source dimension labels doesn't exist, the `LabelNotAvailable` exception is thrown.",
             "schema": {
                 "type": "array",
+                "uniqueItems": true,
                 "items": {
                     "type": [
                         "number",
diff --git a/resample_spatial.json b/resample_spatial.json
index fb34f194..705cba22 100644
--- a/resample_spatial.json
+++ b/resample_spatial.json
@@ -49,7 +49,7 @@
         },
         {
             "name": "projection",
-            "description": "Warps the data cube to the target projection, specified as as [EPSG code](http://www.epsg-registry.org/) or [WKT2 CRS string](http://docs.opengeospatial.org/is/18-010r7/18-010r7.html). By default (`null`), the projection is not changed.",
+            "description": "Warps the data cube to the target projection, specified as [EPSG code](https://spatialreference.org/ref/epsg/) or [WKT2 CRS string](http://docs.opengeospatial.org/is/18-010r7/18-010r7.html). By default (`null`), the projection is not changed.",
             "schema": [
                 {
                     "title": "EPSG Code",
@@ -143,8 +143,8 @@
         },
         {
             "rel": "about",
-            "href": "http://www.epsg-registry.org",
-            "title": "Official EPSG code registry"
+            "href": "https://spatialreference.org/ref/epsg",
+            "title": "EPSG code registry"
         },
         {
             "rel": "about",
diff --git a/save_result.json b/save_result.json
index 7b952ead..418bafc7 100644
--- a/save_result.json
+++ b/save_result.json
@@ -4,7 +4,8 @@
     "description": "Makes the processed data available in the given file format to the corresponding medium that is relevant for the context this processes is applied in:\n\n* For **batch jobs** the data is stored on the back-end. STAC-compatible metadata is usually made available with the processed data.\n* For **synchronous processing** the data is sent to the client as a direct response to the request.\n* **Secondary web services** are provided with the processed data so that it can make use of it (e.g., visualize it). Web service may require the data in a certain format. Please refer to the documentation of the individual service types for details.",
     "categories": [
         "cubes",
-        "export"
+        "export",
+        "stac"
     ],
     "parameters": [
         {
@@ -35,10 +36,10 @@
         }
     ],
     "returns": {
-        "description": "Always returns `true` as in case of an error an exception is thrown which aborts the execution of the process.",
+        "description": "Returns the STAC resource that was created in the process of saving the result.",
         "schema": {
-            "type": "boolean",
-            "const": true
+            "type": "object",
+            "subtype": "stac"
         }
     },
     "exceptions": {
diff --git a/sgn.json b/sgn.json
index f59afdc4..ecdbd9d1 100644
--- a/sgn.json
+++ b/sgn.json
@@ -23,6 +23,12 @@
             "type": [
                 "number",
                 "null"
+            ],
+            "enum": [
+                -1,
+                0,
+                1,
+                null
             ]
         }
     },
@@ -104,4 +110,4 @@
             "result": true
         }
     }
-}
\ No newline at end of file
+}
diff --git a/sin.json b/sin.json
index 06c45cc4..15285979 100644
--- a/sin.json
+++ b/sin.json
@@ -18,12 +18,14 @@
         }
     ],
     "returns": {
-        "description": "The computed sine of `x`.",
+        "description": "The computed sine in the range *[-1, 1]*.",
         "schema": {
             "type": [
                 "number",
                 "null"
-            ]
+            ],
+            "minimum": -1,
+            "maximum": 1
         }
     },
     "examples": [
@@ -41,4 +43,4 @@
             "title": "Sine explained by Wolfram MathWorld"
         }
     ]
-}
\ No newline at end of file
+}
diff --git a/sinh.json b/sinh.json
index c505b3a3..6eced19c 100644
--- a/sinh.json
+++ b/sinh.json
@@ -1,14 +1,14 @@
 {
     "id": "sinh",
     "summary": "Hyperbolic sine",
-    "description": "Computes the hyperbolic sine of `x`.\n\nWorks on radians only.\nThe no-data value `null` is passed through and therefore gets propagated.",
+    "description": "Computes the hyperbolic sine of `x`.\n\nThe no-data value `null` is passed through and therefore gets propagated.",
     "categories": [
         "math > trigonometric"
     ],
     "parameters": [
         {
             "name": "x",
-            "description": "An angle in radians.",
+            "description": "An hyperbolic angle in radians.",
             "schema": {
                 "type": [
                     "number",
@@ -18,7 +18,7 @@
         }
     ],
     "returns": {
-        "description": "The computed hyperbolic sine of `x`.",
+        "description": "The computed hyperbolic sine.",
         "schema": {
             "type": [
                 "number",
@@ -41,4 +41,4 @@
             "title": "Hyperbolic sine explained by Wolfram MathWorld"
         }
     ]
-}
\ No newline at end of file
+}
diff --git a/sqrt.json b/sqrt.json
index bc1aeb6c..b85caf94 100644
--- a/sqrt.json
+++ b/sqrt.json
@@ -1,7 +1,7 @@
 {
     "id": "sqrt",
     "summary": "Square root",
-    "description": "Computes the square root of a real number `x`, which is equal to calculating `x` to the power of *0.5*.\n\nA square root of x is a number a such that *`a² = x`*. Therefore, the square root is the inverse function of a to the power of 2, but only for *a >= 0*.\n\nThe no-data value `null` is passed through and therefore gets propagated.",
+    "description": "Computes the square root of a real number `x`, which is equal to calculating `x` to the power of *0.5*. For negative `x`, the process returns `NaN`.\n\nA square root of x is a number a such that *`a² = x`*. Therefore, the square root is the inverse function of a to the power of 2, but only for *a >= 0*.\n\nThe no-data value `null` is passed through and therefore gets propagated.",
     "categories": [
         "math",
         "math > exponential & logarithmic"
@@ -58,6 +58,11 @@
             "rel": "about",
             "href": "http://mathworld.wolfram.com/SquareRoot.html",
             "title": "Square root explained by Wolfram MathWorld"
+        },
+        {
+            "rel": "about",
+            "href": "https://ieeexplore.ieee.org/document/8766229",
+            "title": "IEEE Standard 754-2019 for Floating-Point Arithmetic"
         }
     ],
     "process_graph": {
@@ -72,4 +77,4 @@
             "result": true
         }
     }
-}
\ No newline at end of file
+}
diff --git a/tan.json b/tan.json
index c3952efa..6e927ffc 100644
--- a/tan.json
+++ b/tan.json
@@ -1,7 +1,7 @@
 {
     "id": "tan",
     "summary": "Tangent",
-    "description": "Computes the tangent of `x`. The tangent is defined to be the sine of x divided by the cosine of x.\n\nWorks on radians only.\nThe no-data value `null` is passed through and therefore gets propagated.",
+    "description": "Computes the tangent of `x`. The tangent is defined to be the sine of x divided by the cosine of x.\n\nWorks on radians only.\nThe no-data value `null` is passed through and therefore gets propagated.\n\nThe computations follow [IEEE Standard 754](https://ieeexplore.ieee.org/document/8766229) whenever the processing environment supports it. Therefore, *`tan(pi()/2 + multipliy(pi(), n))`* with `n` being any integer results in ±infinity. -infinity for negative values passed to `tan`, +infinity otherwise. If the processing environment does not supports it, an exception is thrown.",
     "categories": [
         "math > trigonometric"
     ],
@@ -18,7 +18,7 @@
         }
     ],
     "returns": {
-        "description": "The computed tangent of `x`.",
+        "description": "The computed tangent.",
         "schema": {
             "type": [
                 "number",
@@ -39,6 +39,11 @@
             "rel": "about",
             "href": "http://mathworld.wolfram.com/Tangent.html",
             "title": "Tangent explained by Wolfram MathWorld"
+        },
+        {
+            "rel": "about",
+            "href": "https://ieeexplore.ieee.org/document/4610935",
+            "title": "IEEE Standard 754-2008 for Floating-Point Arithmetic"
         }
     ]
-}
\ No newline at end of file
+}
diff --git a/tanh.json b/tanh.json
index 203f581e..a38462c9 100644
--- a/tanh.json
+++ b/tanh.json
@@ -1,14 +1,14 @@
 {
     "id": "tanh",
     "summary": "Hyperbolic tangent",
-    "description": "Computes the hyperbolic tangent of `x`. The tangent is defined to be the hyperbolic sine of x divided by the hyperbolic cosine of x.\n\nWorks on radians only.\nThe no-data value `null` is passed through and therefore gets propagated.",
+    "description": "Computes the hyperbolic tangent of `x`. The tangent is defined to be the hyperbolic sine of x divided by the hyperbolic cosine of x.\n\nThe no-data value `null` is passed through and therefore gets propagated.",
     "categories": [
         "math > trigonometric"
     ],
     "parameters": [
         {
             "name": "x",
-            "description": "An angle in radians.",
+            "description": "An hyperbolic angle in radians.",
             "schema": {
                 "type": [
                     "number",
@@ -18,12 +18,14 @@
         }
     ],
     "returns": {
-        "description": "The computed hyperbolic tangent of `x`.",
+        "description": "The computed hyperbolic tangent in the range *(-1, 1)*.",
         "schema": {
             "type": [
                 "number",
                 "null"
-            ]
+            ],
+            "minimumExclusive": -1,
+            "maximumExclusive": 1
         }
     },
     "examples": [
@@ -41,4 +43,4 @@
             "title": "Hyperbolic tangent explained by Wolfram MathWorld"
         }
     ]
-}
\ No newline at end of file
+}
diff --git a/xor.json b/xor.json
index d8dbde50..6af7ae5e 100644
--- a/xor.json
+++ b/xor.json
@@ -1,7 +1,7 @@
 {
     "id": "xor",
     "summary": "Logical XOR (exclusive or)",
-    "description": "Checks if **exactly one** of the values is true. If a component is `null`, the result will be `null` if the outcome is ambiguous.\n\n**Truth table:**\n\n```\na \\ b || null | false | true\n----- || ---- | ----- | -----\nnull  || null | null  | null\nfalse || null | false | true\ntrue  || null | true  | false\n```",
+    "description": "Checks if **exactly one** of the values is true. If a component is `null`, the result will be `null` if the outcome is ambiguous.\n\n**Truth table:**\n\n```\nx \\ y || null | false | true\n----- || ---- | ----- | -----\nnull  || null | null  | null\nfalse || null | false | true\ntrue  || null | true  | false\n```",
     "categories": [
         "logic"
     ],
@@ -125,4 +125,4 @@
             "result": true
         }
     }
-}
\ No newline at end of file
+}