OCM-API Existing standards

There are already existing standards that we could use/be based on them:

File management: WebDAV, remoteStorage
Full user and group management (CRUD): System for Cross-domain Identity Management (SCIM)

For using WebDAV as synchronisation protocol there are already documents here: https://github.com/labkode/Internet-Storage-Sync/blob/master/applicability-of-webdav.md

Also, is worth looking into this for pros/cons of WebDAV vs REST for syncing:

Nov 18 '16 14:11 labkode

Here is the one currently used by owncloud and nextcloud: https://github.com/cernbox/smashbox/blob/master/protocol/protocol.md

Nov 18 '16 15:11 moscicki

Also, is worth looking into this for pros/cons of WebDAV vs REST for syncing:

WebDAV already provides a specification for Syncronization of resource collections: https://tools.ietf.org/html/rfc6578

This is the basis for CalDAV and CardDAV synchronization which from my pov has been proved to work in this aread for quite some years now.

Nov 18 '16 18:11 DeepDiver1975

@DeepDiver1975 I haven't read through all the RFC so far, but do you know if it supports MOVE?

Nov 23 '16 22:11 dragotin

@dragotin https://tools.ietf.org/html/rfc6578#section-3.5.1 is explicitly talking about COPY MOVE and BIND - but there seems to be no explicit status/information on the operation.

Basically the result of this sync report is a list of changed (including added) and deleted resources.

For detection of MOVE we need to use additional properites like we do today with the fileid.

Nov 24 '16 08:11 DeepDiver1975