Decision support

Compare standards by the job they do

Place up to three profiles side by side. Compare their architectural role, lifecycle reach, and first limitation to test. No single standard covers every layer.

Choose profiles

1 of 3 selected

CAREGovernance framework

Compare roles before choosing an implementation.

The useful question is not “Which standard wins?” It is “Which job must this part of the architecture perform, and what remains uncovered?”

  1. Start with the job

    Decide whether you need guidance, a domain payload, exchange, semantics, governance, or a reusable release.

  2. Map lifecycle reach

    Use the matrix to see where each profile has a direct role. A filled cell is coverage, not a quality score.

  3. Test the boundary

    Read what each option leaves unresolved before judging maturity or implementation fit.

Review lifecycle coverage and practical fit.

Read left to right. Lifecycle reach comes first; a maturity label never overrides a scope mismatch.

Where each profile contributes directly

Coverage shows a recorded role at that readiness stage. It does not imply end-to-end implementation.

Readiness-stage coverage for CARE Principles for Indigenous Data Governance
ProfilePlanAcquireHarmonizeExchangeLearn + reuse
CAREGovernance frameworkCARE Principles for Indigenous Data Governance has a direct role in Plan.CARE Principles for Indigenous Data Governance has a direct role in Acquire.CARE Principles for Indigenous Data Governance has a direct role in Harmonize.CARE Principles for Indigenous Data Governance has a direct role in Exchange.CARE Principles for Indigenous Data Governance has a direct role in Learn + reuse.
Direct role recordedNo direct role recorded

What each option does not cover

These are design boundaries, not faults. Use them to identify the companion layers your architecture still needs.

CARE

Stage boundary
No direct stage gap is recorded. Lifecycle reach still does not make this an end-to-end implementation.
Known limitation
CARE is not a checklist that an external organization can self-certify; obligations are community and context specific, and implementation requires continuing participation by legitimate Indigenous authorities.

Check the fit and source behind the map

Use the official source, version, and limitation together. A higher maturity label does not erase a scope mismatch.

Detailed comparison of CARE Principles for Indigenous Data Governance
AssessmentCARECARE Principles for Indigenous Data Governance
Purpose & coverage

Collective Benefit, Authority to Control, Responsibility, and Ethics for the governance and use of Indigenous data and Indigenous Knowledge.

Best fitAny data activity involving Indigenous peoples, lands, resources, knowledge, or community interests where openness and reuse must be governed through rights, authority, benefit, and accountability.

Readiness stages
PlanAcquireHarmonizeExchangeLearn + reuse
AI-ready contributionPrevents technically reusable data from being treated as automatically appropriate for AI, while machine-readable controls remain secondary to community authority and accountable review.
First limitation to testCARE is not a checklist that an external organization can self-certify; obligations are community and context specific, and implementation requires continuing participation by legitimate Indigenous authorities.
Maturity

Established

Established people- and purpose-oriented governance reference; no universal conformance specification

Sources & links