Customized container document modules using preferences

• US 20070136201A1
• Filed: 12/12/2005
• Published: 06/14/2007
• Est. Priority Date: 12/12/2005
• Status: Abandoned Application

• Current Assignee: Google Inc. (Alphabet Inc.)
• Original Assignee: Google Inc. (Alphabet Inc.)
• Inventors: Sah, Adam, Rohrs, Christopher, Parker, Dylan, Goldberg, Steven
• Application Number:
  US11/298,987
• Publication Number:
  US 20070136201A1
• Time in Patent Office: Days
• US Class Current: 705/51
• CPC Class Codes: G06Q 99/00 Subject matter not provided for in other groups of this subclass

Abstract

Accordingly, various exemplary embodiments of the present inventions may be directed to a method comprising storing preference information for a user related to a module for use with a container document, transmitting the preference information with a request for data related to the module and receiving module data customized based on the preference information.

Claims

1. A method comprising:

storing preference information for a user related to one or more modules for use with a container document;

transmitting the preference information with a request for data related to the module; and

receiving module data customized based on the preference information.

2. The method of claim 1 wherein preference information is stored for a subset of module of a user separate from other preference information for other modules for that user.

3. The method of claim 2 wherein the subset comprises a single module.

4. The method of claim 2 wherein preference information is stored separately for each module for a user.

5. The method of claim 1 wherein the preference information is transmitted over the Internet to a remote module specification server.

6. The method of claim 5 wherein the remote module specification server uses the preference information to provide module data for use in the container document.

7. The method of claim 1 further comprising the act of displaying the customized module data in the container document.

8. The method of claim 1 wherein the preference information is transmitted as part of an Internet resource request.

9. The method of claim 1 wherein the preference information is transmitted as part of a URL used to transmit the request.

10. The method of claim 1 wherein the preferences for a module are stored in association with a location reference of a module.

11. The method of claim 1 wherein the customized module data customizes the content of the module data.

12. The method of claim 1 wherein the customized module data customizes the appearance of the module data for presentation in the container document.

13. The method of claim 1 further comprising the act of enabling a user to modify, add or delete one or more preferences stored.

14. The method of claim 13 wherein the user may modify a preference for that user.

15. The method of claim 13 wherein the user may modify a preference for another user.

16. The method of claim 13 further comprising the act of verifying user right to modify a preference.

17. The method of claim 16 wherein the act of verifying involves use of a digital certificate.

18. The method of claim 16 wherein the act of verifying involves use of a token.

19. The method of claim 18 wherein the token comprises a time element.

20. The method of claim 16 wherein the token is used to determine whether the user has the right to modify, add or delete a preference.

21. The method of claim 1 wherein each user is allotted a certain amount of storage for preferences.

22. The method of claim 1 wherein the preferences are stored at an Internet location remote from a server that serves the container document.

23. The method of claim 1 wherein the preferences are stored at an Internet location remote from the location where the code for the module is stored.

24. The method of claim 1 further comprising transmitting preference information for a user to another system.

25. The method of claim 1 wherein the preference information comprises data intended to represent a geographic location.

26. The method of claim 25 wherein the preference information comprises a string indicating a location.

27. The method of claim 25 further comprising providing the preference information to a server that converts the data to a geocode location value.

28. The method of claim 27 wherein the geocode location value is provided to a remote module.

29. The method of claim 27 wherein the geocode location value comprises a latitude and longitude value.

30. The method of 25 wherein the preference information is provided to a mapping module.

31. The method of claim 30 wherein the mapping module accesses a map server to generate a map output.

32. The method of claim 31 wherein the map server uses the preference information to generate a map output using the geographic information.

33. The method of claim 31 wherein the map server generates a map output with one or more elements of data from one or more remote modules.

34. The method of claim 33 wherein data from one or more remote modules is overlayed on map output.

35. A system comprising:

a module identification unit that identifies one or more modules for use with a container document;

a preference unit that identifies preferences associated with the module and a user to receive the container document and transmits the preferences to a module server;

a module server that receives module data based on the preferences and serves module data to be used in the container document.

36. A system comprising:

identification means for identifying one or more modules for use with a container document;

preference means for identifying preferences associated with the module and a user to receive the container document and transmits the preferences to a module server; and

module server means for serving module data based on the preferences and serves module data to be used in the container document.

37. A method comprising

storing preference information for a user related to a module for use with a container document, the preferences associated with a location reference where a module specification is stored for the module;

transmitting the preference information with a request for data related to the module to the location reference where a module specification is stored; and

receiving module data customized based on the preference information as applied to the module specification.