Methods and apparatus for information hyperchain management for on-demand business collaboration

• US 7,797,381 B2
• Filed: 09/19/2003
• Issued: 09/14/2010
• Est. Priority Date: 09/19/2003
• Status: Expired due to Fees

• Current Assignee: LinkedIn Corporation (Microsoft Corporation)
• Original Assignee: International Business Machines Corporation
• Inventors: Chao, Tian-Jy, Zhang, Liang-Jie, Ye, Yiming, Xu, Jing Min, Sayah, John Youssef, Zuo, Ying Nan, Yang, Shun Xiang
• Primary Examiner(s): Flynn; Nathan
• Assistant Examiner(s): Park; Jeong S
• Application Number:
  US10/665,699
• Publication Number:
  US 20050065903A1
• Time in Patent Office: 2,552 Days
• Field of Search: 709/204, 709/206, 705/1
• US Class Current: 709/204
• CPC Class Codes: G06Q 30/06 Buying, selling or leasing transactions

Abstract

Hyperchain information management techniques are provided for use in applications such as on-demand business collaboration. In accordance with such techniques, a hyperchain annotation methodology is provided. Such an annotation methodology enables interaction between loosely-coupled business processes or interacting partners and business entities. Annotated information components and process components for collaboration may be expressed as links. Further, techniques for realizing an on-demand message exchange, embedded status/state information, flexible collaborative business message exchange patterns, and a collaborative directory are provided.

Claims

1. A method, comprising:

storing, via a computing device, in a directory;

collaborative information;

a plurality of common message data models, each of the common message data models for use in forming annotated messages comprising links and metadata extracted from the collaborative information; and

a plurality of common primitive message exchange sequences, each common primitive message exchange sequence comprising a combination of at least two common message data models, each common primitive message exchange sequence for use in an exchange of a sequence of annotated messages, the plurality of common primitive message exchange sequences comprising a first common primitive message exchange sequence comprising a first and a second common message data model;

initiating, via a computer system configured for on-demand business collaboration, the first common primitive message exchange sequence by forming and sending a first annotated message based on the first common message data model, the first annotated message comprising links and metadata extracted from the collaborative information stored in the directory; and

receiving, in response to the first annotated message, a second annotated message based on the second common message data model.

2. The method of claim 1, where the first common primitive message exchange sequence comprises a request for design common primitive message exchange sequence, and further comprising:

receiving a third annotated message based on a third common message data model, where the first common primitive message exchange sequence further comprises the third common message data model combined with the first and second common message data models;

where the first common message data model comprises a design request common message data model, and the first annotated message comprises a request for design input;

where the second common message data model comprises an acknowledgement common message data model, and the second annotated message comprises an acknowledgement of receipt of the first annotated message; and

where the third common message data model comprises a design acceptance common message data model, and the third annotated message comprises a notice that a recipient of the first annotated message has accepted the request for design input.

3. The method of claim 2, where the first common message data model comprises:

a transaction resource including a link to a sender of the first annotated message, and a link to the recipient of the first annotated message;

a task resource including a link to a task file stored in the directory, and including metadata regarding the task file;

a project resource including a link to a project file stored in the directory, and including metadata regarding the project file; and

a requirements resource including a link to first and second containers, the first container including metadata and a plurality of links to files of a first type stored in the directory, and the second container including metadata and a plurality of links to files of a second type stored in the directory.

4. The method of claim 3 where the first annotated message comprises:

an access control policy, the access control policy requiring proper identity and authorization for the recipient of the first annotated message to access the first annotated message; and

status information to enable tracking of a collaborative process.

5. The method of claim 1, where the plurality of common primitive message exchange sequences further comprises a second common primitive message exchange sequence comprising a third and a fourth common message data model, further comprising:

storing, in the directory, a plurality of common construct message exchange sequences, each common construct message exchange sequence comprising a combination of at least two common primitive message exchange sequences, each common construct message exchange sequence for use in an exchange of sequences of common primitive message exchange sequences, the plurality of common construct message exchange sequences comprising a first common construct message exchange sequence comprising the first and the second common primitive message exchange sequences; and

