CMIS Browser Binding serializer layer

This commit is contained in:
2026-05-08 12:27:26 +02:00
parent 6382a5a7ab
commit 54a26cdb02
9 changed files with 1172 additions and 40 deletions

View File

@@ -2,12 +2,16 @@
Date: 2026-05-07
Evidence update: the 2026-05-08 OpenCMIS TCK run found that broad commodity
CMIS client compatibility is currently pre-compliance because OpenCMIS cannot
create a Browser Binding session. See
`docs/cmis-opencmis-tck-assessment-2026-05-08T063312Z.md`. The score below is
therefore retained as the pre-TCK product-depth estimate, not as external CMIS
compatibility evidence.
Evidence update: the 2026-05-08 OpenCMIS TCK compatibility implementation
resolved the initial Browser Binding session blocker. The latest run,
`run-20260508T092113Z`, completed the selected baseline with `38` passing
repository/type cases, one local HTTP transport warning, and `22` object/content
skips caused by the current non-creatable folder profile. See
`docs/cmis-opencmis-tck-implementation-evidence-2026-05-08T092113Z.md`.
The score below remains a product-depth estimate against mature CMIS products;
the evidence-backed TCK preparation score for the selected baseline is `23.81`
with `2/9` capability groups covered.
Status: baseline scorecard for the current Browser Binding subset.
@@ -98,16 +102,17 @@ replacement surface.
| Browser Binding protocol fidelity | 7 | 45% | Hyland Alfresco ACS | - Browser-style routes and JSON envelopes exist.<br>- FastAPI route shapes are pragmatic, not complete CMIS Browser Binding selector/action parity.<br>- Route-level tests skip without optional service dependencies. |
| AtomPub binding | 2 | 0% | Hyland Alfresco ACS | - No AtomPub/XML service document or feeds.<br>- Intentionally deferred until monetized need. |
| Web Services binding | 2 | 0% | Hyland Alfresco ACS | - No SOAP/WSDL stack.<br>- Intentionally deferred until monetized need. |
| External conformance evidence | 3 | 20% | OpenCMIS TCK against Alfresco-like server behavior | - Internal fixtures and optional TCK mapping exist.<br>- No recorded OpenCMIS TCK execution against a running access point yet.<br>- No third-party client compatibility matrix yet. |
| External conformance evidence | 3 | 35% | OpenCMIS TCK against Alfresco-like server behavior | - OpenCMIS Browser Binding session creation now succeeds against `compat-tck`.<br>- Selected `repository-type` baseline completes with no failures and one local HTTP warning.<br>- `object-content` reaches parsed cases but skips because `cmis:folder` is not creatable; broader groups and third-party client matrix are still missing. |
Weighted result from this table: **42%**.
## Most Important Gaps
1. **External conformance run**
- Run selected OpenCMIS TCK groups against `compat-tck`.
- Capture failures by capability group.
- Turn "estimated" scores into evidence-backed scores.
1. **External conformance expansion**
- Keep the selected OpenCMIS TCK baseline running against `compat-tck`.
- Decide whether to add TCK-only `createFolder` support or keep CRUD/content
skips as a deliberate profile boundary.
- Expand selected groups after the supported capability boundary is agreed.
2. **Browser Binding fidelity**
- Align route/action/selector shapes more closely with CMIS Browser Binding.