The subject line says it all really.
TMF632 Party Management defines its' own address format as part of the contactMedium/characteristic block.
E.g.
{"street1" : "22 Acacia Rd",
"street2": "Lower Village",
"postCode": "IP5 3RE",
"city": "Upperton",
"stateOrProvince": "Suffolk"
Why does it not use (by reference or value) the TMF673 Geographic Address Management format? E.g. same data as above, different format:
{"streetNr": "22","streetName": "Acacia",
"streetType": "Road",
"postcode": "IP5 3RE",
"locality": "Lower Village",
"city": "Upperton",
"stateOrProvince": "Suffolk"}
If we had an address service (exposed using TMF673) it would be natural to create party records that used to the data from the address service rather than (as the API implies) store separate address values in a separate format.
Suggestion: align the postal addresses in TMF632 to the Geographic Address schema of TMF673. Allow pass by reference or pass by value semantics.
------------------------------
Alasdair MacLeod
BT Group plc
------------------------------