completing the first common construct message exchange sequence by exchanging a third and a fourth annotated message, the third annotated message being based on the third common message data model, and the fourth annotated message being based on the fourth common message data model.

6. The method of claim 5, where:

the first common construct message exchange sequence comprises a request for design common construct message exchange sequence;

the first common primitive message exchange sequence comprises a request for design input; and

the second common primitive message exchange sequence comprises a submission of a design.

7. The method of claim 5, where:

the first common construct message exchange sequence comprises a request for update common construct message exchange sequence;

the first common primitive message exchange sequence comprises a request for update input; and

the second common primitive message exchange sequence comprises an update submission.

8. The method of claim 5, where:

the first common construct message exchange sequence comprises a request for information common construct message exchange sequence;

the first common primitive message exchange sequence comprises a request for information input; and

the second common primitive message exchange sequence comprises an information submission.

9. The method of claim 5, where the first common message data model comprises:

a transaction resource including a link to a sender of the first annotated message, and a link to a recipient of the first annotated message;

a task resource including a link to a task file stored in the directory, and including metadata regarding the task file;

a project resource including a link to a project file stored in the directory, and including metadata regarding the project file; and

a requirements resource including a link to first and second containers, the first container including metadata and a plurality of links to files of a first type stored in the directory, and the second container including metadata and a plurality of links to files of a second type stored in the directory.

10. The method of claim 9, where the first annotated message comprises:

an access control policy, the access control policy requiring proper identity and authorization for the recipient of the first annotated message to access the first annotated message; and

status information to enable tracking of a collaborative process.

11. The method of claim 1, where the first common message data model comprises:

a transaction resource including a link to a sender of the first annotated message, and a link to a recipient of the first annotated message;

a task resource including a link to a task file stored in the directory, and including metadata regarding the task file;

a project resource including a link to a project file stored in the directory, and including metadata regarding the project file; and

a requirements resource including a link to first and second containers, the first container including metadata and a plurality of links to files of a first type stored in the directory, and the second container including metadata and a plurality of links to files of a second type stored in the directory.

12. The method of claim 11, where the first annotated message comprises:

an access control policy, the access control policy requiring proper identity and authorization for the recipient of the first annotated message to access the first annotated message; and

status information to enable tracking of a collaborative process.

13. A computer program product comprising a computer readable storage medium including a computer readable program, where the computer readable program when executed on a computer causes the computer to:

store in a directory;

collaborative information;

a plurality of common message data models, each of the common message data models for use in forming annotated messages comprising links and metadata extracted from the collaborative information; and

a plurality of common primitive message exchange sequences, each common primitive message exchange sequence comprising a combination of at least two common message data models, each common primitive message exchange sequence for use in an exchange of a sequence of annotated messages, the plurality of common primitive message exchange sequences comprising a first common primitive message exchange sequence comprising a first and a second common message data model;

initiate the first common primitive message exchange sequence by forming and sending a first annotated message based on the first common message data model, the first annotated message comprising links and metadata extracted from the collaborative information stored in the directory; and

receive, in response to the first annotated message, a second annotated message based on the second common message data model.

14. The computer program product of claim 13, where the first common primitive message exchange sequence comprises a request for design common primitive message exchange sequence, and where the computer readable program when executed on the computer further causes the computer to:

receive a third annotated message based on a third common message data model, where the first common primitive message exchange sequence further comprises the third common message data model combined with the first and second common message data models;

where the first common message data model comprises a design request common message data model, and the first annotated message comprises a request for design input;

where the second common message data model comprises an acknowledgement common message data model, and the second annotated message comprises an acknowledgement of receipt of the first annotated message; and

where the third common message data model comprises a design acceptance common message data model, and the third annotated message comprises a notice that a recipient of the first annotated message has accepted the request for design input.

15. The computer program product of claim 14, where the first common message data model comprises:

a transaction resource including a link to a sender of the first annotated message, and a link to the recipient of the first annotated message;

a task resource including a link to a task file stored in the directory, and including metadata regarding the task file;

a project resource including a link to a project file stored in the directory, and including metadata regarding the project file; and

