Republishing group event data

• US 20080065740A1
• Filed: 09/08/2006
• Published: 03/13/2008
• Est. Priority Date: 09/08/2006
• Status: Abandoned Application

• Current Assignee: Oath Inc. (Verizon Communications Inc.)
• Original Assignee: Oath Inc. (Verizon Communications Inc.)
• Inventors: Baio, Andrew, Lin, Leonard H., Luk, Gordon
• Application Number:
  US11/517,972
• Publication Number:
  US 20080065740A1
• Time in Patent Office: Days
• US Class Current: 709/217
• 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 group event data. The request includes data identifying a set of group 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 group 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 group event data in response. The group 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 a user-group, wherein the user-group is associated with one or more sets of event data in a repository, and 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 display characteristics indicate the manner in which the event data is to be displayed;

receiving, from the client over the network, a request for a set of one or more instructions which, when processed, causes the set of event data to be displayed on a graphical user interface in the manner specified by the third data;

in response to the request, generating and providing the set of one or more instructions to the client over the network.

3. The method of claim 1, wherein the event data stored in the repository indicates whether the client may republish events associated with a particular user-group.

4. The method of claim 3, wherein the client is allowed to republish events associated with a particular user-group if the client is a member of the particular user-group.

5. The method of claim 1, wherein the display characteristics further identify one or more data fields of the event data to display on a graphical user interface when said instructions are processed.

6. The method of claim 1, wherein the display characteristics further identify the amount of event data to display on a graphical user interface when said instructions are processed.

7. The method of claim 1, wherein the display characteristics further identify the color, size and style for displaying the event data on a graphical user interface when said instructions are processed.

8. The method of claim 1, wherein the set of one or more instructions include a request to access the events repository,

9. The method of claim 8, wherein the one or more instructions further include user-authentication information for accessing the events repository.

10. The method of claim 1, wherein the set of one or more instructions are provided as Javascript commands embedded within Hypertext Transfer Markup Language (HTML) instructions.

11. The method of claim 1, wherein the set of one or more instructions are provided in any type of computer-readable instruction language.

12. The method of claim 1, wherein the code is executed by a web browser application, and wherein executing the code causes the one or more events represented by the data to be displayed on a graphical user interface.

13. The method of claim 12, wherein, in response to executing the code, a request for the set of event data is sent to the events repository.

14. The method of claim 13, wherein, in response to the request, the events repository transmits the set of event data to the web browser application.

2. The method of claim 2, wherein the user-group identified by the first data is associated with one or more sets of event data having one or more common characteristics.

15. 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 a user-group, wherein the user-group is associated with one or more sets of event data in a repository, and 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 display characteristics indicate the manner in which the event data is to be displayed;

receiving, from the client over the network, a request for a set of one or more instructions which, when processed, causes the set of event data to be displayed on a graphical user interface in the manner specified by the third data;

in response to the request, generating and providing the set of one or more instructions to the client over the network.

16. The computer-readable medium of claim 15, wherein the user-group identified by the first data is associated with one or more sets of event data having one or more common characteristics.

17. The computer-readable medium of claim 15, wherein the event data stored in the repository indicates whether the client may republish events associated with a particular user-group.

18. The computer-readable medium of claim 17, wherein the client is allowed to republish events associated with a particular user-group if the client is a member of the particular user-group.

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

20. The computer-readable medium of claim 15, wherein the display characteristics further identify the amount of event data to display on a graphical user interface when said instructions are processed.

21. The computer-readable medium of claim 15, wherein the display characteristics further identify the color, size and style for displaying the event data on a graphical user interface when said instructions are processed.

22. The computer-readable medium of claim 15, wherein the set of one or more instructions include a request to access the events repository,

23. The computer-readable medium of claim 22, wherein the one or more instructions further include user-authentication information for accessing the events repository.

24. The computer-readable medium of claim 15, wherein the set of one or more instructions are provided as Javascript commands embedded within Hypertext Transfer Markup Language (HTML) instructions.

25. The computer-readable medium of claim 15, wherein the set of one or more instructions are provided in any type of computer-readable instruction language.

26. The computer-readable medium of claim 15, wherein the code is executed by a web browser application, and wherein executing the code causes the one or more events represented by the data to be displayed on a graphical user interface.

27. The computer-readable medium of claim 26, wherein, in response to executing the code, a request for the set of event data is sent to the events repository.

28. The computer-readable medium of claim 27, wherein, in response to the request, the events repository transmits the set of event data to the web browser application.

29. An apparatus, comprising:

means for receiving, from a client over a network, first data that identifies a user-group, wherein the user-group is associated with one or more sets of event data in a repository, and wherein the event data stored in the repository reflects one or more real world events;

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

means for receiving, from the client over the network, a request for a set of one or more instructions which, when processed, causes the set of event data to be displayed on a graphical user interface in the manner specified by the third data;

means for, in response to the request, generating and providing the set of one or more instructions to the client over the network.

30. The apparatus of claim 29, wherein the user-group identified by the first data is associated with one or more sets of event data having one or more common characteristics.

31. The apparatus of claim 29, wherein the event data stored in the repository indicates whether the client may republish events associated with a particular user-group.

32. The apparatus of claim 31, wherein the client is allowed to republish events associated with a particular user-group if the client is a member of the particular user-group.

33. The apparatus of claim 29, wherein the display characteristics further identify one or more data fields of the event data to display on a graphical user interface when said instructions are processed.

34. The apparatus of claim 29, wherein the display characteristics further identify the amount of event data to display on a graphical user interface when said instructions are processed.

35. The apparatus of claim 29, wherein the display characteristics further identify the color, size and style for displaying the event data on a graphical user interface when said instructions are processed.

36. The apparatus of claim 29, wherein the set of one or more instructions include a request to access the events repository,

37. The apparatus of claim 36, wherein the one or more instructions further include user-authentication information for accessing the events repository.

38. The apparatus of claim 29, wherein the set of one or more instructions are provided as Javascript commands embedded within Hypertext Transfer Markup Language (HTML) instructions.

39. The apparatus of claim 29, wherein the set of one or more instructions are provided in any type of computer-readable instruction language.

40. The apparatus of claim 29, wherein the code is executed by a web browser application, and wherein executing the code causes the one or more events represented by the data to be displayed on a graphical user interface.

41. The apparatus of claim 40, wherein, in response to executing the code, a request for the set of event data is sent to the events repository.

42. The apparatus of claim 41, wherein, in response to the request, the events repository transmits the set of event data to the web browser application.