Preparing version 1.2.2 (#287)

Author: glpatcern

CHANGELOG.md

@@ -1,5 +1,11 @@
 # Changelog
 
+## [1.2.2] - 2025-10-21 - Giuseppe Lo Presti <[email protected]>
+
+* Further improvements and clarifications in the spec, prior to
+  handing over to the IETF.
+* Introduced concept of Invite string for the Invite flow.
+
 ## [1.2.1] - 2025-07-17 - Giuseppe Lo Presti <[email protected]>
 
 * Overall review of the spec in the ongoing quest to improve clarity

IETF-RFC.md

@@ -572,7 +572,7 @@ contain the following information about its OCM API:
 * REQUIRED: enabled (boolean) - Whether the OCM service is enabled at
   this endpoint
 * REQUIRED: apiVersion (string) - The OCM API version this endpoint
-  supports.  Example: `"1.2.1"`
+  supports.  Example: `"1.2.2"`
 * REQUIRED: endPoint (string) - The URI of the OCM API available at
   this endpoint.  Example: `"https://my-cloud-storage.org/ocm"`
 * OPTIONAL: provider (string) - A friendly branding name of this

README.md

@@ -8,7 +8,7 @@
 This repository contains the text of the [Open Cloud Mesh IETF Draft](https://datatracker.ietf.org/doc/draft-lopresti-open-cloud-mesh/), as well as the equivalent [OpenAPI](https://github.com/OAI/OpenAPI-Specification) (fka Swagger) specification for its API rendered as HTML (by [ReDoc](https://github.com/Redocly/redoc)).
 
 The documents are available as follows:
-* **Latest official version, 1.2.1**: [RFC-formatted Draft](https://github.com/cs3org/OCM-API/blob/v1.2.1/IETF-RFC.md) | [API spec](https://cs3org.github.io/OCM-API/docs.html?branch=v1.2.1&repo=OCM-API&user=cs3org)
+* **Latest official version, 1.2.2**: [RFC-formatted Draft](https://github.com/cs3org/OCM-API/blob/v1.2.2/IETF-RFC.md) | [API spec](https://cs3org.github.io/OCM-API/docs.html?branch=v1.2.2&repo=OCM-API&user=cs3org)
 * Development branch: [RFC-formatted Draft](IETF-RFC.md) | [API spec](https://cs3org.github.io/OCM-API/docs.html?branch=develop&repo=OCM-API&user=cs3org)
 
 [SemVer](https://semver.org) versioning applies to OCM, and backwards compatibility is supported unless stated otherwise by an implementation.

spec.yaml

@@ -5,7 +5,7 @@ info:
     Open Cloud Mesh OpenAPI Specification.
     The semantic of the Protocol Specification is detailed in the
     [IETF-RFC.md](https://github.com/cs3org/OCM-API/blob/develop/IETF-RFC.md) document.
-  version: 1.2.1
+  version: 1.2.2
   x-logo:
     url: logo.png
 servers:
@@ -327,7 +327,7 @@ components:
         apiVersion:
           type: string
           description: The OCM API version this endpoint supports
-          example: 1.2.1
+          example: 1.2.2
         endPoint:
           type: string
           description: The URI of the OCM API available at this endpoint
@@ -348,17 +348,17 @@ components:
               name:
                 type: string
                 description: >
-                  A supported resource type (file, calendar, contact, ...). 
-                  Implementations MUST offer support for at least one resource type, 
-                  where `file` is the commonly supported one. 
-                  Each resource type is identified by its `name`: the list MUST NOT 
+                  A supported resource type (file, calendar, contact, ...).
+                  Implementations MUST offer support for at least one resource type,
+                  where `file` is the commonly supported one.
+                  Each resource type is identified by its `name`: the list MUST NOT
                   contain more than one resource type object per given `name`
                 example: file
               shareTypes:
                 type: array
                 description: |
-                  The supported recipient share types. 
-                  MUST contain `"user"` at a minimum, plus optionally 
+                  The supported recipient share types.
+                  MUST contain `"user"` at a minimum, plus optionally
                   `"group"` and `"federation"`.
                 items:
                   type: string