Open APIs

 View Only

TMF651_Clarification on Mandatory Parameter 'engagedPartyRole' for Conformance Validation

  • 1.  TMF651_Clarification on Mandatory Parameter 'engagedPartyRole' for Conformance Validation

    Posted yesterday

    Dear TMF Team,

    I am currently performing a conformance activity for a telecom operator. While reviewing the conformance profile (RAND), I noticed that engagedPartyRole is marked as a mandatory parameter.

    However, when I reviewed the corresponding TMF Open API Specification and the Swagger (OpenAPI) definition, I could not find engagedPartyRole defined as a mandatory parameter. Please refer to the attached screenshots for reference.

    Could you please clarify:

    • What is the official reference to be used when validating conformance in this case?

    • Should the conformance validation follow the Conformance Profile (RAND) even if the Swagger/OpenAPI specification does not mark the parameter as mandatory?

    • Is there any additional documentation or guideline that explains how to handle such discrepancies between the conformance profile and the OpenAPI specification?

    Your guidance will help us apply the conformance activity correctly and consistently.

    Thank you for your support.



    ------------------------------
    Mohamed Gamal
    Qeema Consultancy and Technology Service
    ------------------------------