Skip to content

Fix formatting of capability protocol-object #343

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
MahdiBaghbani merged 1 commit into from
Feb 25, 2026
Merged

Fix formatting of capability protocol-object #343

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 5 additions & 5 deletions IETF-RFC.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -742,11 +742,11 @@ contain the following information about its OCM API:
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.
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
Expand Down
Loading