Generating event data display code

• US 8,290,980 B2
• Filed: 09/08/2006
• Issued: 10/16/2012
• Est. Priority Date: 09/08/2006
• Status: Active Grant

• Current Assignee: R2 Solutions LLC (Acacia Research Corporation)
• Original Assignee: Yahoo! Inc. (Apollo Global Management, Inc.)
• Inventors: Baio, Andrew, Luk, Gordon, Lin, Leonard H.
• Primary Examiner(s): Kerzhner, Aleksandr
• Application Number:
  US11/517,971
• Publication Number:
  US 20080065599A1
• Time in Patent Office: 2,230 Days
• Field of Search: 707/783, 707/999.01
• US Class Current: 707/783
• CPC Class Codes: G06F 16/958 Organisation or management of web site content, e.g. publishing, maintaining pages or automatic linking
• CPC Class Codes: G06Q 30/02 Marketing; Price estimation or determination; Fundraising

Abstract

Techniques for republishing event data are provided. An event data repository contains event records defining real world events. Users request instructions for republishing event data. The request includes data identifying a set of event data and display characteristics for republication. In response to the request, event data display code is provided back to the client. The user may use the event data display code to display event data on the user'"'"'s own web pages or applications. When the event data display code is processed by a web browser application, a request is sent to the events repository, which provides the identified set of event data in response. The event data is displayed to users at the web browser using the display characteristics specified by the client.

Claims

1. A computer-implemented method comprising:

receiving, from a client over a network, first data that identifies event data stored in a repository, wherein the event data stored in the repository reflects one or more real world events;

receiving, from the client over the network, second data that identifies one or more display characteristics for the event data, wherein the one or more display characteristics indicate the manner in which the event data is to be displayed at the client;

receiving, from the client over the network, a request for event data display code for retrieving the event data from the repository and displaying the event data on a graphical user interface in the manner specified by the second data, wherein the event data display code includes a request to retrieve the event data from the repository; and

in response to the request for the event data display code, generating and providing to the client over the network, a first Web page that includes the event data display code, wherein a first Web browser rendering the first Web page does not cause the request to retrieve the event data from the repository to be issued and wherein when the event data display code is included in a second Web page and rendered by a second Web browser the request to retrieve the event data from the repository is issued.

2. The method of claim 1, wherein the event data stored in said repository indicates whether a particular event record has been marked of interest by the client.

3. The method of claim 2, wherein the event data identified by the first data includes any event record that has been marked of interest by the client.

4. The method of claim 1, wherein the event data stored in the repository indicates whether the client may republish a particular event record stored in said repository.

5. The method of claim 4, wherein the event data identified by the first data includes any event record that the client is allowed to republish.

6. The method of claim 1, wherein the one or more display characteristics further identify one or more data fields of the event data to display on a graphical user interface when the event data display code is processed.

7. The method of claim 1, wherein the one or more display characteristics further identify the amount of event data to display on a graphical user interface when the event data display code is processed.

8. The method of claim 1, wherein the one or more display characteristics further identify the color, size and style for displaying the event data on a graphical user interface when the event data display code is processed.

9. The method of claim 1, wherein the event data display code includes user-authentication information for accessing the repository.

10. The method of claim 1, wherein the event data display code is provided as Javascript commands embedded within Hypertext Transfer Markup Language (HTML) instructions.

11. The method of claim 1, wherein the event data display code is provided in any type of computer-readable instruction language.

12. The method of claim 1, wherein the second Web browser is different than the first Web browser.

13. The method of claim 1, wherein, in response to the request to retrieve the event data from the repository, the repository transmits the event data to the second Web browser.

14. A computer readable medium carrying instructions which, when processed by one or more processors, causes:

receiving, from a client over a network, first data that identifies event data stored in a repository, wherein the event data stored in the repository reflects one or more real world events;

receiving, from the client over the network, second data that identifies one or more display characteristics for the event data, wherein the one or more display characteristics indicate the manner in which the event data is to be displayed at the client;

receiving, from the client over the network, a request for event data display code for retrieving the event data from the repository and displaying the event data on a graphical user interface in the manner specified by the second data, wherein the event data display code includes a request to retrieve the event data from the repository; and

