Hi
The Open API team is working on republishing all the Open API specs and swaggers, this effort started with R18.5 with Service-related APIs, continued in R19.0 with Product and other areas, and is ongoing. It is possible that Resource Inventory (TMF 639) will be republished in R19.5 timescale but no promises.
In this republishing, we are guaranteeing alignment between spec (pdf) and swagger by generation of both assets from a common schema. Also we have eliminated the Admin/regular distinction, since we recognize in real life that authorization is more complex than this - generally role-based and handled outside the API provider (e.g. by an API gateway).
While waiting for TMF 639, I suggest you take a look at recently-published swagger files from other APIs in R19.0
here and see if your concerns are addressed.
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.
------------------------------
Original Message:
Sent: Oct 31, 2019 08:57
From: Anaswara Wilfred
Subject: TMF639 - Resource Type Clarification
As per TMF639_Resource_Inventory_Management_REST_API_Specification_R17.0.1, we have a resource model from which physical and logical is derived out. Create/Delete resource type API available only to ADMIN users seems to be working on resource model based on understanding. But could not find a corresponding resource class in generated model folder using swagger. Resource API controller seems to be written with inbuilt org.springframework.core.io.Resource class which does not have all fields mentioned in API spec document. Kindly clarify on this.
------------------------------
Anaswara Wilfred
Infosys
------------------------------