Open APIs

 View Only
Expand all | Collapse all

leverage TMF 667 API Spec - which is Archived

  • 1.  leverage TMF 667 API Spec - which is Archived

    TM Forum Member
    Posted Jul 19, 2021 07:37

    Hi All,

     

    Currently we want to leverage TMF 667 API Spec

     

    The current production open API table doesn't have it. But in the previous version it is available.

     

    https://projects.tmforum.org/wiki/display/API/Open+API+Table+-+Historic -- Archived Table
    https://projects.tmforum.org/wiki/display/API/Open+API+Table -- Production Table

     

    We found that it is archived, can we use the API's -  if spec is archived and get conformance certification for it?

     

    Thanks,

    Javed



    ------------------------------
    Syed Javed
    Oracle Corporation
    ------------------------------


  • 2.  RE: leverage TMF 667 API Spec - which is Archived

    TM Forum Member
    Posted Jul 19, 2021 14:38
    Hi Syed
    I've referred your query to @Andy Tiller of TM Forum. We're already having a discussion with the Forum regarding their policy for granting certification for older API versions.
    Hope it helps​

    ------------------------------
    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.
    ------------------------------



  • 3.  RE: leverage TMF 667 API Spec - which is Archived

    TM Forum Member
    Posted Jul 19, 2021 15:24
    Hi Javed and Jonathan

    We've recently cleaned up the API Tables.  Older APIs (before v4) have been moved to the Historic Table (except for 656 and 677, which remain in the table temporarily to highlight that a v4 update is expected - see the Pre-production Table).  If an API was previously advertised in the API Table with a full set of assets including a CTK, and has now been moved to the Historic Table with no v4 replacement available, then we will still certify the older API.  This 'almost' applies to 667 (which has a CTK but not a complete set of assets), but we will still certify this one (I just let the team know this decision so they should get back to you with confirmation).

    Going forward, we are working out a policy for certifying v4 APIs when v5 replacements are available.

    Hope this helps.


    Andy

    ------------------------------
    Andy Tiller
    TM Forum
    ------------------------------



  • 4.  RE: leverage TMF 667 API Spec - which is Archived

    TM Forum Member
    Posted Jul 19, 2021 22:04
    thanks Andy and  Jonathan

    ------------------------------
    syed javed
    Oracle Corporation
    ------------------------------



  • 5.  RE: leverage TMF 667 API Spec - which is Archived

    TM Forum Member
    Posted Oct 28, 2021 02:49
    Hi Andy,

    For 667 there is no update available in the Pre-production table. Can you please confirm if we use the Older API's for 667, will they be certified?

    ------------------------------
    Bhavana Aleti
    Oracle Corporation
    ------------------------------



  • 6.  RE: leverage TMF 667 API Spec - which is Archived

    TM Forum Member
    Posted Oct 28, 2021 03:50
    Hi Bhavana,

    Yes, we will continue to offer certification of the pre-4.0 version of 667 in the Historic Table until the end of this year.

    The full certification policy is here.  Regarding 667: "Until the end of 2021 TM Forum will certify pre-v4 APIs shown in the Historic Table which were previously advertised in the Open API Table (Production Table) which have an existing CTK and for which there is no v4+ version available in the Open API Table".  This applies to TMF667 and TMF670.

    Let us know if you have more questions.

    Andy


    ------------------------------
    Andy Tiller
    TM Forum
    ------------------------------



  • 7.  RE: leverage TMF 667 API Spec - which is Archived

    TM Forum Member
    Posted Oct 29, 2021 10:34
    Hi Andy,

    Greetings!

    I am wondering if there is a plan for a replacement spec for TMF667 or any recommendation on which API to use to manage documents.

    Kindly let me know.

    Best Regards,
    Deep

    ------------------------------
    Deepankar Dey
    Oracle Corporation
    ------------------------------



  • 8.  RE: leverage TMF 667 API Spec - which is Archived

    TM Forum Member
    Posted Oct 31, 2021 03:08
    Work on TMF667 is being led by @Steve Harrop, maybe he can share plans.


    ------------------------------
    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.
    ------------------------------



  • 9.  RE: leverage TMF 667 API Spec - which is Archived

    TM Forum Member
    Posted Nov 04, 2021 18:25
    Hi @Bhavana Aleti - I am working on TMF667-Document API right now, with a view to fast-tracking a Document v4.0.0 update. It is one of the few APIs yet to achieve v4 status.
    I would estimate we should have a v4 swagger, conformance profile and CTK within two weeks from now?​

    ------------------------------
    Stephen Harrop
    Integration Architect
    Vodafone Group
    ------------------------------



  • 10.  RE: leverage TMF 667 API Spec - which is Archived

    TM Forum Member
    Posted Jan 03, 2022 04:42
    Hi @Steve Harrop We are  in the process of developing the document management TMF compliant APIs. Do you have any updates on the swagger​?

    ------------------------------
    Panagiotis CHristodoulou
    Amdocs Management Limited
    ------------------------------



  • 11.  RE: leverage TMF 667 API Spec - which is Archived

    TM Forum Member
    Posted Jan 04, 2022 13:24
    Hi @Panagiotis CHristodoulou,

    Just checking the internal status - the v4.0.0 Document swagger is done, and the user-guide is has a round of approval to go through - after that I think the two (swagger and user-guide) would get published in the early-adopter/release table. I will chase internally.

    ------------------------------
    Stephen Harrop
    Integration Architect
    Vodafone Group
    ------------------------------



  • 12.  RE: leverage TMF 667 API Spec - which is Archived

    TM Forum Member
    Posted Jan 05, 2022 08:32
    Hi Again,

    The Document v4.0.0 swagger and user-guide has now been internally approved and is "in the queue" for publication - so it should appear on the early release table any day now.

    ------------------------------
    Stephen Harrop
    Integration Architect
    Vodafone Group
    ------------------------------



  • 13.  RE: leverage TMF 667 API Spec - which is Archived

    TM Forum Member
    Posted Jan 10, 2022 08:56
    Thank you @Stephen Harrop.

    I can see the swagger but not the user guide.​

    ------------------------------
    Panagiotis CHristodoulou
    Amdocs Management Limited
    ------------------------------



  • 14.  RE: leverage TMF 667 API Spec - which is Archived

    TM Forum Member
    Posted Apr 21, 2022 10:32
    Hello @Steve Harrop,
    There is possibly an error publishing the TMF667 Documents API in the main API table. It is published as the Test Case Management API TMF 667.

    ------------------------------
    Paul Stanek
    Suntech S.A.
    ------------------------------



  • 15.  RE: leverage TMF 667 API Spec - which is Archived

    TM Forum Member
    Posted Apr 21, 2022 10:52
    Hi @Paul Stanek

    You're right!

    We discussed this API in a call yesterday to get promoted to the main table.
    I know there is a semi-automated publication process in place, but something must have gone wrong - I will get on it.

    Steve​

    ------------------------------
    Stephen Harrop
    Integration Architect
    Vodafone Group
    ------------------------------



  • 16.  RE: leverage TMF 667 API Spec - which is Archived

    Posted 29 days ago
    Hello @Steve Harrop,

    is publication issue with TMF 667 API is resolved? I still see 667 tagged with Test Case Management.

    Thanks,
    Anshul Srivastava


    ------------------------------
    Anshul Srivastava
    Vodafone India Services Private Limited
    ------------------------------