BOD specific WSDL fully describes the Web Services Interface and the type of services it offers. The WSDL is considered to be strongly typed.

BOD specific WSDL specifies clearly what is to be sent to the service and what is to be returned.

BOD specific WSDL's are more compatible with existing development tools that generate code from the WSDL. These tools work best when they can describe the full capabilities, and not have to leave pieces to be filled in outside of their framework.

Services using BOD Specific WSDL's do not require additional processing by the SOAP engine to figure out the type of payload being received.

Data Validation of the payload can happen before it reaches the application, as it is validated by the type of content the Web Service expects to receive.

Changes can create backward compatibility issues. If the strongly typed data in the WSDL changes or breaks compatibility, code that depends on the WSDL may need to be regenerated.

Strongly typed interfaces require more logic upfront in the Transport dealing with the payload and parsing of the information. The amount depends on the size and complexity of the payload.

There is a closer tie between the transport and application, potentially requiring closer testing between the two.