System and methods for defining a binding for web-services

• US 20040205765A1
• Filed: 02/28/2003
• Published: 10/14/2004
• Est. Priority Date: 02/28/2003
• Status: Active Grant

• Current Assignee: Valtrus Innovations Limited (f/k/a Dolya Holdco 9 Limited) (Key Patent Innovations Limited)
• Original Assignee: Hewlett-Packard Development Company, L.P. (HP Inc.)
• Inventors: Vambenepe, Guillaume, Beringer, Dorothea
• Granted Patent: US 7,577,964 B2
• Time in Patent Office: Days
• US Class Current: 719/311
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]

Abstract

In accordance with an embodiment of the present invention, a web-services interface for a web-service comprises a message binding extension element operable to specify a format for a message requesting the web-service and a binding details extension element operable to specify an availability status of at least one receipt for the message.

Claims

1. A web-services interface for a web-service, comprising:

a message binding extension element operable to specify a format for a message requesting said web-service; and

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

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

3. The web-services interface of claim 1, further comprising a transport extension attribute operable to specify a transport protocol for transmitting said message.

4. The web-services interface 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 interface of claim 1, wherein said message comprises a request for said at least one receipt.

6. The web-services interface 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 interface 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 interface 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 interface of claim 1, further comprising a packaging extension attribute operable to specify a packaging type for packaging said message.

10. The web-services interface of claim 1, further comprising 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 interface of claim 1, further comprising a packaging extension attribute operable to specify that said message is part of a multipart message.

12. The web-services interface of claim 1, further comprising 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 interface of claim 1, further comprising 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 interface of claim 1, further comprising 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 interface of claim 1, further comprising 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 interface of claim 1, further comprising:

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 interface of claim 1, further comprising 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 interface of claim 1, further comprising:

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 interface for a web-service, comprising:

a binding details extension element operable to specify an availability status of at least one receipt for a message 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.

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

21. A method for defining a web-service, comprising:

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

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

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, further 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; 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:

determining whether a web-services interface requires said web-services message to include a delivery receipt request; and

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:

determining whether a web-services interface prohibits a delivery receipt 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 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.