Hi Marek
Paging is part of all APIs, as described in the design guidelines TMF630.
POST as against GET, would need discussion since it affects all APIs, not just Document
Not sure I understand your third point about characteristics, can you give a concrete use case with specific example.
Your fourth point needs further discussion within the Open API team.
Thanks for bringing this to our attention.
------------------------------
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: Mar 08, 2021 10:52
From: Marek Niewiadomski
Subject: TMF667 Document Management API - refreshment?
Hi,
Do you think is it possible to refresh a bit TMF667 Document Management API?
- paging with offset, limit, to solve potential timeout issues,
- POST in place of GET for document searching with document attributes. With GET method all searched attribute values with potential personal data goes to the server logs and are transferred unencrypted which is definitely not GDPR friendly,
- single characteristic.name, characteristic.value limit in GET /document,
- maybe, possibility to POST /document message as a multipart/form-data to enable to include a document into a message.
Maybe you have other points to improve. Maybe I'm wrong and above points are not an issues.
Kind regards
------------------------------
Marek Niewiadomski
Polkomtel S.A. (PLUS)
------------------------------