Most EFSS solutions provide a certain version history of a resource (file). When receiving a resource from another server, this is usually limited to the latest version of said resource. In some cases, the receiving party might want to have access to the whole version history of a resource. OCM should either specify a mechanism on how versions of resources could be made available (e.g., through capabilities), or explicitly state that version history is out of scope.
Most EFSS solutions provide a certain version history of a resource (file). When receiving a resource from another server, this is usually limited to the latest version of said resource. In some cases, the receiving party might want to have access to the whole version history of a resource. OCM should either specify a mechanism on how versions of resources could be made available (e.g., through capabilities), or explicitly state that version history is out of scope.