System and methods for defining a binding for web-services

1. A web-services provider, comprising:

a web server for hosting web-services provided by the web services provider, the web services provider providing a web-services interface accessible by a web-services requestor over a network, the web-services interface defining:

a message binding extension element operable to specify a format for a message transmitted to the web-services provider by the web-services requestor requesting said web-service; and

a binding details extension element operable to specify an availability status of at least one receipt for said message,

wherein the web server determines whether the message includes a valid delivery receipt request by determining whether the web-services interface requires a delivery receipt request to be included in the message by checking an attribute of the binding details extension element in the web-services interface, and if not, determining whether the web-services interface prohibits the delivery receipt request from being included in the message by checking the attribute.

2. The web-services provider of claim 1 , wherein the web-services interface comprises a commitment receipt details extension element operable to specify details regarding said at least one receipt.

3. The web-services provider of claim 1 , wherein the web-services interface comprises a transport extension attribute operable to specify a transport protocol for transmitting said message.

4. The web-services provider of claim 3 , wherein a value of said transport extension attribute is selected from the group consisting of “http” and “smtp”.

5. The web-services provider of claim 1 , wherein said message comprises a request for said at least one receipt.

6. The web-services provider of claim 1 , wherein said at least one receipt is selected from the group consisting of a delivery receipt and a commitment receipt.

7. The web-services provider of claim 1 , wherein said at least one receipt comprises a delivery receipt operable to indicate acceptance of said message by an intended recipient of said message.

8. The web-services provider of claim 1 , wherein said at least one receipt comprises a commitment receipt operable to indicate a commitment for processing of said message by an intended recipient of said message.

9. The web-services provider of claim 1 , wherein the web-services interface comprises a packaging extension attribute operable to specify a packaging type for packaging said message.

10. The web-services provider of claim 1 , wherein the web-services interface comprises a packaging extension attribute operable to specify that a packaging type for said message is determined by a sender of said message.

11. The web-services provider of claim 1 , wherein the web-services interface comprises a packaging extension attribute operable to specify that said message is part of a multipart message.

12. The web-services provider of claim 1 , wherein the web-services interface comprises a delivery receipt extension attribute operable to specify that said at least one receipt comprises a delivery receipt for indicating acceptance of said message by an intended recipient of said message.

13. The web-services provider of claim 1 , wherein the web services interface comprises a commitment receipt extension attribute operable to specify that said at least one receipt comprises a commitment receipt for indicating a commitment for processing of said message by an intended recipient of said message.

14. The web-services provider of claim 1 , wherein the web-services interface comprises a commitment code extension element operable to specify at least one value for inclusion in a header of said at least one receipt.

15. The web-services provider of claim 1 , wherein the web-services interface comprises a commitment detail extension element operable to specify contents specific to said web-service for inclusion in a header of said at least one receipt.

16. The web-services provider of claim 1 , wherein the web-services interface comprises:

a commitment details type message attribute operable to reference said message; and

a commitment details type parts attribute operable to specify at least one part of said message for inclusion in a header of said at least one receipt.

17. The web-services provider of claim 1 , wherein the web-services interface comprises a commitment body extension element operable to specify contents specific to said web-service in a body of said at least one receipt.

18. The web-services provider of claim 1 , wherein the web-services interface comprises:

a commitment body type message attribute operable to reference said message; and

a commitment body type parts attribute operable to specify at least one part of said message for inclusion in a body of said at least one receipt.

19. A web-services provider, comprising:

a web server for hosting web-services provided by the web services provider, the web services provider providing a web-services interface accessible by a web-services requestor over a network, the web-services interface defining:

a binding details extension element operable to specify an availability status of at least one receipt for a message transmitted to the web-services provider by the web-services requestor requesting said web-service; and

a commitment receipt details extension element operable to specify whether said at least one receipt is one of the group consisting of a delivery receipt and a commitment receipt,

wherein the web server determines whether the message includes a valid delivery receipt request by determining whether the web-services interface requires a delivery receipt request to be included in the message by checking an attribute of the binding details extension element in the web-services interface, and if not, determining whether the web-services interface prohibits the delivery receipt request from being included in the message by checking the attribute.

20. The web-services provider of claim 19 , wherein said message comprises a request for said at least one receipt.

21. A method for defining a web-service, comprising: hosting web-services provided by the web services provider, the web services provider providing a web-services interface accessible by a web-services requestor over a network, the web-services:

specifying a format for a message requesting said web-service;

specifying an availability status of at least one receipt for said message; and

determining whether the message includes a valid delivery receipt request by determining whether the web-service requires a delivery receipt request to be included in the message by checking an attribute of a binding details extension element in the web-services interface, and if not, determining whether the web-service prohibits the delivery receipt request from being included in the message by checking the attribute.

22. The method of claim 21 , further comprising specifying whether said at least one receipt is one of the group consisting of a delivery receipt and a commitment receipt.

23. The method of claim 21 , further comprising specifying a transport

protocol for transmitting said message.

