I imagine that the API designers wanted to treat GeoAddress as read-only, managed in some external GIS (Google Maps, government address registry, or similar). You can of course customize the Open API by adding POST and PATCH operations for actually creating or modifying addresses.
I'm not sure if POST and PATCH will be added in v5.
Specifically for your question about validation, the geo address validation resource is a TASK entity, that allows an address to be validated (by POSTing the resource). The typical use case is when an end user enters address details in some UI, and we need to verify that this address exists, perhaps in a GIS. And maybe doing some fuzzy matching against alternate spellings of street or city names, for example.
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: Jan 08, 2024 03:58
From: Chetan Patel
Subject: TMF673 (Geographic Address Management) and TMF 674 (Geographic Site Management) association question
Hi @Jonathan Goldberg
We are getting only get operations for geographicAddress & geographicSubAddress under TMF673. So where is the POST operation for this objects?
As per our understanding, validation means validate existing data with requested data so here we are not clear about geographicAddressValidation POST operation requirement. If you can brief about geographicAddressValidation POST operation business purpose then it will be very helpful to us.
------------------------------
Chetan Patel
Tech Mahindra Limited
Original Message:
Sent: Oct 06, 2022 09:48
From: Jonathan Goldberg
Subject: TMF673 (Geographic Address Management) and TMF 674 (Geographic Site Management) association question
Hi Rochelle
A GeoSite is some named location (e.g. BT Head Office London, Harrods Knightsbridge, etc.). The site may be related to a customer, or to some other party/party role (e.g. a central office, exchange, etc.). Clearly a GeoSite should have a GeoAddress or a GeoLocation (RelatedPlace in the Open API TMF674).
So I would express the relationship FROM Site TO Address/Location.
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 06, 2022 08:44
From: Rochelle Mazarello
Subject: TMF673 (Geographic Address Management) and TMF 674 (Geographic Site Management) association question
Hi,
Can anyone shed light on the multiplicity between geographicAddress entity and geographicSite please?
I am unable to find this explictly mentioned IN TMF.
My view is 1 Address can have 0-n sites which essentially eans we can store registered addresses without a formal customer Site BUT a Site MUST have a GeographicalAddress.
Regards,
RM
------------------------------
Rochelle Mazarello
BT Group plc
------------------------------