generated from coulomb/repo-seed
New assessment of CMIS functionality
This commit is contained in:
@@ -72,14 +72,17 @@ CMIS interoperability importance rather than engine-internal importance.
|
||||
|
||||
| Metric | Score |
|
||||
| --- | ---: |
|
||||
| OpenCMIS selected-baseline infrastructure score | 98.3% |
|
||||
| Weighted CMIS 1.1 depth vs Hyland Alfresco benchmark | 59% |
|
||||
| Controlled-client Browser Binding usefulness | 80% |
|
||||
| Broad commodity CMIS client compatibility | 54% |
|
||||
|
||||
Interpretation: the current CMIS layer is a credible Browser Binding subset for
|
||||
known clients and profile-specific integrations, especially around repository,
|
||||
type, object, folder, content, move/copy, and controlled mutation workflows. It
|
||||
is not yet a broad ECM/CMIS replacement surface.
|
||||
Interpretation: the OpenCMIS infrastructure score measures the selected
|
||||
`repository-type` and `object-content` harness baseline only. The current CMIS
|
||||
layer is a credible Browser Binding subset for known clients and
|
||||
profile-specific integrations, especially around repository, type, object,
|
||||
folder, content, move/copy, and controlled mutation workflows. It is not yet a
|
||||
broad ECM/CMIS replacement surface.
|
||||
|
||||
## Capability Scorecard
|
||||
|
||||
|
||||
Reference in New Issue
Block a user