solution logic that can only be accessed via HTTP methods

solution logic accessible via binary RPC protocols

solution logic that has been shaped by service-orientation design principles

solution logic that can be accessed via a published WSDL definition

The WS-I is an industry standards organization that provides basic profiles to help foster interoperability among solutions based on XML and Web services industry standards.

OASIS is an industry standards organization that has developed a number of important technology specifications, including WS-BPEL and UDDI.

The W3C is a standards organization that has developed a number of important technology specifications, including SOAP, WSDL, and WS-Addressing.

The OAS-C is an industry standards organization that has developed a number of important technology specifications, including WS-Security and XML

When using WS-AtomicTransaction, services participating in a transaction vote on the outcome so as to communicate whether the transaction should be rolled back or committed.

When using WS-AtomicTransaction, services participating in a transaction use RPC protocols to communicate transaction results, so as to communicate whether the transaction should be rolled back or committed.

When using WS-AtomicTransaction, services participating in a transaction rely on the use of WS-Policy definitions to confirm the transaction results.

When using WS-AtomicTransaction, services do not actually participate in a transaction. This specification governs intra-service transactions (transactions that

WSDL definition

HTTP definition

XML schema

WS-Policy definition

I built 3 SOAP-based Web services, each of which has its own published WSDL definition. 2 of the WSDL definitions share the same XML schema.

I built 3 XML schemas, two of which are being shared by the same WSDL definition.

I built 3 WSDL definitions and 3 XML schemas. Each WSDL definition is associated with its own XML schema.

All of the above statements make sense.