Open APIs

Hi all,

My question is around the geographicAddressValidation entity, Im not sure would be the difference in creating an address in a master system or making a validation of an address to the same.
Lets say that an address is provided to be validated, but that address is not existing in the address master system. Then there is a process to verify whether this address is valid, giving back to the consumer an Id (this would be the validation entity) . Once the address is validated, through a notification the consumer gets updated the status to "Verified"... But what would happen to the new address created in the master system? how can the master system reply with the new geographicAddress ID? the consumer does not really care about the validation Id... but yes to the address Id.

I would also like to ask which will be the best way of customising address formats for different countries... the definition provided is very generic but to adhere to a country specific, many changes would be needed. Should we extend the definition based on different schemas per country? How would we refer to each different definition, through the @Type=''countryAddress" and @subType="Portugal" for example?

Thank you all for your thoughts!

Hello

I am not sure I fully understand the question put will give my view as to how address validation could work.

One creates a validation request with as much of the address details as one has and asynchronously one of three things I believe can happen.

The "validation" fails and no new geographic address is created.

The "validation" works but finds a suitable alternative or even fuller address that  can be returned using alternativeGeographicAddress or 

Hi all,

My question is around the geographicAddressValidation entity, Im not sure would be the difference in creating an address in a master system or making a validation of an address to the same.
Lets say that an address is provided to be validated, but that address is not existing in the address master system. Then there is a process to verify whether this address is valid, giving back to the consumer an Id (this would be the validation entity) . Once the address is validated, through a notification the consumer gets updated the status to "Verified"... But what would happen to the new address created in the master system? how can the master system reply with the new geographicAddress ID? the consumer does not really care about the validation Id... but yes to the address Id.

I would also like to ask which will be the best way of customising address formats for different countries... the definition provided is very generic but to adhere to a country specific, many changes would be needed. Should we extend the definition based on different schemas per country? How would we refer to each different definition, through the @Type=''countryAddress" and @subType="Portugal" for example?

Thank you all for your thoughts!

Thanks Derrick, this paragraph replies to my question:

"We have a similar process but we allow "temporary" suggested addresses to be created in the master database with a usable id which can be used for product orders. During order fulfilment, the temporary address is validated by us and either accepted and in effect promoted in value or replaced with a suitable alternative"
But in any case, we would only use the addressvalidation endpoint to initially create a new address in the master system. The validateAddress service will give back the validation Id (which would have an status like "pending validation" and the new temporary address ID created in the master. Once the address is verified, the address will have a verified status, and the consumer could be notified on this status change, but through the addressValidation event resource.- The consumer will then update accordingly the local address record based on this response...

Sorry if my wording is not the most comprehensive...

Hello

I am not sure I fully understand the question put will give my view as to how address validation could work.

One creates a validation request with as much of the address details as one has and asynchronously one of three things I believe can happen.

The "validation" fails and no new geographic address is created.

The "validation" works but finds a suitable alternative or even fuller address that  can be returned using alternativeGeographicAddress or 

Hi all,

My question is around the geographicAddressValidation entity, Im not sure would be the difference in creating an address in a master system or making a validation of an address to the same.
Lets say that an address is provided to be validated, but that address is not existing in the address master system. Then there is a process to verify whether this address is valid, giving back to the consumer an Id (this would be the validation entity) . Once the address is validated, through a notification the consumer gets updated the status to "Verified"... But what would happen to the new address created in the master system? how can the master system reply with the new geographicAddress ID? the consumer does not really care about the validation Id... but yes to the address Id.

I would also like to ask which will be the best way of customising address formats for different countries... the definition provided is very generic but to adhere to a country specific, many changes would be needed. Should we extend the definition based on different schemas per country? How would we refer to each different definition, through the @Type=''countryAddress" and @subType="Portugal" for example?

Thank you all for your thoughts!

Hi all,

My question is around the geographicAddressValidation entity, Im not sure would be the difference in creating an address in a master system or making a validation of an address to the same.
Lets say that an address is provided to be validated, but that address is not existing in the address master system. Then there is a process to verify whether this address is valid, giving back to the consumer an Id (this would be the validation entity) . Once the address is validated, through a notification the consumer gets updated the status to "Verified"... But what would happen to the new address created in the master system? how can the master system reply with the new geographicAddress ID? the consumer does not really care about the validation Id... but yes to the address Id.

I would also like to ask which will be the best way of customising address formats for different countries... the definition provided is very generic but to adhere to a country specific, many changes would be needed. Should we extend the definition based on different schemas per country? How would we refer to each different definition, through the @Type=''countryAddress" and @subType="Portugal" for example?

Thank you all for your thoughts!

This of course depends on countries. but many countries have national address registry. When customer use the address form on the web, each address field is validated. Using prediction (you type the first letter of the street name, city... and we suggest the rest of the word) helps avoid bad address data.

using a interactive map can also help.

when we set up new fiber network in area that don't have yet an address, we create temporary ones. but this does not involve communications with a customer. it's done manually  in BSS.

Hi all,

My question is around the geographicAddressValidation entity, Im not sure would be the difference in creating an address in a master system or making a validation of an address to the same.
Lets say that an address is provided to be validated, but that address is not existing in the address master system. Then there is a process to verify whether this address is valid, giving back to the consumer an Id (this would be the validation entity) . Once the address is validated, through a notification the consumer gets updated the status to "Verified"... But what would happen to the new address created in the master system? how can the master system reply with the new geographicAddress ID? the consumer does not really care about the validation Id... but yes to the address Id.

I would also like to ask which will be the best way of customising address formats for different countries... the definition provided is very generic but to adhere to a country specific, many changes would be needed. Should we extend the definition based on different schemas per country? How would we refer to each different definition, through the @Type=''countryAddress" and @subType="Portugal" for example?

Thank you all for your thoughts!