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 |
|
| Metric | Score |
|
||||||
| --- | ---: |
|
| --- | ---: |
|
||||||
|
| OpenCMIS selected-baseline infrastructure score | 98.3% |
|
||||||
| Weighted CMIS 1.1 depth vs Hyland Alfresco benchmark | 59% |
|
| Weighted CMIS 1.1 depth vs Hyland Alfresco benchmark | 59% |
|
||||||
| Controlled-client Browser Binding usefulness | 80% |
|
| Controlled-client Browser Binding usefulness | 80% |
|
||||||
| Broad commodity CMIS client compatibility | 54% |
|
| Broad commodity CMIS client compatibility | 54% |
|
||||||
|
|
||||||
Interpretation: the current CMIS layer is a credible Browser Binding subset for
|
Interpretation: the OpenCMIS infrastructure score measures the selected
|
||||||
known clients and profile-specific integrations, especially around repository,
|
`repository-type` and `object-content` harness baseline only. The current CMIS
|
||||||
type, object, folder, content, move/copy, and controlled mutation workflows. It
|
layer is a credible Browser Binding subset for known clients and
|
||||||
is not yet a broad ECM/CMIS replacement surface.
|
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
|
## Capability Scorecard
|
||||||
|
|
||||||
|
|||||||
@@ -29,6 +29,38 @@ Guide Board summary:
|
|||||||
- `pass`: 1
|
- `pass`: 1
|
||||||
- `warning`: 2
|
- `warning`: 2
|
||||||
|
|
||||||
|
## OpenCMIS Infrastructure Score
|
||||||
|
|
||||||
|
This is a compatibility-infrastructure score for the selected Browser Binding
|
||||||
|
baseline, not a CMIS certification score and not the broader product-depth
|
||||||
|
score from `docs/cmis-1-1-capability-scorecard.md`.
|
||||||
|
|
||||||
|
Formula:
|
||||||
|
|
||||||
|
- Accepted case = `pass`, `info`, or declared `skipped`.
|
||||||
|
- Warning case = half credit.
|
||||||
|
- Hard blocker = `fail`, `infrastructure_error`, or unexpected finding.
|
||||||
|
|
||||||
|
Scores:
|
||||||
|
|
||||||
|
| Metric | Score | Basis |
|
||||||
|
| --- | ---: | --- |
|
||||||
|
| Selected baseline completion | 100.0% | Guide Board result `completed`; both selected groups returned `0`. |
|
||||||
|
| Unexpected finding clearance | 100.0% | `0` unexpected findings, `0` fail, `0` infrastructure_error. |
|
||||||
|
| Warning-adjusted normalized case score | 98.3% | `(56 accepted + 0.5 * 2 warnings) / 58 normalized cases`. |
|
||||||
|
| Strict no-warning normalized case score | 96.6% | `56 accepted / 58 normalized cases`. |
|
||||||
|
|
||||||
|
Digest versus the previous WP-0014 object/content frontier
|
||||||
|
(`run-20260508T164334Z`):
|
||||||
|
|
||||||
|
- Overall OpenCMIS status improved from `infrastructure_error` to `completed`.
|
||||||
|
- Object/content hard blockers improved from `3 fail` and
|
||||||
|
`3 infrastructure_error` to `0 fail` and `0 infrastructure_error`.
|
||||||
|
- Object/content warnings improved from `3 warning` to `1 warning`.
|
||||||
|
- The old remaining blockers were closed: CMIS exception mapping,
|
||||||
|
`bulkUpdateProperties`, `deleteContentStream`, change-token conflict
|
||||||
|
handling, copy/create-from-source, and offset-zero range classification.
|
||||||
|
|
||||||
## Blocker Resolution
|
## Blocker Resolution
|
||||||
|
|
||||||
Resolved in this pass:
|
Resolved in this pass:
|
||||||
|
|||||||
Reference in New Issue
Block a user