a requirements resource including a link to first and second containers, the first container including metadata and a plurality of links to files of a first type stored in the directory, and the second container including metadata and a plurality of links to files of a second type stored in the directory.

16. The computer program product of claim 15, where the first annotated message comprises:

an access control policy, the access control policy requiring proper identity and authorization for the recipient of the first annotated message to access the first annotated message; and

status information to enable tracking of a collaborative process.

17. The computer program product of claim 13, where the plurality of common primitive message exchange sequences further comprises a second common primitive message exchange sequence comprising a third and a fourth common message data model, and where the computer readable program when executed on the computer further causes the computer to:

store, in the directory, a plurality of common construct message exchange sequences, each common construct message exchange sequence comprising a combination of at least two common primitive message exchange sequences, each common construct message exchange sequence for use in an exchange of sequences of common primitive message exchange sequences, the plurality of common construct message exchange sequences comprising a first common construct message exchange sequence comprising the first and the second common primitive message exchange sequences; and

complete the first common construct message exchange sequence by exchanging a third and a fourth annotated message, the third annotated message being based on the third common message data model, and the fourth annotated message being based on the fourth common message data model.

18. The computer program product of claim 17, where:

the first common construct message exchange sequence comprises a request for design common construct message exchange sequence;

the first common primitive message exchange sequence comprises a request for design input; and

the second common primitive message exchange sequence comprises a submission of a design.

19. The computer program product of claim 17, where:

the first common construct message exchange sequence comprises a request for update common construct message exchange sequence;

the first common primitive message exchange sequence comprises a request for update input; and

the second common primitive message exchange sequence comprises an update submission.

20. The computer program product of claim 17, where:

the first common construct message exchange sequence comprises a request for information common construct message exchange sequence;

the first common primitive message exchange sequence comprises a request for information input; and

the second common primitive message exchange sequence comprises an information submission.

21. The computer program product of claim 17, where the first common message data model comprises:

a transaction resource including a link to a sender of the first annotated message, and a link to a recipient of the first annotated message;

a task resource including a link to a task file stored in the directory, and including metadata regarding the task file;

a project resource including a link to a project file stored in the directory, and including metadata regarding the project file; and

a requirements resource including a link to first and second containers, the first container including metadata and a plurality of links to files of a first type stored in the directory, and the second container including metadata and a plurality of links to files of a second type stored in the directory.

22. The computer program product of claim 21, where the first annotated message comprises:

an access control policy, the access control policy requiring proper identity and authorization for the recipient of the first annotated message to access the first annotated message; and

status information to enable tracking of a collaborative process.

23. The computer program product of claim 13, where the first common message data model comprises:

a transaction resource including a link to a sender of the first annotated message, and a link to a recipient of the first annotated message;

a task resource including a link to a task file stored in the directory, and including metadata regarding the task file;

a project resource including a link to a project file stored in the directory, and including metadata regarding the project file; and

a requirements resource including a link to first and second containers, the first container including metadata and a plurality of links to files of a first type stored in the directory, and the second container including metadata and a plurality of links to files of a second type stored in the directory.

24. The computer program product of claim 23, where the first annotated message comprises:

an access control policy, the access control policy requiring proper identity and authorization for the recipient of the first annotated message to access the first annotated message; and

status information to enable tracking of a collaborative process.

25. A system, comprising:

a memory; and

a processor programmed to;

store in a directory within the memory;

collaborative information;

a plurality of common message data models, each of the common message data models for use in forming annotated messages comprising links and metadata extracted from the collaborative information; and

a plurality of common primitive message exchange sequences, each common primitive message exchange sequence comprising a combination of at least two common message data models, each common primitive message exchange sequence for use in an exchange of a sequence of annotated messages, the plurality of common primitive message exchange sequences comprising a first common primitive message exchange sequence comprising a first and a second common message data model;

initiate the first common primitive message exchange sequence by forming and sending a first annotated message based on the first common message data model, the first annotated message comprising links and metadata extracted from the collaborative information stored in the directory; and

receive, in response to the first annotated message, a second annotated message based on the second common message data model.

