My personal recommendation would be to hide the TMF Open APIs behind a more consumer focused set of experience APIs. I'm pretty concerned about the idea that major releases could come twice per year - is that going to include version updates? That a very high rate of change for underlying APIs which are already heavyweight...
Also, there are some gaps in the way the current APIs are modeled. Trying to shoe-horn in SID like resource constructs has led to some significant bloat and burden of understanding. At the moment the APIs are very bottom up and therefore not fit for direct use by channels.
You need to provide a layer of tailored abstraction which insulates the client from underlying changes and also provides a more consumer focused experience.
IMHO
------------------------------
Craig Bayley
MuleSoft
------------------------------
Original Message:
Sent: 06-07-2017 12:26
From: Joann O'Brien
Subject: API development
Hi Kai
the APIs created and crowd sourced inside the Forum are intended to be service agnostic. we are also committing to no more than 2 major updates in any one year.
we have created a governance process published in fx 16.5 and there will be further enhancements to the Fx 17 version.
you can view the latest published version here:
GB996 API Governance Practice R16.5.1 - TM Forum
thanks
------------------------------
Joann O'Brien
TM Forum
Original Message:
Sent: 04-17-2017 15:12
From: Kaj Jonasson
Subject: API development
If we create an API today in one place - it will be different in another place, and definitely different a year from now. How will the open API's follow the development of the services they are connecting to?
------------------------------
Kaj Jonasson
Applied BSS
------------------------------