in response to the request for the event data display code, generating and providing to the client over the network, a first Web page that includes the event data display code, wherein a first Web browser rendering the first Web page does not cause the request to retrieve the event data from the repository to be issued and wherein when the event data display code is included in a second Web page and rendered by a second Web browser the request to retrieve the event data from the repository is issued.

15. The computer-readable medium of claim 14, wherein the event data stored in said repository indicates whether a particular event record has been marked of interest by the client.

16. The computer-readable medium of claim 15, wherein the event data identified by the first data includes any event record that has been marked of interest by the client.

17. The computer-readable medium of claim 14, wherein the event data stored in the repository indicates whether the client may republish a particular event record stored in said repository.

18. The computer-readable medium of claim 17, wherein the event data identified by the first data includes any event record that the client is allowed to republish.

19. The computer-readable medium of claim 14, wherein the one or more display characteristics further identify one or more data fields of the event data to display on a graphical user interface when the event data display code is processed.

20. The computer-readable medium of claim 14, wherein the one or more display characteristics further identify the amount of event data to display on a graphical user interface when the event data display code is processed.

21. The computer-readable medium of claim 14, wherein the one or more display characteristics further identify the color, size and style for displaying the event data on a graphical user interface when the event data display code is processed.

22. The computer-readable medium of claim 14, wherein the event data display code includes user-authentication information for accessing the repository.

23. The computer-readable medium of claim 14, wherein the event data display code is provided as Javascript commands embedded within Hypertext Transfer Markup Language (HTML) instructions.

24. The computer-readable medium of claim 14, wherein the event data display code is provided in any type of computer-readable instruction language.

25. The computer-readable medium of claim 14, wherein the second Web browser is different than the first Web browser.

26. The computer-readable medium of claim 14, wherein, in response to the request to retrieve the event data from the repository, the repository transmits the event data to the second Web browser.

27. An apparatus, comprising:

a memory storing instructions which, when processed by one or more processors, causes;

receiving, from a client over a network, first data that identifies event data stored in a repository, wherein the event data stored in the repository reflects one or more real world events;

receiving, from the client over the network, second data that identifies one or more display characteristics for the event data, wherein the one or more display characteristics indicate the manner in which the event data is to be displayed at the client;

receiving, from the client over the network, a request for event data display code for retrieving the event data from the repository and displaying the event data on a graphical user interface in the manner specified by the second data, wherein the event data display code includes a request to retrieve the event data from the repository; and

in response to the request for the event data display code, generating and providing to the client over the network, a first Web page that includes the event data display code, wherein a first Web browser rendering the first Web page does not cause the request to retrieve the event data from the repository to be issued and wherein when the event data display code is included in a second Web page and rendered by a second Web browser the request to retrieve the event data from the repository is issued.

28. The apparatus of claim 27, wherein the event data stored in said repository indicates whether a particular event record has been marked of interest by the client.

29. The apparatus of claim 28, wherein the event data identified by the first data includes any event record that has been marked of interest by the client.

30. The apparatus of claim 27, wherein the event data stored in the repository indicates whether the client may republish a particular event record stored in said repository.

31. The apparatus of claim 30, wherein the event data identified by the first data includes any event record that the client is allowed to republish.

32. The apparatus of claim 27, wherein the one or more display characteristics further identify one or more data fields of the event data to display on a graphical user interface when the event data display code is processed.

33. The apparatus of claim 27, wherein the one or more display characteristics further identify the amount of event data to display on a graphical user interface when the event data display code is processed.

34. The apparatus of claim 27, wherein the one or more display characteristics further identify the color, size and style for displaying the event data on a graphical user interface when the event data display code is processed.

35. The apparatus of claim 27, wherein the event data display code includes user-authentication information for accessing the repository.

36. The apparatus of claim 27, wherein the event data display code is provided as Javascript commands embedded within Hypertext Transfer Markup Language (HTML) instructions.

37. The apparatus of claim 27, wherein the event data display code is provided in any type of computer-readable instruction language.

38. The apparatus of claim 27, wherein the second Web browser is different than the first Web browser.

39. The apparatus of claim 27, wherein, in response to the request to retrieve the event data from the repository, the repository transmits the event data to the second Web browser.