Conveners
OCM Interoperability Workshop
- Hugo Gonzalez Labrador (CERN)
Last year, we had a first version of the OCM test suite, testing three flows of OCM v1.0 between Nextcloud, ownCloud, and a stub server. These tests were running between a number of live test instances, deployed to virtual private servers for this purpose.
This year, we present:
* the Dockerized version of these same tests
* the addition of Reva/IOP as an OCM v1.0 implementation
* the...
The Invitation workflow is one of the elementary scenario on how to enable file sharing among users from different EFSS systems. Invitation workflow eliminates the necessity of knowing the exact identity of the user (share receiver) in the target EFSS system. You can generate a share invitation and distribute it via email or distribute the link via any other channel, chat app, etc. The target...
In the OCM specification the share message specifies the protocol to be used for establishing the synchronization. For regular shares the webdav protocol is supported.
We present a (custom) protocol 'datatx' to support data transfer in the mesh. Using this protocol signifies that the share message is in fact a data transfer.
This presentation will be about this new OCM protocol extension...
Existing implementations of OCM generally implement the public-link workflow and the share-with workflow.
Reva implements the share-with workflow and the invitation workflow.
Should other OCM implementations add this third workflow too?
Should Reva add the public-link workflow?
Can we keep OCM-over-ScienceMesh and generic OCM-over-WWW in lock-step?
OCM assumes the sender of a share is a specific user.
But in some situations it would be useful to think of
shares as owned by a group. Would this be a feature
we could add to OCM? What would be needed? What issues
can we foresee?
See also https://github.com/cs3org/OCM-API/issues/53
