Open APIs

 View Only
Back to discussions
Expand all | Collapse all

TMF717 - Discrepancies in Customer360 V4 Resource Formats Across Spec & OpenAPI

  • 1.  TMF717 - Discrepancies in Customer360 V4 Resource Formats Across Spec & OpenAPI

    TM Forum Member
    Posted 25 days ago

    Hi everyone,

    I'm currently working on implementing the Customer360 Management V4 API (TMF717) and have run into a bit of confusion: the Customer360 resource appears in at least three different forms across TM Forum materials:

    1. Narrative Spec (PDF/HTML) – the tables and diagrams in the guide define one set of fields.

    2. Example Payloads – the sample JSON snippets in the document sometimes include extra attributes.

    3. OpenAPI Specification customer360.yaml – the machine‑readable schema defines yet another structure (with different nesting, additional metadata fields, and sometimes renamed properties).

    Because of these discrepancies, I'm not sure which version to trust as the "canonical" schema for code generation and validation.

    • Is there a single source of truth for Customer360 v4 (or v5) that we should use?

    • Are the differences intentional-e.g., narrative vs. simplified vs. full‑blown schemas-or are some of these simply out of sync?

    • Will there be an upcoming alignment or errata publication to reconcile the variations?

    Any guidance or pointers to an authoritative spec would be greatly appreciated!

    Thanks in advance for your help.



    ------------------------------
    TS Ph
    Singapore Telecommunications Limited
    ------------------------------