26. The system of claim 25, where the first common primitive message exchange sequence comprises a request for design common primitive message exchange sequence, and where the processor is further programmed to:

receive a third annotated message based on a third common message data model, where the first common primitive message exchange sequence further comprises the third common message data model combined with the first and second common message data models;

where the first common message data model comprises a design request common message data model, and the first annotated message comprises a request for design input;

where the second common message data model comprises an acknowledgement common message data model, and the second annotated message comprises an acknowledgement of receipt of the first annotated message; and

where the third common message data model comprises a design acceptance common message data model, and the third annotated message comprises a notice that a recipient of the first annotated message has accepted the request for design input.

27. The system of claim 26, where the first common message data model comprises:

a transaction resource including a link to a sender of the first annotated message, and a link to a recipient of the first annotated message;

a task resource including a link to a task file stored in the directory, and including metadata regarding the task file;

a project resource including a link to a project file stored in the directory, and including metadata regarding the project file; and

a requirements resource including a link to first and second containers, the first container including metadata and a plurality of links to files of a first type stored in the directory, and the second container including metadata and a plurality of links to files of a second type stored in the directory.

28. The system of claim 27, where the first annotated message comprises:

an access control policy, the access control policy requiring proper identity and authorization for the recipient of the first annotated message to access the first annotated message; and

status information to enable tracking of a collaborative process.

29. The system of claim 25, where the plurality of common primitive message exchange sequences further comprises a second common primitive message exchange sequence comprising a third and a fourth common message data model, and where the processor is further programmed to:

store, in the directory, a plurality of common construct message exchange sequences, each common construct message exchange sequence comprising a combination of at least two common primitive message exchange sequences, each common construct message exchange sequence for use in an exchange of sequences of common primitive message exchange sequences, the plurality of common construct message exchange sequences comprising a first common construct message exchange sequence comprising the first and the second common primitive message exchange sequences; and

complete the first common construct message exchange sequence by exchanging a third and a fourth annotated message, the third annotated message being based on the third common message data model, and the fourth annotated message being based on the fourth common message data model.

30. The system of claim 29, where:

the first common construct message exchange sequence comprises a request for design construct message exchange sequence;

the first common primitive message exchange sequence comprises a request for design input; and

the second common primitive message exchange sequence comprises a submission of a design.

31. The system of claim 29, where:

the first common construct message exchange sequence comprises a request for update common construct message exchange sequence;

the first common primitive message exchange sequence comprises a request for update input; and

the second common primitive message exchange sequence comprises an update submission.

32. The system of claim 29, where:

the first common construct message exchange sequence comprises a request for information common construct message exchange sequence;

the first common primitive message exchange sequence comprises a request for information input; and

the second common primitive message exchange sequence comprises an information submission.

33. The system of claim 29, where the first common message data model comprises:

a transaction resource including a link to a sender of the first annotated message, and a link to a recipient of the annotated first message;

a task resource including a link to a task file stored in the directory, and including metadata regarding the task file;

a project resource including a link to a project file stored in the directory, and including metadata regarding the project file; and

a requirements resource including a link to first and second containers, the first container including metadata and a plurality of links to files of a first type stored in the directory, and the second container including metadata and a plurality of links to files of a second type stored in the directory.

34. The system of claim 33, where the first annotated message comprises:

an access control policy, the access control policy requiring proper identity and authorization for the recipient of the first annotated message to access the first annotated message; and

status information to enable tracking of a collaborative process.

35. The system of claim 25, where the first common message data model comprises:

a transaction resource including a link to a sender of the first annotated message, and a link to a recipient of the first annotated message;

a task resource including a link to a task file stored in the directory, and including metadata regarding the task file;

a project resource including a link to a project file stored in the directory, and including metadata regarding the project file; and

a requirements resource including a link to first and second containers, the first container including metadata and a plurality of links to files of a first type stored in the directory, and the second container including metadata and a plurality of links to files of a second type stored in the directory.

36. The system of claim 35, where the first annotated message comprises:

an access control policy, the access control policy requiring proper identity and authorization for the recipient of the first annotated message to access the first annotated message; and

status information to enable tracking of a collaborative process.