24. The method of claim 21 , further comprising specifying a packaging type for packaging said message.

25. The method of claim 21 , further comprising specifying that a packaging type for said message is determined by a sender of said message.

26. The method of claim 21 , further comprising specifying that said message is part of a multipart message.

27. The method of claim 21 , further comprising specifying that said at least one receipt comprises a delivery receipt for indicating acceptance of said message by an intended recipient of said message.

28. The method of claim 21 , further comprising publishing the specified format.

29. The method of claim 21 , further comprising specifying that said at least one receipt comprises a commitment receipt for indicating a commitment for processing of said message by an intended recipient of said message.

30. The method of claim 21 , thither comprising specifying at least one value for inclusion in a header of said at least one receipt.

31. The method of claim 21 , further comprising specifying contents specific to said web-service for inclusion in a header of said at least one receipt.

32. The method of claim 21 , further comprising:

referencing said message; and

specifying at least one part of said message for inclusion in a header of said at least one receipt.

33. The method of claim 21 , further comprising specifying contents specific to said web-service for inclusion in a body of said at least one receipt.

34. The method of claim 21 , further comprising:

referencing said message; and

specifying at least one part of said message for inclusion in a body of said at least one receipt.

35. A method for providing a web-service, comprising:

determining whether a web-services message is in a specified format;

determining whether said web-services message comprises a valid delivery receipt request by determining whether the web-service requires a delivery receipt request to be included in the web-services message by checking an attribute of a binding details extension element in a web-services interface, and if not, determining whether the web-service prohibits the delivery receipt request from being included in the web-services message by checking the attribute; and

processing said web-services message in response to said web-services message being in said specified format and comprising a valid delivery receipt request.

36. The method of claim 35 , further comprising comparing a process element of said web-services message with a process extension attribute for said web-service listed in a web-services interface to determine whether said web-services message is in said specified format.

37. The method of claim 35 , wherein said determining whether said web-services message comprises a valid delivery receipt request comprises:

processing said web-services message in response to said web-services message including said delivery receipt request and upon determining that said web-services interface requires said web-services message to include said delivery receipt request.

38. The method of claim 35 , wherein said determining whether said web-services message comprises a valid delivery receipt request comprises:

processing said web-services message in response to said web-services message not including said delivery receipt request and upon determining that said web-services interface prohibits said delivery receipt request from being included in said web-services message.

39. The method of claim 35 , further comprising:

determining whether a web-services interface prohibits a delivery commitment request from being included in said web-services message; and

processing said web-services message in response to said web-services message not including said delivery commitment request and upon determining that said web-services interface prohibits said delivery commitment request from being included in said web-services message.

40. The method of claim 35 , further comprising transmitting an error message in response to said web-services message comprising an invalid delivery receipt request.

41. The method of claim 35 , further comprising processing said web-services message in response to said web-services message being packaged in accordance with a packaging format specified in a packaging extension attribute of a web-services interface.

42. A method for providing a web-service, comprising:

receiving a web-services message from a web-services requestor;

determining a value of a delivery receipt extension attribute of a web-services interface published by a web-services provider;

determining whether said web-services message comprises a valid delivery receipt request by determining whether the web-service requires a delivery receipt request to be included in the web-services message by checking an attribute of a binding details extension element in the web-services interface, and if not, determining whether the web-service prohibits the delivery receipt request from being included in the web-services message by checking the attribute;

responsive to determining that the value indicates that a delivery receipt request is prohibited from being included in a web-services message, determining whether the received web-services message includes a delivery receipt request; and

responsive to determining that the received web-services message does not include a delivery receipt request, processing the web-services message.

43. A method for providing a web-service, comprising:

receiving a web-services message from a web-services requestor;

determining a value of a delivery receipt extension attribute of a web-services interface published by a web-services provider;

determining whether said web-services message comprises a valid delivery receipt request by determining whether the web-service requires a delivery receipt request to be included in the web-services message by checking an attribute of a binding details extension element in the web-services interface, and if not, determining whether the web-service prohibits the delivery receipt request from being included in the web-services message by checking the attribute;

responsive to determining that the value indicates that a delivery receipt request is required in a web-services message, determining whether the received web-services message includes a delivery receipt request; and

responsive to determining that the received web-services message includes a delivery receipt request, processing the web-services message.

44. A web-services server having software residing thereon, the software, when executed by the web-services server, causes the web-services server to:

in response to receiving a web-services message from a web-services requestor, determine a value of a delivery receipt extension attribute of a web-services interface published by a web-services provider;

determine whether said web-services message comprises a valid delivery receipt request by determining whether the web-service requires a delivery receipt request to be included in the web-services message by checking an attribute of a binding details extension element in the web-services interface, and if not, determining whether the web-service prohibits the delivery receipt request from being included in the web-services message by checking the attribute;

in response to determining that the value indicates that a delivery receipt request is required in a web-services message, determine whether the received web-services message includes a delivery receipt request; and

in response to determining that the received web-services message includes a delivery receipt request, process the web-services message.