Updated and homogenized capabilities

Author: glpatcern

IETF-RFC.md

@@ -633,29 +633,31 @@ contain the following information about its OCM API:
   to be compliant, it is not necessary to expose that as a
   capability.
   Example: `["exchange-token", "webdav-uri"]`.  The array MAY
-  include for instance:
+  include one or more of the following items:
   _ `"enforce-mfa"` - to indicate that this OCM Server can apply a
   Sending Server's MFA requirements for a Share on their behalf.
-  _ `"webdav-uri"` - to indicate that this OCM Server can append a
-  relative URI to the path listed for WebDAV [RFC4918] in the
-  appropriate `resourceTypes` entry `"protocol-object"` - to
-  indicate that this OCM Server can receive a Share Creation
-  Notification whose `protocol` object contains one property per
-  supported protocol instead of containing the standard `name` and
-  `options` properties.
-  _ `"invites"` - to indicate the server would support acting as an
-  Invite Sender or Invite Receiver OCM Server.  This might be useful
-  for suggesting to a user that existing contacts might be upgraded
-  to the more secure (and possibly required) invite flow.
   _ `"exchange-token"` - to indicate that this OCM Server exposes a
   [RFC6749]-compliant endpoint, which allows to exchange a secret
   received in the protocol properties of a Share Creation Notification
   for a short-lived bearer token.
-  _ `"invite-wayf"` - to indicate that this OCM Server exposes a WAYF
-  Page to facilitate the Invite flow.
   _ `"http-sig"` - to indicate that this OCM Server supports
   [RFC9421] HTTP Message Signatures and advertises public keys in the
   `publicKeys` array for signature verification.
+  _ `"invites"` - to indicate the server would support acting as an
+  Invite Sender or Invite Receiver OCM Server.  This might be useful
+  for suggesting to a user that existing contacts might be upgraded
+  to the more secure (and possibly required) invite flow.
+  _ `"notifications"` - to indicate that this OCM Server handles
+  notifications to exchange updates on shares and invites.
+  _ `"invite-wayf"` - to indicate that this OCM Server exposes a WAYF
+  Page to facilitate the Invite flow.
+  _ `"webdav-uri"` - to indicate that this OCM Server can append a
+  relative URI to the path listed for WebDAV [RFC4918] in the
+  appropriate `resourceTypes` entry `"protocol-object"` - to
+  indicate that this OCM Server can receive a Share Creation
+  Notification whose `protocol` object contains one property per
+  supported protocol instead of containing the standard `name` and
+  `options` properties.
 * OPTIONAL: criteria (array of string) - The criteria for accepting a
   Share Creation Notification.
   As all Receiving Servers SHOULD require the use of TLS in API

spec.yaml

@@ -388,17 +388,18 @@ components:
           type: array
           description: >
             The optional capabilities exposed at this endpoint according to the
-            present
-            specifications.
+            present specifications.
           items:
             type: string
             enum:
               - enforce-mfa
-              - webdav-uri
-              - protocol-object
-              - invites
               - exchange-token
               - http-sig
+              - invites
+              - invite-wayf
+              - notifications
+              - protocol-object
+              - webdav-uri
           example:
             - webdav-uri
             - protocol-object