Hi community,
We are now adopting TMF673 on our Address Management System but we are facing some limitations to match it with specific use-cases that we need it for.
In addition to query addresses and validating addresses (aligned with current listed operations), we also need to be able to initiate Address updates, creation and deletion. Following a (external) geographic address verification process, we need to take actions on our Address Management System on use-cases as these ones:
- Address update: a specific street has been renamed or some municipality borders have been reviewed
- Sub-address deletion: a specific appartment is no longer existing as there was an acquisition and aggregation of two different plots.
- Address addition: a new neighbourhood has been born and various streets and numbers need to be added
For this, we need to support additional API operations that enable external systems to initiate these changes into our adopted Address Management System. In some cases, we might initiate an internal process to validate the change but, in some others, raw CRUD operations will be sufficient. However, there are no operations available in the specification to manipulate existing addresses or add new ones.
Wondering if this topic was debated anywhere in past and, if not, I am open for suggestions. For now, our plan is to just extend the API with new Operations (POST/PATCH/DELETE) in Address and SubAddress resource model to support our use-cases.
Regards
------------------------------
Carlos Portela
Deutsche-Glasfaser.de
------------------------------