Open APIs

Expand all | Collapse all

TMF - 645 CTK

  • 1.  TMF - 645 CTK

    TM Forum Member
    Posted 25 days ago
    I noticed that recently a new TMF 645 specification version has been released.
    However, I'm having trouble to find it the related CTK tests.
    Under the Open API Table link (Open API Table) we still see reference to older
    Also searched under gitHub and no success.
    Only able to GET the specification (TMF645) and, conformance profile (TMF645B)

    Marcos Donato da Silva
    Ericsson Inc.

  • 2.  RE: TMF - 645 CTK

    TM Forum Member
    Posted 22 days ago
    Hello Marcos,
    Links to the latest Swagger, User Guide and Conformance Profile for TMF645 can be found in the Open API Table - Early Adoption (Beta) page. The CTK will be added as soon as it has been completed and approved.

    Alan Pope
    Collaboration Manager
    TM Forum
    United Kingdom

  • 3.  RE: TMF - 645 CTK

    TM Forum Member
    Posted 20 days ago
    Thanks Alan,

    I have a doubt here:

    We're planning to implement TMF645 but now, it came a doubt around which version to use:

    * When we google for TMF645, we're redirected to the version 4.0.1 as the production one.
    * When we go for the Open-API table, we see that we're redirected to the previous version (18.5.1)
    * When we go to the Open-API Early Adoption page, we see that 4.0.1 but, it is pointed as pre-production.

    The current approach is to go for the 4.0.1 (despite not having the CTK tests yet) but, is this the
    actual forum recommendation?

    Marcos Donato da Silva
    Ericsson Inc.

  • 4.  RE: TMF - 645 CTK

    TM Forum Member
    Posted 19 days ago
    To clarify - the Open API team policy is that APIs are posted to the main Open API table only when all the assets are available for an API. During the interim period, the assets (user guide, swagger, CTK, etc.) are posted to the early adoption table.

    Items in the early adoption table have been approved internally by the Open API team, and are unlikely to be changed but it is a possibility (e.g. due to the TMF formal member review process).

    I urge you access assets via the API table (main or early adoption), and not directly via search, GitHub, etc.

    Also, please note that denotations such as 18.5, 19.5, 20.0, etc. are not API versions, but rather reflect the TMF global du-yearly release cycle. The actual API version, represented by the "version" string within the swagger file, will be 4.0.0 (for most of the recently published APIs), or maybe 1.0, 2.0, etc. for older APIs.

    Jonathan Goldberg
    Amdocs Management Limited
    Any opinions and statements made by me on this forum are purely personal, and do not necessarily reflect the position of the TM Forum or my employer.