Files
open-cmis-tck/registry/capabilities/capability.cmis.tck.md
tegwick 8b00d33336 Draft capability entry (reuse-surface REUSE-WP-0017-T04, cohort 3)
Honest first-pass maturity vector grounded in README/docs/tests present
in this repo; no invented evidence. Flagged for human review before
publish. See reuse-surface history/2026-07-06-coverage-classification.md.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-07-06 19:50:53 +02:00

118 lines
4.0 KiB
Markdown

---
id: capability.cmis.tck
name: OpenCMIS Conformance-Preparation Extension
summary: CMIS conformance-preparation extension for guide-board, keeping CMIS-specific runner code, profiles,
capability mappings, and workplans outside the generic compliance framework.
owner: open-cmis-tck
status: draft
domain: communication
tags:
- cmis
- compliance
- guide-board-extension
maturity:
discovery:
current: D2
target: D4
confidence: medium
rationale: README documents the extension relationship to guide-board (external extension root, invoked
via --extension-dir) and explicitly disclaims issuing certifications itself — it produces preparation
evidence only.
availability:
current: A1
target: A3
confidence: medium
rationale: Python package runnable via guide-board's extension mechanism (`--extension-dir ../open-cmis-tck`);
depends on a sibling guide-board checkout to function.
external_evidence:
completeness:
level: C1
confidence: low
basis: scope_vs_intent_and_consumer_expectations
satisfied_expectations:
- CMIS-specific runner code, profiles, and capability mappings kept outside the generic framework
repo
broken_expectations: []
out_of_scope_expectations: []
reliability:
level: R0
confidence: low
basis: consumer_quality_signals
known_reliability_risks:
- cannot function standalone; requires a sibling guide-board checkout
discovery:
intent: Provide CMIS-specific conformance-preparation evidence as a guide-board extension, without polluting
the generic compliance framework with CMIS specifics.
includes:
- CMIS runner code, profiles, capability mappings, workplans
excludes:
- issuing certifications (produces preparation evidence only)
- the generic compliance framework itself (see guide-board)
assumptions: []
use_cases: []
research_memos: []
availability:
current_level: A1
target_level: A3
current_artifacts:
- Python package consumed as a guide-board `--extension-dir`
target_artifacts: []
consumption_modes:
- library import (guide-board extension)
relations:
depends_on: []
supports: []
related_to: []
evidence:
documentation:
- README.md
tests:
- tests/
consumer_feedback: []
bug_reports: []
incidents: []
consumer_guidance:
recommended_for:
- guide-board users needing CMIS-specific conformance preparation
not_recommended_for:
- standalone use without a guide-board checkout
known_limitations:
- preparation evidence only; does not issue certifications
promotion_history: []
---
# OpenCMIS Conformance-Preparation Extension
## Overview
`open-cmis-tck` is the CMIS conformance-preparation extension for `guide-board`, keeping CMIS-specific runner code, profiles, and capability mappings out of the generic compliance framework. It produces preparation evidence to support future compatibility reviews and certification work, not certifications itself.
## Assessment notes
### Discovery
README documents the extension relationship to guide-board (external extension root, invoked via --extension-dir) and explicitly disclaims issuing certifications itself — it produces preparation evidence only.
### Availability
Python package runnable via guide-board's extension mechanism (`--extension-dir ../open-cmis-tck`); depends on a sibling guide-board checkout to function.
### Completeness
First-pass honest assessment from the REUSE-WP-0017 coverage campaign
(reuse-surface). No external consumer feedback exists yet; levels reflect
scope-vs-intent documentation quality, not internal code quality.
### Reliability
No production consumer telemetry exists yet; reliability level is
intentionally conservative pending REUSE-WP-0019 reuse-telemetry evidence.
## Promotion checklist
- [x] ID follows `capability.<domain>.<name>` pattern
- [x] Maturity enums match `specs/CapabilityMaturityStandard.md`
- [x] `external_evidence` is populated separately from `maturity`
- [ ] Relations reference valid capability IDs (none yet)
- [x] Index entry added in `registry/indexes/capabilities.yaml`