Seperating assemblies with web references
I am curious how others would handle this situation.  I have a domain layer that includes an Address object.  I then have an application that uses this object.  Additionally, there is an asp.net asmx web service that performs address validation by going out to a third party web service.

I am curious how to deal with this functionality. I don't want to put the service reference and code to access the web service in the domain layer.  It also seems wrong to put it in the application layer.

My current best solution is to create a third assembly that references the original domain layer AND the validation web service.  This keeps my domain layer a bit cleaner with no external references.  How would you handle this situation?
Seperating assemblies with web references
===

I am curious how others would handle this situation.  I have a domain layer that includes an Address object.  I then have an application that uses this object.  Additionally, there is an asp.net asmx web service that performs address validation by going out to a third party web service.

I am curious how to deal with this functionality. I don't want to put the service reference and code to access the web service in the domain layer.  It also seems wrong to put it in the application layer.

My current best solution is to create a third assembly that references the original domain layer AND the validation web service.  This keeps my domain layer a bit cleaner with no external references.  How would you handle this situation?