Hi Stuart
The best way to gauge the focus of the Open API project is to look at the API catalog at
https://projects.tmforum.org/wiki/display/AP/Open+API+Catalog?src=spaceshortcut. You will see that there are indeed APIs related to Service and Resource (and even Alarms) in various states of development and publication.
The Open API data model is a work in progress (thanks
@Mariano Belaunde for his sterling efforts in maintaining this model) that does not necessarily reflect the full scope of the API, since not all contributors are using the model and the toolset.
And if there are areas that you feel are missing, perhaps you could consider contributing.
------------------------------
Jonathan Goldberg
Amdocs Management Limited
------------------------------
Original Message:
Sent: Apr 10, 2018 23:18
From: Stuart Batten
Subject: Data Model
Looking through TMF625_API_Data_Model it is apparent that there has been a heavy focus on exploring Product, Billing and Customer at the expense of Service and Resource. It appears this is further reflected (although to a lesser extent) in the Open API's. Such things as the relationships between service specs and usage specs, service and usage, service and alarms/faults and services and listeners.
The latest versions of the document appear to be 2016 releases. Are there any working documents that show the foundation data structure upon which the API specs are built? Whilst I can see each spec has UML models, these models do not present a connected view that addresses full service perspectives that we need.
------------------------------
Stuart Batten
Telstra Corporation
------------------------------