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

4.0 KiB

id, name, summary, owner, status, domain, tags, maturity, external_evidence, discovery, availability, relations, evidence, consumer_guidance, promotion_history
id name summary owner status domain tags maturity external_evidence discovery availability relations evidence consumer_guidance promotion_history
capability.cmis.tck OpenCMIS Conformance-Preparation Extension CMIS conformance-preparation extension for guide-board, keeping CMIS-specific runner code, profiles, capability mappings, and workplans outside the generic compliance framework. open-cmis-tck draft communication
cmis
compliance
guide-board-extension
discovery availability
current target confidence rationale
D2 D4 medium 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.
current target confidence rationale
A1 A3 medium Python package runnable via guide-board's extension mechanism (`--extension-dir ../open-cmis-tck`); depends on a sibling guide-board checkout to function.
completeness reliability
level confidence basis satisfied_expectations broken_expectations out_of_scope_expectations
C1 low scope_vs_intent_and_consumer_expectations
CMIS-specific runner code, profiles, and capability mappings kept outside the generic framework repo
level confidence basis known_reliability_risks
R0 low consumer_quality_signals
cannot function standalone; requires a sibling guide-board checkout
intent includes excludes assumptions use_cases research_memos
Provide CMIS-specific conformance-preparation evidence as a guide-board extension, without polluting the generic compliance framework with CMIS specifics.
CMIS runner code, profiles, capability mappings, workplans
issuing certifications (produces preparation evidence only)
the generic compliance framework itself (see guide-board)
current_level target_level current_artifacts target_artifacts consumption_modes
A1 A3
Python package consumed as a guide-board `--extension-dir`
library import (guide-board extension)
depends_on supports related_to
documentation tests consumer_feedback bug_reports incidents
README.md
tests/
recommended_for not_recommended_for known_limitations
guide-board users needing CMIS-specific conformance preparation
standalone use without a guide-board checkout
preparation evidence only; does not issue certifications

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

  • ID follows capability.<domain>.<name> pattern
  • Maturity enums match specs/CapabilityMaturityStandard.md
  • external_evidence is populated separately from maturity
  • Relations reference valid capability IDs (none yet)
  • Index entry added in registry/indexes/capabilities.yaml