generated from coulomb/repo-seed
CMIS Browser Binding serializer layer
This commit is contained in:
@@ -4,7 +4,7 @@ type: workplan
|
||||
title: "CMIS Browser Binding TCK Compatibility"
|
||||
domain: markitect
|
||||
repo: kontextual-engine
|
||||
status: planned
|
||||
status: completed
|
||||
owner: codex
|
||||
topic_slug: markitect
|
||||
planning_priority: high
|
||||
@@ -38,6 +38,7 @@ The result is persisted in
|
||||
## References
|
||||
|
||||
- `docs/cmis-opencmis-tck-assessment-2026-05-08T063312Z.md`
|
||||
- `docs/cmis-opencmis-tck-implementation-evidence-2026-05-08T092113Z.md`
|
||||
- `docs/cmis-1-1-capability-scorecard.md`
|
||||
- `docs/cmis-compliance-assessment.md`
|
||||
- `docs/cmis-profiled-access-points-implementation.md`
|
||||
@@ -70,11 +71,25 @@ adds them explicitly.
|
||||
- Updated CMIS scorecard separates TCK-backed compatibility from native
|
||||
controlled-client usefulness.
|
||||
|
||||
## Implementation Evidence
|
||||
|
||||
Completed on 2026-05-08 with final live run `run-20260508T092113Z`.
|
||||
|
||||
- Focused internal CMIS suite: `45 passed`.
|
||||
- Guide Board/OpenCMIS status: `completed`.
|
||||
- Repository/type cases: `38 pass`, `2 info`, `2 skipped`, `1 warning`, `0 fail`.
|
||||
- Object/content cases: `22 skipped`, `0 fail`.
|
||||
- Latest TCK preparation scorecard: `23.81`, coverage `2/9`.
|
||||
|
||||
The only remaining repository/type warning is local HTTP transport. The
|
||||
object/content skips are caused by the deliberate non-creatable `cmis:folder`
|
||||
profile boundary, not by a Browser Binding session failure.
|
||||
|
||||
## F13.1 - Define Browser Binding protocol contract examples
|
||||
|
||||
```task
|
||||
id: KONT-WP-0013-T001
|
||||
status: todo
|
||||
status: done
|
||||
priority: high
|
||||
state_hub_task_id: "fa2f99fb-51ed-4fba-8f36-ba4b790908e5"
|
||||
```
|
||||
@@ -92,7 +107,7 @@ Acceptance:
|
||||
|
||||
```task
|
||||
id: KONT-WP-0013-T002
|
||||
status: todo
|
||||
status: done
|
||||
priority: high
|
||||
state_hub_task_id: "39949f5b-32bb-4ec7-b0f6-83a16ce443b7"
|
||||
```
|
||||
@@ -111,7 +126,7 @@ Acceptance:
|
||||
|
||||
```task
|
||||
id: KONT-WP-0013-T003
|
||||
status: todo
|
||||
status: done
|
||||
priority: high
|
||||
state_hub_task_id: "96e11fe6-68c6-46ce-88b8-bda0b9baf2d5"
|
||||
```
|
||||
@@ -128,7 +143,7 @@ Acceptance:
|
||||
|
||||
```task
|
||||
id: KONT-WP-0013-T004
|
||||
status: todo
|
||||
status: done
|
||||
priority: high
|
||||
state_hub_task_id: "06506455-b3c3-4f17-ae8a-8ffebc226f73"
|
||||
```
|
||||
@@ -141,11 +156,16 @@ Acceptance:
|
||||
generic infrastructure error.
|
||||
- The preflight reports actionable missing or misshaped fields.
|
||||
|
||||
Completion note: the engine-side protocol-shape regression is now covered by
|
||||
Browser Binding route tests and the live OpenCMIS run. A stronger negative
|
||||
preflight fixture belongs in the sister `open-cmis-tck` repository and remains
|
||||
a follow-up outside this repo's implementation boundary.
|
||||
|
||||
## F13.5 - Fix OpenAPI generation for streaming routes
|
||||
|
||||
```task
|
||||
id: KONT-WP-0013-T005
|
||||
status: todo
|
||||
status: done
|
||||
priority: medium
|
||||
state_hub_task_id: "de73a3ff-ddf9-40bb-b89c-50d6fabdb841"
|
||||
```
|
||||
@@ -161,7 +181,7 @@ Acceptance:
|
||||
|
||||
```task
|
||||
id: KONT-WP-0013-T006
|
||||
status: todo
|
||||
status: done
|
||||
priority: medium
|
||||
state_hub_task_id: "1cf8d36c-6127-46cd-b409-dda7a045b8dd"
|
||||
```
|
||||
@@ -178,7 +198,7 @@ Acceptance:
|
||||
|
||||
```task
|
||||
id: KONT-WP-0013-T007
|
||||
status: todo
|
||||
status: done
|
||||
priority: high
|
||||
state_hub_task_id: "38777aea-7d2d-4b30-99b4-5194f2c2f8b0"
|
||||
```
|
||||
@@ -194,7 +214,7 @@ Acceptance:
|
||||
|
||||
```task
|
||||
id: KONT-WP-0013-T008
|
||||
status: todo
|
||||
status: done
|
||||
priority: high
|
||||
state_hub_task_id: "8e7b2235-d39a-465a-b828-b05eb6bcfce3"
|
||||
```
|
||||
@@ -209,7 +229,7 @@ Acceptance:
|
||||
|
||||
```task
|
||||
id: KONT-WP-0013-T009
|
||||
status: todo
|
||||
status: done
|
||||
priority: high
|
||||
state_hub_task_id: "22af3e39-c217-4f6b-b54a-5ecea3894020"
|
||||
```
|
||||
@@ -226,7 +246,7 @@ Acceptance:
|
||||
|
||||
```task
|
||||
id: KONT-WP-0013-T010
|
||||
status: todo
|
||||
status: done
|
||||
priority: medium
|
||||
state_hub_task_id: "469a3ea6-a6ab-4e6e-ba4f-5b1abdabd6c4"
|
||||
```
|
||||
@@ -247,3 +267,10 @@ Acceptance:
|
||||
- Object/content TCK group produces parsed evidence or documented
|
||||
unsupported-by-design gaps.
|
||||
- Updated documentation clearly states the evidence-backed CMIS posture.
|
||||
|
||||
## Follow-Up Boundary
|
||||
|
||||
The next CMIS decision is not another protocol-shape fix. It is whether to
|
||||
support CMIS `createFolder` in the `compat-tck` profile so OpenCMIS CRUD/content
|
||||
cases execute instead of skipping, or whether to keep those skips as an honest
|
||||
profile boundary until a client requires full CMIS CRUD scaffolding.
|
||||
|
||||
Reference in New Issue
Block a user