FR-04 Adhere to Standardized API Definitions

[danisoler-charin]

Description: All pool operators shall implement the defined API standard (OPNC) for certificate provisioning and related operations.
Use Case: Any scenario involving API interaction between pools
Already in OPNC 1?: This FR has been flagged as Possible in all APIs.

What I understad is:
All pools must implement the exact same API endpoints, input formats, and output formats as defined in the OPNC spec.

Are all current APIs enough and well documented?
How could we review this?

[steffenrhinow]

we did already multiple times a Gap Analysis bases on the Charin PnC USecases and could not find any gaps.
Documentation - can be always improved, but needs to be judged by tech staff which want ti activly use it

[danisoler-charin]

After discussion on 09/07/25:
Current status:
This requirement is already supported in the current OPNC implementation. No missing functionality was identified.

Improvement area:
The main need is for clearer documentation, such as:

• API sequence diagrams
• Service call flow examples
• Better explanation of message transitions

Classification note:
This is more a protocol compliance rule than a functional requirement, and may not need to be tracked in the same way as the others.

No further discussion expected