Application Service

In a SOA sense, a service can serve many applications (front ends). In a DDD sense, an application (presentation layer) interacts with the application service layer to execute domain behavior.
 

 While there's slight variation in terminology from the two perspectives the associations between application and presentation layer typically seem to align as the front-end facing layer of a software solution.
 

 So to the question...
 Is it fair to say that there can be many DDD application services standing in front of a domain model, each servicing a specific application?
 

 If the application service itself was physically implemented as a web service is it more common to see a single application (web) service serve multiple application front-ends? Or Is it more common for there to be a one-to-one relationship between the application and the application (web) service?
 

 Thinking about it I'd tend to think the Api exposed by an application service could vary depending on the needs of the specific application it services and not all that uncommon to have a one-to-one relationship (even if application service is physically a web service).
 

 Thoughts?