Relax minimum requirements to qualify as OCM Server#192
Merged
Conversation
glpatcern
force-pushed
the
min-requirements
branch
from
45654b7 to
4a4a32d
Compare
mickenordin
approved these changes
Jun 12, 2025
Member
mickenordin
left a comment
mickenordin
left a comment
There was a problem hiding this comment.
Yes, this looks good according to our discussion today
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This change is proposed, as discussed today, in the context of OCM implementations for third-party integrations (cf. #180 and #191).
The idea here is that the third-party component is not an EFSS, and may only offer limited support for a given type of resource, NOT including
file. Yet, it would expose an OCM discovery endpoint and issue Share Creation Notification requests to recipients that possibly host a full-fledged OCM server.