Hi.
In our system, we're working on a use-case where the user types an address into a single-line input field, and the system should suggest relevant matches dynamically (autocomplete), updating with each keystroke.
TMF673 version 4.0 resource GeographicAddress included a name field, which could potentially enable submitting the full address as a single string. However, in version 5.0, this field has been removed and expects input to be split across multiple fields (streetName, streetNr, city, etc.), which doesn't align well with the typical UX of an autocomplete component.
Validation via POST /geographicAddressValidation also requires structured input, making it difficult to support free-text address search.
Question:
Is there a recommended approach within TMF specifications to support this kind of full-text address search?
------------------------------
Jan Brnka
T-Mobile Czech & Slovak Telekom, a.s.
------------------------------