Hi Andres,
If you don't find an appropriate placeholder in the TMF Original object, then you can extend the model to include additional properties.
ExtendedAddress:
title: ExtendedAddress
allOf: # Combines the main `Address` schema with `ExtendedAddress`-specific properties
- $ref: '#/definition/Address'
- type: object
# all other properties specific to your `ExtendedAddress`
properties:
neighborhood:
type: string
block:
type: string
staircase:
type: string
Then you can give a reference to your extended model as below:
"@baseType": "Address",
"@schemaLocation": "https://{openapidocument_location}#//definition/Address",
"@type": "ExtendedAddress"
Note: This is an opinion based on my research and not an official TMF response.
------------------------------
Aneesh Damodaran
BT Group plc
------------------------------
Original Message:
Sent: Jun 02, 2021 17:05
From: Andrés Contona
Subject: TMF647 Address API REST Specification R16.0.1
Hello All, I found that in this specification a "street" type address format is mentioned, this being one of the many possible ones. At least in my country there are many other formats where the determinant is not the street but another group of variables, for example: neighborhood, block, building, staircase, door (just to mention a possible variant of the "n" that there are and keep appearing). I can't imagine how to solve that with this API.
------------------------------
Andrés Contona
Telefonica Moviles Argentina
------------------------------