T2 – Package Generation

Version: 0.9.0
Status: Release Candidate
Type: Normative Conformance Test Specification

Copyright © 2026 inside workspace GmbH
This work is licensed under the Creative Commons Attribution 4.0 International (CC BY 4.0) License.

1 Introduction

1.1 Purpose

This specification defines the reference process for generating a Knowledge Asset Package.

The Package Generation process transforms a collection of Knowledge Assets and associated resources into a complete, signed Knowledge Asset Package conforming to the KAPRI specification.

The generated Package serves as the reference Package used for interoperability testing.

1.2 Scope

This specification defines:

the Package generation workflow,
the execution order of generation steps,
the generated Package components,
the Package Generation conformance tests.

This specification does not define:

knowledge authoring,
content management,
editing environments,
production workflows.

1.3 Relationship to Other Specifications

This specification validates requirements defined by:

SC0 – Common Serialization Rules
SC1 – Common Data Types
S1 – Package Manifest Schema
S2 – Packing List Schema
S3 – Composition Schema
S4 – KAP Key Delivery Message Schema

The generated Package SHALL conform to all referenced specifications.

2 Package Generation

2.1 Purpose

Package Generation produces a complete Knowledge Asset Package from a defined collection of Knowledge Assets and associated resources.

The resulting Package SHALL be structurally complete, internally consistent and suitable for cryptographic validation.

2.2 Generation Workflow

The reference generation workflow SHALL consist of the following steps.

Knowledge Assets
        │
        ▼
Generate Package Files
        │
        ▼
Generate Packing List
        │
        ▼
Generate Composition
        │
        ▼
Generate Package Manifest
        │
        ▼
Canonicalize Manifest
        │
        ▼
Digitally Sign Package Manifest
        │
        ▼
Generate KAP-KDM (if required)

2.3 Generated Components

The generated Package SHALL contain:

one Package Manifest,
one Packing List,
one or more Compositions,
all referenced Package Files.

If encrypted Package Files are present, a corresponding KAP-KDM SHALL be generated separately.

3 Conformance Tests

The reference Package Generation SHALL provide the following executable conformance tests.

T2.7 corresponds to T4.2–T4.4 (Encrypt File Keys, Generate KAP-KDM, Sign KAP-KDM), as defined by T4 – Secure Delivery. It is listed here for completeness of the Package Generation workflow and does not impose a separate implementation requirement beyond T4.2–T4.4.

4 Test Execution Order

The Package Generation tests SHALL be executed in the following order.

T2.1 Generate Package Files
        ↓
T2.2 Generate Packing List
        ↓
T2.3 Generate Composition
        ↓
T2.4 Generate Package Manifest
        ↓
T2.5 Canonicalize Package Manifest
        ↓
T2.6 Digitally Sign Package Manifest
        ↓
T2.7 Generate KAP-KDM (optional)

Each step depends on the successful completion of all preceding steps.

5 Expected Results

The generated Knowledge Asset Package SHALL:

contain all mandatory Package components,
contain all referenced Package Files,
satisfy all structural requirements,
contain valid references between Package components,
satisfy all integrity requirements,
contain a valid digital signature,
be suitable for independent validation by conforming Consumers.

6 Conformance

An implementation claiming conformance with this specification SHALL:

execute the Package Generation process in the defined order,
generate Package components conforming to S1–S4,
preserve all identifiers and references,
produce a Knowledge Asset Package that successfully passes all applicable Technical Validation defined by S0.

T2 – Package Generation

1 Introduction

Kontakt

Login