Clarify resourceType use in new shares (#285)

Author: glpatcern

IETF-RFC.md

@@ -749,7 +749,10 @@ To create a Share, the Sending Server SHOULD make a HTTP POST request
   metadata and act as an OCM proxy, forwarding the OCM requests to
   the actual members of the federation.
 * REQUIRED resourceType (string)
-  Resource type (file, calendar, contact, ...)
+  Resource type (file, folder, calendar, contact, ...).  If the
+  Resource is a folder, implementations SHOULD advertise it as
+  `folder` rather than `file`, in order to streamline the processing
+  by the Receiving Server.
 * OPTIONAL expiration (integer)
   The expiration time for the OCM share, in seconds
   of UTC time since Unix epoch.  If omitted, it is assumed

spec.yaml

@@ -543,7 +543,7 @@ components:
         resourceType:
           type: string
           description: |
-            Resource type (file, calendar, contact, ...)
+            Resource type (file, folder, calendar, contact, ...)
           example: file
         expiration:
           type: integer
@@ -766,7 +766,7 @@ components:
         resourceType:
           type: string
           description: |
-            Resource type (file, user, calendar, contact, ...)
+            Resource type (file, folder, user, calendar, contact, ...)
         providerId:
           type: string
           description: |