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
------------------------------
Original Message:
Sent: Jul 19, 2021 07:36
From: syed javed
Subject: leverage TMF 667 API Spec - which is Archived
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
------------------------------