Skip to content

[3.13] Templates, worked examples & tooling #13

Description

@ozzyathome

Aspect

Section: 3.13 Templates, worked examples, and tooling considerations
Orientation relevance: both

Objective

Decide the standard profile-definition template, the first worked-example profile to develop
end-to-end, and what the methodology says about tooling. Develop in parallel to test the
method against a real case; finalise last, as it captures the outputs of the other aspects.

Background & links

Scoping document §3.13. A methodology is adopted in proportion to how easy it is to apply.
A procurement or PQC-migration profile is the natural first worked example.

Options under consideration

  • Single canonical template + one worked example — one template capturing objective,
    scope, attribute selection, obligations, mappings, semantics, governance; one end-to-end
    example. (Trade-off: focused; may not cover both orientations.)
  • Per-orientation templates — separate inventory and migration templates.
    (Trade-off: better fit; more to maintain.)
  • Tooling stance — describe generation/validation/ingestion needs without mandating
    specific tools (tool-neutral but tool-friendly).

Open questions

  • A standard profile-definition template capturing the outputs of the other aspects.
  • At least one worked-example profile developed end-to-end (procurement or PQC-migration a natural first candidate).
  • What the methodology says about tooling, without mandating specific tools.

Dependencies

Depends on the outputs of 3.1–3.12 (especially the model 3.3 #1, obligations 3.4 #6,
and conformance 3.5 #7). Develop the worked example in parallel; finalise the template last.

Decision

Not yet decided.

Impact on the specification

Spec section "Profile-definition template and worked example," plus the worked-example annex.

Metadata

Metadata

Assignees

No one assigned

    Labels

    aspect:templates-tooling3.13 Templates, worked examples & toolingneeds:ownerNo aspect owner assigned yetstatus:deliberatingOpen argument — options being exploredtype:decisionA concrete choice to be resolved

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions