4.6 Relationship to Transaction Requirements and Conformance

Endpoint capability descriptions communicate supported interoperability behavior. They do not establish or modify the normative requirements of the transactions being implemented.

The applicable GenTXDef or UCTXDef remains authoritative for its transaction requirements, including Sender Actor and Receiver Actor responsibilities, information-object requirements, metadata constraints, workflow status obligations, and transaction-specific processing rules.

An implementation may support a subset of available MAP transactions. Supporting one transaction does not automatically establish support for other transactions or for optional capabilities associated with them.

Conformance to an applicable Transaction Definition is determined by the requirements of that definition and any governing conformance provisions, not solely by the existence or contents of a published capability description.

Implementation Guides may provide additional use case-specific capability guidance or examples. Such guidance should distinguish recommended publication practices from requirements explicitly established by applicable specifications.

The MAP Framework encourages implementers to begin with useful, understandable capability descriptions and progressively adopt more structured or automated approaches when they provide practical interoperability value.