Sections of a presentation having user-definable properties

Information

  • Patent Grant
  • 10423301
  • Patent Number
    10,423,301
  • Date Filed
    Monday, February 9, 2015
    11 years ago
  • Date Issued
    Tuesday, September 24, 2019
    7 years ago
Abstract
In general, this disclosure describes techniques that employ user-defined values of properties of sections of an electronic presentation. As described herein, a user may configure a presentation to include a plurality of sections. Each of the sections includes zero or more slides of the electronic slide presentation. In addition to the slides associated with each section, each of the sections is associated with one or more properties having values that can be defined by an author of the presentation. Because the values of the properties of the sections are user-definable, these properties may, in some implementations of these techniques, enable the author of the presentation to use the sections in ways not possible in presentation applications that merely use sections as a means of grouping thumbnail images of slides for navigation among slides in an authoring interface.
Description
BACKGROUND

Electronic presentations are used in a variety of contexts for conveying information. For example, a businessperson may use an electronic slide presentation to convey information about business performance. In another example, a teacher may use an electronic slide presentation to teach a lesson.


Presentation applications executing on personal computers are used to author and present electronic presentations. A typical presentation application presents an authoring interface that enables a user to edit slides in a presentation. The authoring interface may include a primary pane and a navigation pane. The primary pane contains an editable slide in the presentation. The navigation pane may include a series of thumbnail images of each slide in the presentation. A thumbnail image of a slide is a smaller version of the slide. A user of the presentation application can click on a thumbnail image of a slide to cause the primary pane of the authoring interface to display the slide for editing.


Electronic slide presentations may include a large number of slides and may contain information about several topics. For example, a physics teacher may use an electronic slide presentation to teach a lesson that includes slides about resistance, slides about capacitance, and slides about an upcoming exam.


SUMMARY

This Summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This Summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter.


In general, this disclosure describes techniques that employ user-defined values of properties of sections of an electronic presentation. As described herein, a user may configure a presentation to include a plurality of sections. Each of the sections includes zero or more slides of the electronic slide presentation. In addition to the slides associated with each section, each of the sections is associated with one or more properties having values that can be defined by an author of the presentation. Because the values of the properties of the sections are user-definable, these properties may, in some implementations of these techniques, enable the author of the presentation to use the sections in ways not possible in presentation applications that merely use sections as a means of grouping thumbnail images of slides for easy navigation among slides in an authoring interface.


As described below, the properties of a section may include, for example, a title of the section, a name of an author of the section, a set of access control data that specifies rights of users to perform actions with respect to the section, and other properties. The properties of sections may be used during authoring of the presentation or during presentation of the presentation. The uses of such properties during authoring of a presentation may include, for example, the ability to conceal or reveal thumbnail images of slides in a section by clicking on a title of the section, the ability to reorder sections using titles of the sections, the ability to use the name of a section to print the slides in the section, the ability to create a hyperlink to a section of a presentation, the ability to associate searchable keywords with sections, and other uses. The uses of such properties during presentation of the presentation may, for example, include the ability to view names of sections of a presentation during presentation of the presentation and navigating to a first slide in a section.





BRIEF DESCRIPTION OF THE DRAWINGS


FIG. 1 illustrates an example computing device.



FIG. 2 illustrates an example operation that instructions of a presentation application may cause a processing unit of the computing device to perform.



FIG. 3 illustrates an example graphical interface generated by the presentation application for authoring a presentation.



FIG. 4 illustrates an example graphical interface generated by the presentation application for printing slides in the presentation.



FIG. 5 illustrates an example graphical interface generated by the processing unit to select sections to include in a presentation of the presentation.



FIG. 6 illustrates an example graphical interface generated by the processing unit for presenting the presentation.



FIG. 7 illustrates an example graphical interface generated by the processing unit for defining access control data properties of a section of the presentation.



FIG. 8 illustrates a sixth example version of graphical interface 26 generated by processing unit 4 for sorting slides.



FIG. 9 illustrates an example system in which multiple computing devices simultaneously access a presentation file stored in a storage medium accessible by a network.





DETAILED DESCRIPTION

In general, this disclosure describes techniques that employ user-defined values of properties of sections of an electronic presentation. In the following description, various examples are described. It should be appreciated that these examples are provided for purposes of explanation and not as express or implied limitations on the scopes of the claims.



FIG. 1 illustrates an example computing device 2. Computing device 2 may be a wide variety of different types of physical computing devices. For example, computing device 2 may be a personal computer, a laptop computer, a tablet computer, a server computer, a mainframe computer, a mobile telephone, a network telephone, a television set top box, a personal media player, or another type of computing device. Furthermore, computing device 2 may implemented as two or more physically separate “boxes.” For example, computing device 2 may be a cluster of two or more physical computing devices. In another example, computing device 2 may be a grid computing system.


As illustrated in the example of FIG. 1, computing device 2 comprises a processing unit 4 that is capable of executing instructions. Processing unit 4 may be implemented as a set of integrated circuits that includes at least one integrated circuit. In one example implementation, processing unit 4 is a Core 2 processor manufactured by Intel Corporation of Santa Clara, Calif. In other example implementations, processing unit 4 is implemented as a plurality of integrated circuits distributed among several physical devices.


The example of FIG. 1 also illustrates that computing device 2 comprises a communication link 6 that enables processing unit 4 to communicate with a storage medium 8. Communication link 6 may be a variety of different types of communications link, including a front-side bus, a HyperTransport link, an Intel QuickPath Interconnect, an Accelerated Graphics Port bus, a computer network link (e.g., one or more Ethernet links, fiber optic links, etc.), a PCI link, or another type of link.


Storage medium 8 is capable of storing instructions that are readable and executable by processing unit 4. Storage medium 8 may be a wide variety of different types of computer-readable storage media. For example, storage medium 8 may be implemented as one or more random access memory units, one or more read-only memory units, magnetic disks, optical disks, magnetic tapes, flash memory units, or other types of storage media. It should be appreciated that the term “storage medium” refers to a collection of one or more storage media units or one or more types of storage media. For instance, some data in storage medium 8 may be physically stored on a magnetic tape and some data in storage medium 8 may be physically stored on a magnetic disk.


In the example of FIG. 1, computing device 2 includes a communication link 10 that enables processing unit 4 to communicate with an input device interface 12 and an output device interface 14. Communication link 10 may be a variety of different types of communications link, including a front-side bus, a HyperTransport link, an Intel QuickPath Interconnect, an Accelerated Graphics Port bus, a computer network link (e.g., one or more Ethernet links, fiber optic links, etc.), a PCI link, or another type of link. Input device interface 10 facilitates communication from an input device 16. Output device interface 14 facilitates communication with an output device 18 that is capable of outputting information to the real world. Input device interface 12 and output device interface 14 may be implemented in a variety of ways. For instance, input device interface 12 and/or output device interface 14 may be implemented as a Universal Serial Bus (USB) interface card, a serial bus card, a network interface (e.g., an Ethernet card, a WiFi adapter, a WiMax adapter, etc.) or another type of physical input device interface. In some instances, the functionality of input device interface 10 and the functionality of output device interface 12 may be implemented by a single physical card.


Input device 16 may be wide variety of different types of devices. For example, input device 16 may be a mouse, a trackball, a touch-sensitive screen, a keyboard, a keypad, or another type of input device.


Output device 18 may also be a wide variety of different types of devices. For example, output device 18 may be a visual display unit such as a cathode ray display screen, a liquid crystal display (LCD) screen, a light-emitting diode (LED) array, a plasma screen, or another type of device that is capable of outputting information to the real world. Processing unit 4 may present information on output device 18 in a variety of ways. For example, processing unit 4 and output device interface 14 may be connected to a motherboard of computing device 2. In this example, a digital visual interface cable, or another type of physical video connector cable, may connect the output device interface 14 and output device 18. In this example, processing unit 4 may send instructions regarding an image to output device interface 14 and output device interface 14 may send signals to output device 18 to display the image. In another example, processing unit 4 may present information on output device 18 by transmitting information over a network to a computing device that causes output device 18 to display an image based on the transmitted information.


Storage medium 8 stores a presentation file 20 that represents an electronic presentation. Presentation file 20 contains at least one set of section data. Each set of section data in presentation file 20 defines a section. A “section” is a logical unit of an electronic presentation that has at least one property having a user-definable value and that is associated with zero or more sequential or non-sequential slides of the presentation. Each set of section data identifies a set of slides associated with a section and a user-defined value of a property of the section other than the set of slides included in the section. As discussed below, the property of the section may be a variety of different properties and that a set of section data may include several user-defined values of properties of a section. For example, a first set of section data may contain data that directly represents six slides included in a first section and may contain data that indicates that the name of the first section is “Section 1.” Further, in this example, a second set of section data in presentation file 20 may contain data that directly represents four slides and may contain data that indicates that the name of the second section is “Section 2.” In this example, the first section may include slides 1, 3, 5, 6, 7, and 9 and the second section may include slides 2, 4, 8, and 10.


Presentation file 20 may include a wide variety of different types of data structures that embody the sets of section data. For example, presentation file 20 may include an extensible markup language (XML) data structure for each set of section data. In another example, presentation file 20 may include binary data structures that represent each set of section data. In another example, presentation file 20 may include a set of section data that identifies the first set of slides and identifies the data that specifies the user-defined value of the property of the first section by specifying a link to a third set of section data contained in a second presentation file. In this example, the third set of section data identifies the first set of slides and identifies data that specifies the user-defined value of the property of the first section by containing data that directly represents the first set of slides and by containing data that directly represents the user-defined value of the property of the first presentation.


In addition to presentation file 20, storage medium 8 stores a presentation application 22. Presentation application 22 may be similar in some respects to presentation applications such as the Microsoft POWERPOINT® presentation graphics program sold by Microsoft Corporation of Redmond, Wash., the KEYNOTE® slide presentation software sold by Apple Corporation of Cupertino, Calif., the OpenOffice Impress slide presentation software provided by OpenOffice.org, and the GOOGLE APPS® slide presentation application provided by Google, Inc. of Mountain View, Calif.


In one example implementation, presentation application 22 comprises a set of instructions that are executable by processing unit 4. When a user 24 wants to interact with the electronic presentation represented by presentation file 20, user 24 may use input device 16 to instruct computing device 2 to begin executing the instructions of presentation application 22. For example, user 24 may instruct computing device 2 to begin executing instructions of presentation application 22 by using a mouse to select an icon displayed on output device 18 that represents presentation application 22. In another example, user 24 may instruct computing device 2 to begin executing instructions of presentation application 22 by using a keyboard to select an icon representing presentation file 20.


When processing unit 4 begins executing the instructions of presentation application 22, the instructions cause processing unit 4 to access presentation file 20. Upon accessing presentation file 20, the instructions of presentation application 22 cause processing unit 4 to generate a graphical interface 26 in storage medium 8. When processing unit 4 generates graphical interface 26, processing unit 4 uses the values of the properties of the sections of the presentation. Graphical interface 26, when displayed on output device 18 enables a user 24 to interact with an electronic presentation that includes the slides in each of the sections defined by the sets of section data included in presentation file 20. After causing processing unit 4 to generate graphical interface 26, the instructions of presentation application 22 cause processing unit 4 to display graphical interface 26 on output device 18.



FIG. 2 illustrates a first example operation that instructions of presentation application 22 may cause processing unit 4 of computing device 2 to perform. When processing unit 4 begins executing the instructions of presentation application 22, the instructions cause processing unit 4 to access presentation file 20 (40). In other words, the instructions cause processing unit 4 to retrieve some or all of presentation file 20 from storage medium 8. As described above, presentation file 20 contains at least one set of section data. Each set of section data identifies a set of zero or more slides included in a section and a user-defined value of a property of the section other than the set of slides included in the section. For example, presentation file 20 may contain: (i) a first set of section data that defines a first section, the first set of section data identifying a first set of slides and identifying data that specifies a user-defined value of a property of the first section other than the first set of slides, and (ii) a second set of section data that defines a second section, the second set of section data identifying a second set of slides and identifying data that specifies a user-defined value of a property of the second section other than the second set of slides.


After the instructions of presentation application 22 cause processing unit 4 to access presentation file 20, the instructions of presentation application 22 cause processing unit 4 to generate graphical interface 26 using at least one user-defined value of a property of one of the sections (42). Continuing the example cited in the previous paragraph, the instructions of presentation application 22 may cause processing unit 4 to generate graphical interface 26 using the value of property of the first section and the value of the property of the second section. Once processing unit 4 generates graphical interface 26, the instructions of presentation application 22 cause processing unit 4 to display graphical interface 26 on output device 18 (44).


As mentioned above, graphical interface 26 is designed to enable user 24 to interact with a presentation that includes slides in the sections contained in presentation file 20. Accordingly, when output device 18 displays graphical interface 26, the instructions of presentation application 22 enable processing unit 4 to receive input related to a property of a section in the presentation (46). For example, the instructions of presentation application 22 may enable processing unit 4 to receive mouse movement and mouse click input. In response to the input, the instructions of presentation application 22 cause processing unit 4 to perform an action using the property of the section (48).


The instructions of presentation application 22 may cause processing unit 4 to generate graphical interface 26 in a wide variety of ways, thereby enabling a wide variety of possible ways that user 24 can interact with the presentation. Furthermore, because the instructions of presentation application 22 may cause processing unit 4 to generate graphical interface 26 in a wide variety of ways, processing unit 4 may be receive a wide variety of inputs in step 46 and may perform a wide variety of actions in response to these inputs in step 48. Some of the potential ways of generating graphical interface 26 to enable specific types of interaction are summarized with reference to FIGS. 3-8.


In a first example, presentation file 20 includes sets of section data that contain user-defined values of title properties of the sections of the presentation. Referring to FIG. 3, the instructions of presentation application 22 cause processing unit 4 to generate graphical interface 26 such that graphical interface 26 includes a primary pane 70 and a navigation pane 72. Primary pane 70 contains an editable slide 76 in the presentation. Navigation pane 72 includes a series of thumbnail images 78A through 78D (collectively, “thumbnail images 78”) of slides in the presentation. In addition to thumbnail images 78, navigation pane 72 includes the values of the title properties 80A-80C (collectively, “titles 80”) of the sections of the presentation. Thumbnail images of slides within a section are shown below the value of the title property of the section. For instance, in the example of FIG. 3, thumbnail images 78A and 78B are shown below the title “Electrical Properties” indicating that the slides represented by thumbnail images 78A and 78B are within a section having the title property “Electrical Properties.” Similarly, thumbnail images 78C and 78D are shown below the title “Ohm's Law” indicating that the slides represented by thumbnail images 78C and 78D are within the section having the title property “Ohm's Law.”


The example interface in FIG. 3 also illustrates that a first section may be a child section of a second section. When a first section is a child section of a second section, all slides in the first section are slides in the second section, but all slides in the second section are not necessarily slides in the first section. In the example of FIG. 3, the section having the title property “Ohm's Law” is a child section of the section having the title property “Electrical Properties.” The fact that the section having the title property “Ohm's Law” is a child section of the section having the title property “Electrical Properties” is demonstrated visually by the indentation of the title “Ohm's Law” relative to the title “Electrical Properties” and the indentation of the thumbnail images of the slides in the section having the title property of “Ohm's Law” relative to slides in the section having the title property “Electrical Properties.”


The example interface in FIG. 3 also includes conceal icons 82A and 82B (collectively, “conceal icons 82”). When graphical interface 26 is displayed on output device 18, user 24 may use input device 14 to select one of conceal icons 82. When user 24 selects conceal icon 82A, processing unit 4 receives section concealment input that indicates that user 24 wants to conceal the thumbnail images of slides in the section having the title property “Electrical Properties.” Note that in the example of FIG. 3, the slides in the section having the title property “Electrical Properties” include all slides in the section having the title property “Ohm's Law” and all slides in the section having the title property “Capacitance.” In response to the section concealment input, the instructions of presentation application 22 cause processing unit 4 to update graphical interface 26 such that graphical interface 26 does not include any thumbnail images of slides in the section having the title property “Electrical Properties” (i.e., thumbnail images 78A, 78B, 78C, and 78D). The instructions of presentation application 22 may also cause processing unit 4 to update graphical interface 26 such that graphical interface 26 does not include the titles of any sections that are child sections of the section having the title property “Electrical Properties” (i.e., “Capacitance” and “Ohm's Law”). The instructions of presentation application 22 also cause processing unit 4 to display the updated graphical interface on output device 18.


The example interface in FIG. 3 also includes a reveal icon 84. The instructions of presentation application 22 may cause processing unit 4 to display a reveal icon next to a title of a section in which the thumbnail image of slides in the section are concealed. When user 24 selects reveal icon 84, processing unit 4 receives section reveal input that indicates that user 24 wants to reveal the thumbnail images of slides in the section having the title property “Capacitance.” In response to the section reveal input, the instructions of presentation application 22 cause processing unit 4 to update graphical interface 26 such that graphical interface 26 includes thumbnail images of slides in the section having the title “Capacitance.” The instructions of presentation application 22 then cause processing unit 4 to display the updated graphical interface on output device 18.


The example interface of FIG. 3 also includes an auto-update field 86 within slide 76. Auto-update field 86 contains the value of the title property of the section to which slide 76 belongs. In the example of FIG. 3, slide 76 belongs to the section having the title “Ohm's Law.” When user 24 elects to change the value of the title property of the section to which slide 76 belongs, processing unit 4 receives title change input that indicates a new title for the section. In response to the title change input, the instructions of presentation application cause processing unit 4 to update the value of the title property displayed in auto-update field 86. It should be understood that other auto-update fields may contain values of other properties of sections. For instance, an auto-update field in a slide of a section may contain the name specified by an “author” property of the section. In this instance, if user 24 elected to change the value of the “author” property of the section, the instructions of presentation application 22 cause processing unit 4 to automatically update the name contained in the auto-update field.


The example interface of FIG. 3 also includes a link 88. During presentation of the presentation, user 24 may select link 88 in order to jump to the sequentially first slide in a presentation selection referenced by link 88. In the example of FIG. 3, selection on link 88 may cause processing unit 4 to display the sequentially first slide in the section titled “Capacitance.”


User 24 can use the example interface of FIG. 3 to interact with the presentation in additional ways. For example, user 24 may use input device 14 to select a section by selecting the title (e.g., title 80C) of the section in navigation pane 72. When user 24 selects one of titles 80, processing unit 4 receives section selection input that indicates that user 24 has selected the section associated with the selected one of titles 80. In response to the section selection input, the instructions of presentation application 22 cause processing unit 4 to update graphical interface 26 such that the thumbnail images of the slides in the selected section are visually differentiated from the thumbnail images of the slides in the non-selected sections. For example, the thumbnail images of the slides in the selected section may be visually differentiated from the thumbnail images of the slides in the non-selected sections by a thicker border around the thumbnail images of the slides in the selected section.


When user 24 has selected a section, processing unit 4 may receive copy command input from user 24 and may subsequently receive paste command input from user 24. In response to the paste command input, the instructions of presentation application 22 cause processing unit 4 to copy the presentation data that defines the selected section to a location indicated by the paste command input. For instance, when the paste command input indicates a location in a second presentation, the instructions of presentation application 22 may cause processing unit 4 to copy the set of presentation data that defines the selected section to a location in the second presentation. As a result, the second presentation includes the selected section, including the data identifying the slides in the selected section and values of properties of the selected section. The copy command input may take the form of user 24 clicking on the title of a section of the presentation and the paste command input may take the form of user 24 dragging the title of the section to a location and “dropping” the title of the section at a location where the section is to be added.



FIG. 4 illustrates a second example version of graphical interface 26 generated by processing unit 4 for printing slides in the presentation. In the example of FIG. 4, graphical interface 26 is a print dialog window. The instructions of presentation application 22 may cause processing unit 4 to display graphical interface 26 in response to an input from user 24 that indicates that user 24 wants to print slides in the presentation. As illustrated in the example of FIG. 4, graphical interface 26 includes a “Printer” drop box 100 that enables user 24 to select a printer with which to print the slides of the presentation. Furthermore, as illustrated in the example of FIG. 4, graphical interface 26 includes a “Print Sections” drop box 102. User 24 may interact with “Print Sections” drop box 102 to indicate that user 24 wants to print slides in all sections of the presentation or that user 24 wants to print slides only in a selected section of the presentation. When user 24 interacts with “Print Sections” drop box 102, processing unit 4 may receive section selection input that indicates one or more of the sections as selected sections. Furthermore, as illustrated in the example of FIG. 4, graphical interface 26 includes an “OK” button 104. When user 24 uses input device 14 to select “OK” button 104, processing unit 4 instructs the printing device indicated by “Printer” drop box 100 to print the slides in the selected sections.



FIG. 5 illustrates a third example version of graphical interface 26 generated by processing unit 4 that enables user 24 to select sections to display in a presentation of the presentation. As illustrated in the example of FIG. 5, graphical interface 26 is a section selection dialog window. The instructions of presentation application 22 may cause processing unit 4 to display graphical interface 26 in response to an input from user 24 that indicates that user 24 wants to select sections of the presentation to be displayed in a presentation of the presentation. In the example of FIG. 5, graphical interface 26 includes a list 110 of the values of the title properties of the sections in the presentation. In addition, graphical interface 26 includes checkboxes 112A-112C (collectively, “checkboxes 112”) next to each of the values of the title properties of the sections in the presentation. A checkmark in one of checkboxes 112 next to a value of the title property of one of the sections indicates that a property of the section specifies that the slides of the section are to be included in a presentation of the presentation. In the example of FIG. 5, there are checkmarks in checkboxes 112A and 112B, indicating that slides in the section titled “Electric Properties” and slides in the section titled “Ohm's Law” are to be included in a presentation of the presentation and that the slides in the section titled “Capacitance” are not to be included in the presentation of the presentation.


User 24 may use input device 14 to add or remove checkmarks from checkboxes 112. When user 24 adds a checkmark to one of checkboxes 112, processing unit 4 receives section selection input that indicates that user 24 wants slides in the section associated with the one of checkboxes 112 to be included in the presentation of the presentation. In response to the section selection input, processing unit 4 modifies the value of property of the presentation selection to indicate that the slides of the section are to be included in presentations of the presentation.


Later, processing unit 4 may receive input that indicates that user 24 wants to present the presentation. In response to this input, the instructions of presentation application 22 may cause processing unit 4 to use the value of the property of the selected section to determine whether to display the slides of the selected section. Subsequently, the instructions of presentation application 22 may cause processing unit 4 to generate a presentation graphical interface that includes a slide of the selected section when it is determined that the value of the property of the selected section indicates that the slides of the selected section are to be displayed in the presentation of the presentation. The instructions of presentation application 22 may then cause processing unit 4 to display the presentation graphical interface on output device 18. In this way, sections can be skipped seamlessly during presentation of the presentation.



FIG. 6 illustrates a fourth example version of graphical interface 26 generated by processing unit 4 for presenting the presentation. As illustrated in the example of FIG. 6, graphical interface 26 includes slide 76 (FIG. 3). Furthermore, graphical interface 26 shows a pointer 130 controlled by user 24 using input device 14. User 24 may use input device 14 to indicate that user 24 wants to skip to a different section of the presentation. For example, user 24 may press a right mouse button of input device 14. When user 24 indicates that user 24 wants to skip to a different section of the presentation, processing unit 4 updates graphical interface 26 such that graphical interface 26 includes a menu 132 that lists the values of the title properties of the sections of the presentation. User 24 may then position pointer 130 to indicate that user 24 wants to skip to a particular section of the presentation. When user 24 indicates that user 24 wants to skip to a selected section of the presentation, processing unit 4 receives section selection input that indicates that user 24 wants output device 18 to display a sequentially first slide in the selected section. In response to the section selection input, the instructions of presentation application 22 cause processing unit 4 to update graphical interface 26 such that graphical interface 26 includes an image of the sequentially first slides in the selected section and causes processing unit 4 to display the updated graphical interface on output device 18.



FIG. 7 illustrates a fifth example version of graphical interface 26 generated by processing unit 4 for defining access control data properties of a section of the presentation. In the example of FIG. 7, graphical interface 26 enables user 24 to select access control data for the section titled “Ohm's Law.” Specifically, graphical interface 26 includes a “users” drop box 150 that enables user 24 to select another user. For instance, in the example of FIG. 7, user 24 may select users named “Hillary,” “John,” “David,” or “Trevor.” In addition, graphical interface 26 includes a list of rights 152. In the example of FIG. 7, list of rights 152 includes a right to view slides in the section titled “Ohm's Law” and a right to edit slides in the section titled “Ohm's Law.” Furthermore, graphical interface 26 includes a checkbox 154A and a checkbox 154B. A checkmark in checkbox 154A indicates a property of the section titled “Ohm's Law” has a value that specifies that the user selected in “users” drop box 150 has the right to view slides in the section titled “Ohm's Law.” A checkmark in checkbox 154B indicates a property of the section titled “Ohm's Law” has a value that specifies that the user selected in “users” drop box 150 has the right to edit slides in the section titled “Ohm's Law.” User 24 may redefine the values of these properties by clicking on checkbox 154A and/or checkbox 154B.


It should be appreciated that values of these properties for a single user may differ among sections of the presentation. For instance, the value of the property of a first section represents a first set of access control data that specifies that a user has a right to perform an action with respect to the first section and the value of the property of the second section represents a second set of access control data that specifies that the user does not have the right to perform the action with respect to the second section.


Subsequently, processing unit 4 may receive a request from a user to perform an action (e.g., view or edit a slide) with respect to a section in the presentation. In response to receiving the request from the user to perform the action with respect to the section of the presentation, the instructions of presentation application 22 cause processing unit 4 to use these properties of the section to determine whether the user has a right to perform the action with respect to the section. If the user has the right to perform the action with respect to the section, the instructions of presentation application 22 cause processing unit 4 to perform the action. If the user does not have the right to perform the action with respect to the section, the instructions of presentation application 22 cause processing unit 4 to deny the request to perform the action.



FIG. 8 illustrates a sixth example version of graphical interface 26 generated by processing unit 4 for sorting slides. As illustrated in the example of FIG. 8, graphical interface 26 includes title bars 170A, 170B, 170C, and 170D (collectively, “title bars 170”). Title bars 170 include the values of title properties of sections in a presentation. In the example of FIG. 8, title bar 170A indicates that “Introduction” is the value of a title property of a first section of a presentation, title bar 170B indicates that “Q2 Sales Report” is the value of a title property of a second section of the presentation, title bar 170C indicates that “Q3 Sales Outlook” is the value of a title property of a third section of the presentation, and title bar 170D indicates that “Q3 Expenses Outlook” is the value of a title property of a fourth section of the presentation. Title bars 170 also indicate how many slides are in each of the sections of the presentation.


Title bars 170 include icons 172A, 172B, 172C, and 172D (collectively, “icons 172”) that enable user 24 to conceal or reveal thumbnail images of slides. In the example of FIG. 8, graphical interface 26 includes a set of thumbnail images 174A beneath title bar 170A that includes thumbnail images in the first section of the presentation. In addition, in the example of FIG. 8, graphical interface 26 includes a set of thumbnail images 174B beneath title bar 170C that includes thumbnail images in the third section of the presentation. User 24 may conceal thumbnail images 174A by selecting icon 172A and may conceal thumbnail images 174B by selecting icon 172C. User 24 may reveal a set of thumbnail images of the slides in the second section of the presentation by selecting icon 172B. Because the fourth section of the presentation does not include any slides, graphical interface 24 does not display any thumbnail images beneath title bar 170D.


User 24 may use this version of graphical interface 24 to organize slides of the presentation into sections. For example, user 24 may use input device 14 to select one of thumbnail images 174A. User 24 may then drag the selected thumbnail image of the slide to an area of graphical interface 26 beneath one of title bars 170. When user 24 has dragged the thumbnail image of the slide to the area of graphical interface 26 beneath one of title bars 170, the slide is removed from the first section added to the section of the presentation associated with the title bar. For instance, user 24 drags the selected thumbnail image of the slide to an area of graphical interface 26 beneath title bar 170D, the slide is removed from the first section and added to the fourth section.


User 24 may interact with the presentation in a variety of ways by selecting title bars 170. For instance, by selecting title bars 170, user 24 may change the values of the title properties of the sections of the presentation. In another instance, by selecting title bars 170, user 24 may add a set of keywords that enable a search engine to identify a section within the presentation. In each of these instances, when user 24 selects one of title bars 170, processing unit 4 receives input and the instructions of presentation application 22 cause processing unit 4 to perform an action in response.



FIG. 9 illustrates an example system 190 in which multiple computing devices 192 and 194 simultaneously access a presentation file 196 stored in a storage medium 198 accessible by a network 200. In system 190, presentation file 196 may include a first set of section data that defines a first section and a second set of section data that defines a second section. Because the first set of section data and the second set of section data are logically distinct within presentation file 196, a user of computing device 192 may edit slides in the first section of the presentation at the same time that a user of computing device 194 is editing slides in the second section of the presentation. This may enable these users to work on the presentation in a collaborative fashion.


It is to be understood that the implementations described herein may be implemented by hardware, software, firmware, middleware, microcode, or any combination thereof. When the systems and/or methods are implemented in software, firmware, middleware or microcode, program code or code segments, they may be stored in a computer-readable storage medium, such as a storage component. A code segment may represent a procedure, a function, a subprogram, a program, a routine, a subroutine, a module, a software package, a class, or any combination of instructions, data structures, or program statements A code segment may be coupled to another code segment or a hardware circuit by passing and/or receiving information, data, arguments, parameters, or memory contents. Information, arguments, parameters, data, etc. may be passed, forwarded, or transmitted using any suitable means including memory sharing, message passing, token passing, network transmission, etc.


Furthermore, it is to be understood that computing device 2 may have additional features or functionality. For example, computing device 2 may also include additional data storage devices (removable and/or non-removable) such as, for example, magnetic disks, optical disks, or tape. Computer-readable storage media may include volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information, such as computer readable instructions, data structures, program modules, or other data.


For a software implementation, the techniques described herein may be implemented with modules (e.g., procedures, functions, and so on) that perform the functions described herein. The software codes and instructions may be stored in computer-readable storage media and executed by processors. The memory unit may be implemented within the processor or external to the processor, in which case it can be communicatively coupled to the processor via various means as is known in the art.


These techniques may be realized in several ways. For example, these techniques may be conceptualized as a method for organizing slides of an electronic slide presentation. The method comprises accessing, with a computing device, a presentation file stored on a computer-readable storage medium, the presentation file containing: (i) a first set of section data that defines a first section, the first set of section data identifying a first set of slides and identifying data that specifies a user-defined value of a property of the first section other than the first set of slides, and (ii) a second set of section data that defines a second section, the second set of section data identifying a second set of slides and identifying data that specifies a user-defined value of a property of the second section other than the second set of slides. The method also comprises generating, at the computing device, a graphical interface using the value of the property of the first section and the value of the property of the second section, the graphical interface enabling a user to interact with an electronic presentation that includes the slides in the first set of slides and the slides in the second set of slides. In addition, the method comprises displaying the graphical interface on an output device.


In another example, the techniques of this disclosure may be realized as a computing device comprising a processing unit that is capable of executing instructions, an output device, and a storage medium. The storage medium comprises a presentation file stored on a computer-readable storage medium, the presentation file containing: (i) a first set of section data that defines a first section, the first set of section data identifying a first set of slides and identifying data that specifies a user-defined value of a property of the first section other than the first set of slides, and (ii) a second set of section data that defines a second section, the second set of section data identifying a second set of slides and identifying data that specifies a user-defined value of a property of the second section other than the second set of slides. The computer-readable storage medium also comprises instructions that, when executed by the processing unit, cause the processing unit to: access the presentation file; generate a graphical interface using the value of the property of the first section and the value of the property of the second section, the graphical interface enabling a user to interact with an electronic presentation that includes the slides in the first set of slides and the slides in the second set of slides; and display the graphical interface on the output device.


In another example, the techniques of this disclosure may be realized as a computer-readable storage medium comprising a presentation file stored on a computer-readable storage medium, the presentation file containing: (i) a first set of section data that defines a first section, the first set of section data identifying a first set of slides, identifying data that specifies a title of the first section, and identifying data that specifies a user-defined value of a property of the first section that represents a first set of access control data that specifies that the user has a right to perform an action with respect to the first section, and (ii) a second set of section data that defines a second section, the second set of section data identifying a second set of slides, identifying data that specifies a title of the second section, and identifying data that specifies a user-defined value of a property of the second section that represents a second set of access control data that specifies that the user does not have the right to perform the action with respect to the second section. The computer-readable storage medium also comprises instructions that, when executed by a processing unit of a computing device, cause the processing unit to access the presentation file. The instructions also cause the processing unit to generate a graphical interface that displays the title of the first section and the title of the second section. Furthermore, the instructions cause the processing unit to receive a request from the user to perform the action with respect to the first section. The instructions also cause the processing unit to, in response to receiving the request from the user to perform the action with respect to the first section, determine that the second set of access control data specifies that the user does not have the right to perform the action with respect to the second section; and perform the action with respect to the first section. In addition, the instructions cause the processing unit to receive a request from the user to perform the action with respect to the second section. Furthermore, the instructions cause the processing unit to, in response to receiving the request from the user to perform the action with respect to the second section, determine that the second set of access control data specifies that the user does not have the right to perform the action with respect to the second section and deny the request to perform the action with respect to the second section.


Although the subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.

Claims
  • 1. A method for providing access to an electronic file based on user-definable properties, comprising: accessing, with a computing device, the electronic file stored on a computer-readable storage medium, the electronic file comprising: a first set of data within the electronic file comprising a first set of access control data, the first set of access control data specifying at least a first action that a user has a right to perform on the first set of data, wherein the first set of access control data is received via a user interface operable to identify a set of data and one or more actions that may be performed on the set of data; anda second set of data within the electronic file comprising a second set of access control data, the second set of access control data specifying at least a second action that a user has a right to perform on the second set of data, wherein the second set of access control data is received via the user interface;receiving, at the computing device, a request from the user to perform a first user action with respect to the first set of data;in response to receiving the request from the user to perform the first user action with respect to the first set of data: determining, by the computing device, whether the user has the right to perform the first user action with respect to the first set of data based upon the first set of access control data;when the user has the right to perform the first user action with respect to the first set of data, performing, by the computing device, the first user action with respect to the first set of data; andwhen the user does not have the right to perform the first user action with respect to the first set of data, denying, by the computing device, the request to perform the first user action with respect to the first set of data.
  • 2. The method of claim 1, wherein the first user action comprises viewing the first set of data.
  • 3. The method of claim 1, wherein the first user action comprises editing the first set of data.
  • 4. The method of claim 1, further comprising: receiving, at the computing device, a request from the user to perform a second user action with respect to the second set of data;in response to receiving the request from the user to perform the second action with respect to the second set of data: determining, by the computing device, whether the user has the right to perform the second action with respect to the second set of data based upon the second set of access control data;when the user has the right to perform the second action with respect to the second set of data, performing, by the computing device, the second action with respect to the second set of data; andwhen the user does not have the right to perform the second action with respect to the second set of data, denying, by the computing device, the request to perform the second action with respect to the second set of data.
  • 5. The method of claim 4, wherein the second user action comprises one of viewing or editing the second set of data.
  • 6. The method of claim 1, further comprising: displaying a graphical interface that includes user names associated with the electronic file.
  • 7. The method of claim 6, wherein the user names are selected from a drop box.
  • 8. The method of claim 6, wherein the graphical interface graphically indicates which user name has the right to perform an edit action.
  • 9. A computing device, comprising: a processing unit;a storage medium including instructions, which when executed by the processing unit, cause the computing device to be operable to: access, with a computing device, an electronic file stored on a computer-readable storage medium, the electronic file containing: a first set of data within the electronic file comprising a first set of access control data, the first set of access control data specifying at least a first action that a user has a right to perform on the first set of data, wherein the first set of access control data is received via a user interface operable to identify a set of data and one or more actions that may be performed on the set of data; anda second set of data within the electronic file comprising a second set of access control data, the second set of access control data specifying at least a second action that a user has a right to perform on the second set of data, wherein the second set of access control data is received via the user interface;receiving, at the computing device, a request from the user to perform a first user action with respect to the first set of data;in response to receiving the request from the user to perform the first user action with respect to the first set of data: determining, by the computing device, whether the user has the right to perform the first user action with respect to the first set of data based upon the first set of access control data;when the user has the right to perform the first user action with respect to the first set of data, performing, by the computing device, the first user action with respect to the first set of data; andwhen the user does not have the right to perform the first user action with respect to the first set of data, denying, by the computing device, the request to perform the first user action with respect to the first set of data.
  • 10. The computing device of claim 9, wherein the first user action comprises viewing the first set of data.
  • 11. The computing device of claim 9, wherein the first user action comprises editing the first set of data.
  • 12. The computing device of claim 9, wherein the computing device is further operable to: receive, at the computing device, a request from the user to perform a second user action with respect to the second set of data;in response to receiving the request from the user to perform the second user action with respect to the second set of data: determine, by the computing device, whether the user has the right to perform the second action with respect to the second set of data based upon the second set of access control data;when the user has the right to perform the second action with respect to the second set of data, perform, by the computing device, the second action with respect to the second set of data; andwhen the user does not have the right to perform the second action with respect to the second set of data, deny, by the computing device, the request to perform the second action with respect to the second set of data.
  • 13. The computing device of claim 12, wherein the second user action comprises one of viewing or editing the second set of data.
  • 14. The computing device of claim 9, further comprising: displaying a graphical interface that includes user names associated with the electronic file.
  • 15. The computing device of claim 14, wherein the user names are selected from a drop box.
  • 16. The computing device of claim 14, wherein the graphical interface graphically indicates which user name has the right to perform an edit action.
  • 17. A computer-readable storage medium having computer-executable instructions that, when executed by a processing unit, cause the processing unit to perform steps comprising: accessing, with a computing device, an electronic file stored on a computer-readable storage medium, the electronic file containing: a first set of data within the electronic file comprising a first set of access control data, the first set of access control data specifying that a user has a right to perform an action with respect to the first set of data, wherein the first set of access control data is received via a user interface operable to identify a set of data and one or more actions that may be performed on the set of data; anda second set of data within the electronic file comprising a second set of access control data, the second set of access control data specifying that the user does not have a right to perform the action with respect to the second set of data, wherein the second set of access control data is received via the user interface;receiving, at the computing device, a request from the user to perform the action with respect to the first set of data;in response to receiving the request from the user to perform the action with respect to the first set of data: determining, by the computing device, whether the user has the right to perform the action with respect to the first set of data based upon the first set of access control data; andafter determining that the user has the right to perform the action with respect to the first set of data, performing, by the computing device, the action with respect to the first set of data;receiving, at the computing device, a request from the user to perform the action with respect to the second set of data; andin response to receiving the request from the user to perform the action with respect to the second set of data: determining, by the computing device, whether the user does not have the right to perform the action with respect to the second set of data based upon the second set of access control data; andafter determining that the user does not have the right to perform the action with respect to the second set of data, denying, by the computing device, the request to perform the action with respect to the second set of data.
  • 18. The computer-readable storage medium of claim 17, wherein the action comprises one of viewing or editing.
  • 19. The computer-readable storage medium of claim 17, further comprising: displaying a graphical interface that includes user names associated with the electronic file.
  • 20. The computer-readable storage medium of claim 19, wherein the graphical interface graphically indicates which user name has the right to perform an edit action.
CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of application Ser. No. 13/361,009, filed Jan. 30, 2012, and assigned U.S. Pat. No. 8,954,857, which is a continuation of application Ser. No. 12/189,583, filed Aug. 11, 2008, and now U.S. Pat. No. 8,108,777, the disclosures of which are incorporated by reference herein in their entirety.

US Referenced Citations (477)
Number Name Date Kind
4831552 Scully et al. May 1989 A
5107443 Smith et al. Apr 1992 A
5195086 Baumgartner et al. Mar 1993 A
5220657 Bly et al. Jun 1993 A
5297250 Leroy et al. Mar 1994 A
5495269 Elrod et al. Feb 1996 A
5566291 Boulton et al. Oct 1996 A
5572644 Liaw et al. Nov 1996 A
5649105 Aldred et al. Jul 1997 A
5652866 Aldred et al. Jul 1997 A
5675520 Pit et al. Oct 1997 A
5675752 Scott et al. Oct 1997 A
5689641 Ludwig et al. Nov 1997 A
5704029 Wright, Jr. Dec 1997 A
5717869 Moran et al. Feb 1998 A
5758110 Boss et al. May 1998 A
5793365 Tang et al. Aug 1998 A
5802299 Logan et al. Sep 1998 A
5821925 Carey et al. Oct 1998 A
5821932 Pittore Oct 1998 A
5874958 Ludolph Feb 1999 A
5893098 Peters et al. Apr 1999 A
5907324 Larson et al. May 1999 A
5956489 San Andres et al. Sep 1999 A
5960173 Tang et al. Sep 1999 A
5990888 Blades et al. Nov 1999 A
6008807 Bretschneider et al. Dec 1999 A
6014135 Fernandes Jan 2000 A
6016478 Zhang et al. Jan 2000 A
6018346 Moran et al. Jan 2000 A
6041333 Bretschneider et al. Mar 2000 A
6101480 Conmy et al. Aug 2000 A
6119147 Toomey et al. Sep 2000 A
6128629 Bretschneider et al. Oct 2000 A
6144991 England Nov 2000 A
6192395 Lemer et al. Feb 2001 B1
6208339 Atlas et al. Mar 2001 B1
6215498 Filo et al. Apr 2001 B1
6230185 Salas et al. May 2001 B1
6237025 Ludwig et al. May 2001 B1
6249281 Chen et al. Jun 2001 B1
6314408 Salas et al. Nov 2001 B1
6353436 Reichlen Mar 2002 B1
6363352 Dailey et al. Mar 2002 B1
6369835 Lin Apr 2002 B1
6396500 Qureshi et al. May 2002 B1
6396512 Nickerson May 2002 B1
6421655 Horvitz et al. Jul 2002 B1
6438564 Morton et al. Aug 2002 B1
6469711 Foreman et al. Oct 2002 B2
6473749 Smith et al. Oct 2002 B1
6522347 Tsuji et al. Feb 2003 B1
6546246 Bridges et al. Apr 2003 B1
6546405 Gupta et al. Apr 2003 B2
6553417 Gampper Apr 2003 B1
6586349 Jeon et al. Jul 2003 B1
6608636 Roseman Aug 2003 B1
6630944 Kakuta et al. Oct 2003 B1
6633315 Sobeski et al. Oct 2003 B1
6639836 Hung et al. Oct 2003 B1
6670970 Bonura et al. Dec 2003 B1
6735615 Iwayama et al. May 2004 B1
6738075 Torres et al. May 2004 B1
6744447 Estrada et al. Jun 2004 B2
6757365 Bogard Jun 2004 B1
6819338 Heasman et al. Nov 2004 B2
6834371 Jensen et al. Dec 2004 B1
6853988 Dickinson et al. Feb 2005 B1
6926799 Yeom et al. Aug 2005 B2
6933495 Yeom et al. Aug 2005 B1
6938032 Heath et al. Aug 2005 B1
6981223 Becker et al. Dec 2005 B2
7007067 Azvine et al. Feb 2006 B1
7035865 Doss et al. Apr 2006 B2
7036076 Anwar Apr 2006 B2
7051285 Harrison et al. May 2006 B1
7058647 Hill Jun 2006 B1
7062532 Sweat et al. Jun 2006 B1
7073127 Zhao et al. Jul 2006 B2
7075513 Silfverberg et al. Jul 2006 B2
7076546 Bates et al. Jul 2006 B1
7124123 Roskind et al. Oct 2006 B1
7124164 Chemtob Oct 2006 B1
7143356 Shafrir et al. Nov 2006 B1
7171567 Bayer et al. Jan 2007 B1
7185054 Ludwig et al. Feb 2007 B1
7203479 Deeds Apr 2007 B2
7206773 Erol et al. Apr 2007 B2
7213051 Zhu et al. May 2007 B2
7225257 Aoike et al. May 2007 B2
7233933 Horvitz et al. Jun 2007 B2
7233971 Levy Jun 2007 B1
7242389 Stern Jul 2007 B1
7246316 Furlong et al. Jul 2007 B2
7246317 Karasawa et al. Jul 2007 B2
7248677 Randall et al. Jul 2007 B2
7251786 Wynn et al. Jul 2007 B2
7266568 Erol et al. Sep 2007 B1
7266773 Dorwart Sep 2007 B2
7269787 Amitay et al. Sep 2007 B2
7284203 Meeks et al. Oct 2007 B1
7299193 Cragun et al. Nov 2007 B2
7299405 Lee et al. Nov 2007 B1
7299418 Dieberger Nov 2007 B2
7363581 Parks et al. Apr 2008 B2
7373505 Seltzer et al. May 2008 B2
7392475 Leban et al. Jun 2008 B1
7401300 Nurmi Jul 2008 B2
7421660 Charnock et al. Sep 2008 B2
7426297 Zhang et al. Sep 2008 B2
7447713 Berkheimer Nov 2008 B1
7451186 Morinigo et al. Nov 2008 B2
7454439 Gansner et al. Nov 2008 B1
7466334 Baba Dec 2008 B1
7469222 Glazer Dec 2008 B1
7478129 Chemtob Jan 2009 B1
7493561 Sareen et al. Feb 2009 B2
7512906 Baier et al. Mar 2009 B1
7526726 Skwarecki et al. Apr 2009 B1
7533146 Kumar May 2009 B1
7546533 Sareen et al. Jun 2009 B2
7554576 Erol et al. Jun 2009 B2
7555784 Cameron et al. Jun 2009 B2
7571210 Swanson et al. Aug 2009 B2
7590939 Sareen et al. Sep 2009 B2
7590941 Wee et al. Sep 2009 B2
7599989 Stevens et al. Oct 2009 B2
7606862 Swearingen et al. Oct 2009 B2
7624110 Alagna et al. Nov 2009 B2
7627830 Espinoza et al. Dec 2009 B1
7636754 Zhu et al. Dec 2009 B2
7640506 Pratley et al. Dec 2009 B2
7669141 Pegg Feb 2010 B1
7679518 Pabla et al. Mar 2010 B1
7720698 Gulko et al. May 2010 B1
7730411 Chotai et al. Jun 2010 B2
7743098 Anglin et al. Jun 2010 B2
7743331 Fleischer et al. Jun 2010 B1
7764247 Blanco et al. Jul 2010 B2
7770116 Zhang et al. Aug 2010 B2
7774221 Miller et al. Aug 2010 B2
7799706 Yeom et al. Sep 2010 B2
7818678 Massand Oct 2010 B2
7822200 Cameron et al. Oct 2010 B2
7869941 Coughlin et al. Jan 2011 B2
7882565 Collins et al. Feb 2011 B2
7911409 Chatterjee et al. Mar 2011 B1
7919142 Yeom et al. Apr 2011 B2
7941399 Bailor et al. May 2011 B2
7962525 Kansal Jun 2011 B2
7984387 Batthish et al. Jul 2011 B2
7992089 Murray et al. Aug 2011 B2
8032832 Russ et al. Oct 2011 B2
8099458 Burtne et al. Jan 2012 B2
8108777 Penner et al. Jan 2012 B2
8126974 Lyle et al. Feb 2012 B2
8150719 Perrella et al. Apr 2012 B2
8161419 Palahnuk et al. Apr 2012 B2
8204942 Roskind et al. Jun 2012 B2
8214748 Srikanth et al. Jul 2012 B2
8330795 Iyer et al. Dec 2012 B2
8358762 Renner et al. Jan 2013 B1
8385964 Haney Feb 2013 B2
8423883 Stockmann Apr 2013 B1
8437461 Gartner et al. May 2013 B1
8452839 Heikes et al. May 2013 B2
8517888 Brookins Aug 2013 B1
8560487 Jhoney et al. Oct 2013 B2
8583148 Ollila et al. Nov 2013 B2
8606517 Ehrlacher et al. Dec 2013 B1
8631119 Malkin et al. Jan 2014 B2
8682973 Kikin-Gil et al. Mar 2014 B2
8768308 Kim et al. Jul 2014 B2
8826117 Junee et al. Sep 2014 B1
8954857 Penner et al. Feb 2015 B2
9544158 Kotler et al. Jan 2017 B2
9996241 Kikin-Gil et al. Jun 2018 B2
20010040592 Foreman et al. Nov 2001 A1
20020001106 Lan Jan 2002 A1
20020044683 Deshpande et al. Apr 2002 A1
20020059604 Papagan et al. May 2002 A1
20020060201 Yeom et al. May 2002 A1
20020062403 Burnett et al. May 2002 A1
20020065848 Walker May 2002 A1
20020078007 Herrero Jun 2002 A1
20020101446 Tang et al. Aug 2002 A1
20020109712 Yacovone et al. Aug 2002 A1
20020130904 Becker et al. Sep 2002 A1
20020138389 Martone et al. Sep 2002 A1
20020143876 Boyer et al. Oct 2002 A1
20020143877 Hackbarth et al. Oct 2002 A1
20020143885 Ross, Jr. Oct 2002 A1
20020147777 Hackbarth et al. Oct 2002 A1
20020156787 Jameson et al. Oct 2002 A1
20020164151 Jasinschi et al. Nov 2002 A1
20020174085 Nelson et al. Nov 2002 A1
20030005053 Novaes Jan 2003 A1
20030014409 Shukoor Jan 2003 A1
20030020805 Allen et al. Jan 2003 A1
20030038831 Engelfriet Feb 2003 A1
20030048291 Dieberger Mar 2003 A1
20030052915 Brown et al. Mar 2003 A1
20030061284 Mandarino et al. Mar 2003 A1
20030081785 Boneh et al. May 2003 A1
20030097273 Carpenter et al. May 2003 A1
20030101043 Boegelund et al. May 2003 A1
20030110228 Xu et al. Jun 2003 A1
20030122863 Dieberger et al. Jul 2003 A1
20030135558 Bellotti et al. Jul 2003 A1
20030135559 Bellotti et al. Jul 2003 A1
20030137539 Dees Jul 2003 A1
20030142133 Brown et al. Jul 2003 A1
20030142145 Bennett et al. Jul 2003 A1
20030158900 Santos Aug 2003 A1
20030160814 Brown Aug 2003 A1
20030167339 Zhu et al. Sep 2003 A1
20030172174 Mihalcheon Sep 2003 A1
20030177190 Moody et al. Sep 2003 A1
20030204815 Edwards et al. Oct 2003 A1
20030209519 Yeom et al. Nov 2003 A1
20030222890 Salesin et al. Dec 2003 A1
20030222900 Schramm-Apple et al. Dec 2003 A1
20030231202 Parker et al. Dec 2003 A1
20040001079 Zhao et al. Jan 2004 A1
20040001106 Deutscher et al. Jan 2004 A1
20040015595 Lin et al. Jan 2004 A1
20040016876 Yeom et al. Jan 2004 A1
20040017396 Werndorfer et al. Jan 2004 A1
20040024822 Werndorfer et al. Feb 2004 A1
20040027370 Jaeger Feb 2004 A1
20040030992 Moisa et al. Feb 2004 A1
20040034622 Espinoza et al. Feb 2004 A1
20040062383 Sylvain Apr 2004 A1
20040071453 Valderas Apr 2004 A1
20040085354 Massand May 2004 A1
20040109021 Price Jun 2004 A1
20040113934 Kleinman et al. Jun 2004 A1
20040123157 Alagna et al. Jun 2004 A1
20040125128 Chang et al. Jul 2004 A1
20040128350 Topfl et al. Jul 2004 A1
20040128691 Egawa et al. Jul 2004 A1
20040150627 Luman et al. Aug 2004 A1
20040153456 Charnock et al. Aug 2004 A1
20040161090 Digate et al. Aug 2004 A1
20040169683 Chiu et al. Sep 2004 A1
20040174392 Bjoernsen et al. Sep 2004 A1
20040175036 Graham Sep 2004 A1
20040196286 Guzik Oct 2004 A1
20040205653 Hadfield et al. Oct 2004 A1
20040210845 Paul et al. Oct 2004 A1
20040254998 Horvitz Dec 2004 A1
20040263636 Cutler et al. Dec 2004 A1
20040267701 Horvitz et al. Dec 2004 A1
20040267871 Pratley et al. Dec 2004 A1
20050005025 Harville et al. Jan 2005 A1
20050018828 Nierhaus et al. Jan 2005 A1
20050021754 Alda Jan 2005 A1
20050055625 Kloss Mar 2005 A1
20050057584 Gruen et al. Mar 2005 A1
20050081160 Wee et al. Apr 2005 A1
20050088410 Chaudhri Apr 2005 A1
20050091571 Leichtling Apr 2005 A1
20050091596 Anthony et al. Apr 2005 A1
20050125246 Muller et al. Jun 2005 A1
20050125717 Segal et al. Jun 2005 A1
20050138109 Redlich et al. Jun 2005 A1
20050138570 Good et al. Jun 2005 A1
20050149442 Adams et al. Jul 2005 A1
20050171830 Miller et al. Aug 2005 A1
20050187937 Kawabe Aug 2005 A1
20050193221 Yoneyama Sep 2005 A1
20050235351 Seltzer et al. Oct 2005 A1
20050246642 Valderas et al. Nov 2005 A1
20050278331 Hatori Dec 2005 A1
20050289127 Giampaolo Dec 2005 A1
20050289453 Segal et al. Dec 2005 A1
20060004911 Becker et al. Jan 2006 A1
20060010023 Tromczynski et al. Jan 2006 A1
20060010197 Ovenden Jan 2006 A1
20060020581 Dettinger Jan 2006 A1
20060026253 Kessen et al. Feb 2006 A1
20060036950 Himberger et al. Feb 2006 A1
20060053380 Spataro et al. Mar 2006 A1
20060067250 Boyer et al. Mar 2006 A1
20060067578 Fuse Mar 2006 A1
20060080610 Kaminsky Apr 2006 A1
20060082594 Vafiadis et al. Apr 2006 A1
20060132507 Wang Jun 2006 A1
20060136828 Asano Jun 2006 A1
20060143063 Braun et al. Jun 2006 A1
20060146765 Van de sluis et al. Jul 2006 A1
20060161585 Clarke et al. Jul 2006 A1
20060167996 Orsolini et al. Jul 2006 A1
20060168533 Yip et al. Jul 2006 A1
20060171515 Hintermeister et al. Aug 2006 A1
20060184872 Dontcheva et al. Aug 2006 A1
20060190547 Bhogal et al. Aug 2006 A1
20060195587 Cadiz et al. Aug 2006 A1
20060198517 Cameron et al. Sep 2006 A1
20060200667 Cameron et al. Sep 2006 A1
20060213443 Yeom et al. Sep 2006 A1
20060234735 Digate et al. Oct 2006 A1
20060235732 Miller Oct 2006 A1
20060239212 Pirzada et al. Oct 2006 A1
20060259875 Collins et al. Nov 2006 A1
20060265398 Kaufman Nov 2006 A1
20060265659 Collins et al. Nov 2006 A1
20060282759 Collins et al. Dec 2006 A1
20060284981 Erol Dec 2006 A1
20060294046 Sareen et al. Dec 2006 A1
20060294468 Sareen et al. Dec 2006 A1
20060294469 Sareen et al. Dec 2006 A1
20070005752 Chawla et al. Jan 2007 A1
20070011231 Manion et al. Jan 2007 A1
20070056045 Collins Mar 2007 A1
20070074268 Pepper et al. Mar 2007 A1
20070100937 Burtner et al. May 2007 A1
20070106724 Gorti et al. May 2007 A1
20070112926 Brett et al. May 2007 A1
20070118598 Bedi May 2007 A1
20070150583 Asthana et al. Jun 2007 A1
20070168447 Chen et al. Jul 2007 A1
20070174389 Armstrong et al. Jul 2007 A1
20070185870 Hogue et al. Aug 2007 A1
20070188520 Finley et al. Aug 2007 A1
20070189487 Sharland et al. Aug 2007 A1
20070214423 Teplov et al. Sep 2007 A1
20070219645 Thomas et al. Sep 2007 A1
20070226032 White et al. Sep 2007 A1
20070245238 Fugitt et al. Oct 2007 A1
20070253424 Herot et al. Nov 2007 A1
20070271592 Noda Nov 2007 A1
20070276909 Chavda et al. Nov 2007 A1
20070279416 Cobb et al. Dec 2007 A1
20070294612 Drucker et al. Dec 2007 A1
20070300185 Macbeth et al. Dec 2007 A1
20080005235 Hegde et al. Jan 2008 A1
20080008458 Gudipaty et al. Jan 2008 A1
20080013698 Holtzberg Jan 2008 A1
20080022225 Erl Jan 2008 A1
20080025691 Kinoshita et al. Jan 2008 A1
20080040187 Carraher et al. Feb 2008 A1
20080040188 Klausmeier Feb 2008 A1
20080059889 Parker Mar 2008 A1
20080065580 Spence et al. Mar 2008 A1
20080066016 Dowdy et al. Mar 2008 A1
20080070218 Ahl et al. Mar 2008 A1
20080084984 Levy et al. Apr 2008 A1
20080098328 Rollin et al. Apr 2008 A1
20080114844 Sanchez et al. May 2008 A1
20080115076 Frank et al. May 2008 A1
20080136897 Morishima et al. Jun 2008 A1
20080141126 Johnson et al. Jun 2008 A1
20080177782 Poston et al. Jul 2008 A1
20080189616 Coulomb et al. Aug 2008 A1
20080189624 Chotai et al. Aug 2008 A1
20080195981 Pulier et al. Aug 2008 A1
20080239995 Lee et al. Oct 2008 A1
20080263460 Altberg et al. Oct 2008 A1
20080276174 Hintermeister et al. Nov 2008 A1
20080288889 Hunt et al. Nov 2008 A1
20080300944 Surazski et al. Dec 2008 A1
20080303746 Schlottmann et al. Dec 2008 A1
20080307322 Stochosky et al. Dec 2008 A1
20080313544 Kleinman et al. Dec 2008 A1
20080320082 Kuhlke et al. Dec 2008 A1
20090006980 Hawley et al. Jan 2009 A1
20090006982 Curtis et al. Jan 2009 A1
20090007003 Dukhon et al. Jan 2009 A1
20090007014 Coomer et al. Jan 2009 A1
20090019367 Cavagnari et al. Jan 2009 A1
20090030766 Denner et al. Jan 2009 A1
20090037821 O'Neal et al. Feb 2009 A1
20090037848 Tewari et al. Feb 2009 A1
20090043856 Darby Feb 2009 A1
20090044117 Vaughan et al. Feb 2009 A1
20090055739 Murillo et al. Feb 2009 A1
20090089055 Caspi et al. Apr 2009 A1
20090092068 Moritomo Apr 2009 A1
20090094367 Song et al. Apr 2009 A1
20090109180 Do et al. Apr 2009 A1
20090112703 Brown Apr 2009 A1
20090119255 Frank et al. May 2009 A1
20090119604 Simard et al. May 2009 A1
20090129596 Chavez et al. May 2009 A1
20090138552 Johnson et al. May 2009 A1
20090138826 Barros May 2009 A1
20090183095 Deitsch et al. Jul 2009 A1
20090204671 Hawkins et al. Aug 2009 A1
20090210793 Yee et al. Aug 2009 A1
20090222741 Shaw et al. Sep 2009 A1
20090222763 Dukhon et al. Sep 2009 A1
20090228569 Kalmanje et al. Sep 2009 A1
20090234721 Bigelow et al. Sep 2009 A1
20090235166 Keohane et al. Sep 2009 A1
20090235177 Saul et al. Sep 2009 A1
20090249223 Barsook et al. Oct 2009 A1
20090254843 Van wie et al. Oct 2009 A1
20090265632 Russ et al. Oct 2009 A1
20090282339 Van melle et al. Nov 2009 A1
20090300501 Miller et al. Dec 2009 A1
20090309846 Trachtenberg et al. Dec 2009 A1
20090313584 Kerr et al. Dec 2009 A1
20090319562 Holm-Petersen et al. Dec 2009 A1
20100005398 Pratley et al. Jan 2010 A1
20100031152 Villaron et al. Feb 2010 A1
20100037140 Penner et al. Feb 2010 A1
20100037151 Ackerman et al. Feb 2010 A1
20100058201 Harvey et al. Mar 2010 A1
20100097331 Wu Apr 2010 A1
20100114691 Wu et al. May 2010 A1
20100114991 Chaudhary et al. May 2010 A1
20100131868 Chawla et al. May 2010 A1
20100138756 Saund et al. Jun 2010 A1
20100149307 Iyer et al. Jun 2010 A1
20100174993 Pennington et al. Jul 2010 A1
20100201707 Rasmussen et al. Aug 2010 A1
20100235216 Hehmeyer et al. Sep 2010 A1
20100235763 Massand Sep 2010 A1
20100241968 Tarara et al. Sep 2010 A1
20100251140 Tipirneni Sep 2010 A1
20100268705 Douglas et al. Oct 2010 A1
20100279266 Laine et al. Nov 2010 A1
20100306004 Burtner et al. Dec 2010 A1
20100306018 Burtner et al. Dec 2010 A1
20100312706 Combet et al. Dec 2010 A1
20100324963 Gupta et al. Dec 2010 A1
20110022967 Vijayakumar et al. Jan 2011 A1
20110105092 Felt et al. May 2011 A1
20110107241 Moore May 2011 A1
20110113348 Twiss et al. May 2011 A1
20110113351 Phillips May 2011 A1
20110137894 Narayanan et al. Jun 2011 A1
20110154180 Evanitsky et al. Jun 2011 A1
20110161130 Whalin et al. Jun 2011 A1
20110167036 Liebman Jul 2011 A1
20110185288 Gupta et al. Jul 2011 A1
20110212430 Smithmier et al. Sep 2011 A1
20110239142 Steeves et al. Sep 2011 A1
20110282871 Seefeld et al. Nov 2011 A1
20110289142 Whalin et al. Nov 2011 A1
20110289433 Whalin et al. Nov 2011 A1
20110295879 Logis et al. Dec 2011 A1
20120023418 Frields et al. Jan 2012 A1
20120050197 Kemmochi Mar 2012 A1
20120075337 Rasmussen et al. Mar 2012 A1
20120078708 Taylor et al. Mar 2012 A1
20120129347 Yeom et al. May 2012 A1
20120131464 Penner et al. May 2012 A1
20120144325 Mital et al. Jun 2012 A1
20120150577 Berg et al. Jun 2012 A1
20120150863 Fish et al. Jun 2012 A1
20120159347 Fish et al. Jun 2012 A1
20120159355 Fish et al. Jun 2012 A1
20120166985 Friend et al. Jun 2012 A1
20120179980 Whalin et al. Jul 2012 A1
20120179981 Whalin et al. Jul 2012 A1
20120233543 Vagell et al. Sep 2012 A1
20130007103 Braun et al. Jan 2013 A1
20130035853 Stout et al. Feb 2013 A1
20130091205 Kotler et al. Apr 2013 A1
20130091440 Kotler et al. Apr 2013 A1
20130091465 Kikin-gil et al. Apr 2013 A1
20130097544 Parker et al. Apr 2013 A1
20130101978 Ahl et al. Apr 2013 A1
20130124978 Horns et al. May 2013 A1
20130132886 Mangini et al. May 2013 A1
20130154946 Sakuramata et al. Jun 2013 A1
20130211980 Heiferman et al. Aug 2013 A1
20130212494 Heiferman et al. Aug 2013 A1
20130239002 Maloney et al. Sep 2013 A1
20130246903 Mukai Sep 2013 A1
20130263020 Heiferman et al. Oct 2013 A1
20140033068 Gupta et al. Jan 2014 A1
20140207867 Kotler et al. Jul 2014 A1
20140317561 Robinson et al. Oct 2014 A1
20150127628 Rathod May 2015 A1
Foreign Referenced Citations (45)
Number Date Country
1551567 Dec 2004 CN
1723431 Jan 2006 CN
1928859 Mar 2007 CN
1992625 Jul 2007 CN
101689188 Mar 2010 CN
101834905 Sep 2010 CN
10003907 Aug 2000 DE
674291 Sep 1995 EP
1478121 Nov 2004 EP
1517260 Mar 2005 EP
1628198 Feb 2006 EP
2316059 May 2011 EP
H04257046 Sep 1992 JP
06062142 Mar 1994 JP
H0784905 Mar 1995 JP
07-261963 Oct 1995 JP
H08161214 Jun 1996 JP
08272578 Oct 1996 JP
H1125076 Jan 1999 JP
2000050226 Feb 2000 JP
2001-022257 Jan 2001 JP
2002149754 May 2002 JP
2004287525 Oct 2004 JP
2004336794 Nov 2004 JP
2005500740 Jan 2005 JP
2005-5352701 Dec 2005 JP
2006-59361 Mar 2006 JP
2006163732 Jun 2006 JP
4721663 Jul 2011 JP
2011-530769 Dec 2011 JP
101015295 Feb 2011 KR
2005 139 793 Jun 2007 RU
2312390 Dec 2007 RU
2324987 May 2008 RU
200615840 May 2006 TW
9428480 Dec 1994 WO
02061682 Aug 2002 WO
2005098630 Oct 2005 WO
2006100475 Sep 2006 WO
2006124140 Nov 2006 WO
2006124137 Nov 2006 WO
2007092470 Aug 2007 WO
2009087999 Jul 2009 WO
2010014294 Feb 2010 WO
2010019349 Feb 2010 WO
Non-Patent Literature Citations (235)
Entry
“Non-Final Office Action Received for U.S. Appl. No. 13/361,009”, dated Apr. 14, 2014, 44 Pages.
“Office Action Issued in Malaysia Patent Application No. PI 2011000144”, dated Feb. 13, 2015, 3 Pages.
Office Action Received for Chinese Patent Application No. 200980131157.5, dated Jul. 6, 2015, 8 Pages.
Taiwan Office Action and Search Report Received for Patent Application No. 98126585, dated Aug. 4, 2014, 15 Pages.
Notice of Allowance Received for Russian Federation Patent Application No. 2011103151, dated Sep. 4, 2013, Filed Date: Jun. 7, 2009, 18 Pages.
Russian Notice of Allowance dated Jan. 21, 2013 in Application No. 2011105032, 22 pgs.
Office Action dated Jul. 7, 2015, in U.S. Appl. No. 12/184,174, 34 pgs.
“Microsoft Word's Click and Type Feature”, published by SnipTools, Nov. 12, 2003 downloaded Jun. 28, 2015 from http://sniptools.com/vault/microsoft-words-click-and-type-feature; 2 pgs.
Canadian Office Action dated Aug. 18, 2015 in Application No. 2,730,019, 3 pgs.
Korean Notice of Allowance dated Jun. 25, 2015 in Application No. 10-2011-7003276, 2 pgs.
“An Overview of Aabel 3 Features” accessed at: http://www.gigawiz.com/Aabel.html; accessed on Jul. 21, 2010, 19 pages.
“Collaboration within the Telepresence Experience” accessed at: http://www.wrplatinum.com/Downloads/11056.aspx; published Jan. 2010, 11 pages.
“Content Applications”, Products—Content Applications, http://web.archive.org/web/20030810211219/www.documentum.com/products/content_a . . . , Aug. 10, 2003, 2 pages.
“CounterPoint: A Zooming Presentation Tool”; http://web.archive.org/web/20050205082738/www.cs.umd.edu/hcil/counterpoint/, Archive.org 2005 Capture, 3 pgs.
“Create treemaps using easy drag and drop interactions” accessed at: http://www.magnaview.nl/treemap/; accessed on Jul. 21, 2010, 1 page.
“CSS Max-width Property” by W3Schools, archived by Internet Archive WaybackMachine Jun. 8, 2007, downloaded Nov. 16, 2012; 1 pg.
“Delivering format transformation and analysis for all content,” EMC Documentum Content Transformation Services, Copyright 2006, 4 pages.
“First Examination Report Received in Australian Patent Application No. 2009282364”, dated Mar. 17, 2014, Filed Date: Jul. 19, 2009, 3 Pages.
“Microsoft Office Picture Manager Basics” Nov. 8, 2006, 4 pages.
“Microsoft Office Picture Manager,” Microsoft Office Picture Manager accessed at: http://en.wikipedia.org/wiki/Microsoft_Office_Picture_Manager; accessed on Dec. 13, 2007, 2 pages.
“Office Action and Search Report Received for Taiwan Patent Application No. 98126585”, dated Aug. 4, 2014, 15 Pages.
“Office Action Received in Japanese Patent Application No. 2011-523026”, dated Mar. 7, 2014, Filed Date: Jul. 19, 2009, 4 Pages.
“SpanSoft,” Software from SpanSoft at Download-By.Net, copyright 2006, 4 pages.
“The Beginner's Guide to Data Visualization” accessed at: http://www.tableausoftware.com/beginners-data-visualization; accessed on Jul. 21, 2010, 6 pages.
“The Platinum Experience of Collaboration—CollaboratorHYPERMAX”, accessed at: http://www.businessoctane.com/group_telepresence.php; accessed on Jul. 16, 2010, 7 pages.
“What is Slide Librarian,” Slide Librarian, Current Version 2.4; accessed at: http://www.spansoft.org/slide_rt.htm; accessed on Dec. 7, 2007, 3 pages.
Chilean Office Action Summary dated Aug. 17, 2012 in Appln No. 282-2011.
Chinese Fifth Office Action dated May 30, 2014 in Appln No. 200980131157.5, 9 pgs.
Chinese Fourth Office Action dated Nov. 21, 2013 in Appln No. 200980137757.5, 11 pgs.
Chinese Office Action dated Aug. 31, 2012 in Appln No. 200980131157.5.
Chinese Office Action dated Nov. 16, 2012 in Appln No. 200980131705.4.
Chinese Second Office Action dated Jan. 30, 2013 in Appln No. 200980131157.5.
Chinese Third Office Action dated Jul. 23, 2013 in Appln No. 200980137757.5, 8 pgs.
Davis et al., “Collaboration within the Telepresence Experience” accessed at: http://www.wrplatinum.com/Downloads/11056.aspx; published Jan. 2010, 11 pages.
Deneba Systems, Inc., Canvas Tips and Techniques, © 1995-2002, 9 pages; http://www.acdamerica.com/support-canvas/tutorials/presentation.pdf.
Dontcheva et al., v4v: a View for the Viewer, © 2005 AIGA, cover page plus 8 pages; http://research.microsoft.com/˜sdrucker/papers/v4v.pdf.
Drucker et al., Comparing and Managing Multiple Versions of Slide Presentations, USIST'06, Oct. 15-18, 2006, © 2005 ACM 1-59593-313-1/06/0010; 10 pages, http://research.microsoft.com/˜sdrucker/papers/fp214-DruckerFinalSnriall.pdf.
EP Examination Report in EP Application No. 06759316.0 dated Dec. 28, 2011, 6 pages.
EP Supplemental Search Report in EP Application No. 09803312.9 dated Jul. 7, 2011, 6 pages.
Gallegos et al.; “CounterPoint User Manual” downloaded from archive Org 2005 capture, http://web.archive.org/web/20050205082738/www.cs.umd.edu/hcil/counterpoint/; 21 pages.
GeoTime, accessed at: http://www.geotime.com/Product/GeoTime-(1)/Features---Benefits.aspx; accessed on Jul. 19, 2010, 7 pages.
Good et al.; “CounterPoint: Creating Jazzy Interactive Presentations”—HCIL Tech Report #2001-03, 9 pages.
Grass Roots Software Freepath-Edu Nonlinear Presentation Software, accessed website Aug. 14, 2008,3 pages; http://www.fullcompass.com/product/233150.html.
Hewagamage et al.; Interactive Visualization of Spatiotemporal Patterns Using Spirals on a Geographical Map—accessed at: http://ieeexplore.ieee.org/stamp/stamp.jsp?arnumber=00795916; published 1999, 8 pages.
International Search Report in Application No. PCT/US2006/17725, dated Jul. 5, 2007, 8 pages.
International Search Report in Application No. PCT/US2009/046529 dated Nov. 30, 2009, 11 pages.
International Search Report in Application No. PCT/US2009/051090 dated Jan. 29, 2010, 12 pages.
Izadi et al., “Dynamo: A public interactive surface supporting the cooperative sharing and exchange of media” accessed at: http://hci.stanford.edu/publications/2007/range-wip-final.pdf; published Apr. 2007, 10 pages.
Japanese Notice of Rejection dated Sep. 20, 2013 in Appln No. 2011-523026.
Japanese Office Action Received for Patent Application No. 2011-523026, dated Nov. 5, 2014, 4 Pages.
Kan, Min-Yen, SlideSeer: A Digital Library of Aligned Document and Presentation Pairs, Copyright 2006, 10 pages, http://www.comp.nus.edu.sg/.about.kanmy/papers/jcd12004.pdf.
Keynote '08 User's Guide, Apple Inc. © 2008, 204 pages, http://manuals.info.apple.com/en/Keynote08_UserGuide.pdf.
Little, J. Ambrose; High-End Business Intelligence with Data Visualization for WPF 4, accessed at: http://www.codeproject.com/KB/showcase/DataVisualizationWPF4.aspx; published Jun. 29, 2010, 7 pages.
Microsoft Releases First Beta of “Office 11”: Next Version of Office to Connect People, Information and Business Processes, Oct. 2, 2002, 1 page.
Moran et al., “Tailorable Domain Objects as Meeting Tools for an Electronic Whiteboard” accessed at: http://www.fxpal.com/people/chiu/paper-mvc-CSCW98.pdf; published1998, 10 pages.
Moscovich et al., Customizable Presentations, accessed website Aug. 14, 2008, 5 pages; http://www.cs.brown.edu/people/tm/papers/cpresentations.pdf.
Nelson, John; Just Around the Corner: Visual Fusion 4.5, accessed at: http://www.idvsolutions.com/press_newsletter_vfx45_silverlight.aspx; published Sep. 30, 2009, 6 pages.
Office Action dated Aug. 11, 2014, in U.S. Appl. No. 12/184,174, 50 pgs.
Office Action dated Nov. 20, 2012, in U.S. Appl. No. 12/184,174.
Office Action dated Sep. 25, 2013, in U.S. Appl. No. 12/184,174.
Photodex Corporation, ProShow Producer Feature Overview, © 2008, 2 pages; http://www.photodex.com/products/producer/features.html.
PresenterNet.com: “PresenterNet Product Overview”—accessed at URL:http://web.archive.org/web/20050105035936/http://www.presenternet.com/html/products.php; posted Jan. 6, 2005, 3 pages.
U.S. Office Action in U.S. Appl. No. 12/184,174 dated Mar. 13, 2012, 20 pages.
U.S. Appl. No. 13/271,148, filed Oct. 11, 2011 entitled “Interactive Visualization of Multiple Software Functionality Content Items”.
U.S. Appl. No. 13/253,839, filed Oct. 5, 2011 entitled “Multi-User and Multi-Device Collaboration”.
U.S. Appl. No. 13/253,886, filed Oct. 5, 2011 entitled “Workspace Collaboration Via a Wall-Type Computing Device”.
U.S. Appl. No. 13/272,832, filed Oct. 13, 2011 entitled “Authoring of Data Visualizations and Maps”.
University of Maryland, CounterPoint: A Zooming Presentation Tool, accessed website Aug. 14, 2008, 2 pages; http://www.cs.umd.edu/hcil/counterpoint.
U.S. Final Office Action in U.S. Appl. No. 12/184,174 dated Sep. 6, 2011, 25 pages.
U.S. Final Office Action in U.S. Appl. No. 12/189,583 dated Mar. 11, 2011, 14 pages.
U.S. Non-Final Office Action in U.S. Appl. No. 12/184,174 dated Feb. 4, 2011, 19 pages.
U.S. Non-Final Office Action in U.S. Appl. No. 12/189,583 dated Sep. 24, 2010, 25 pages.
Visualize and Map SalesForce Leads with SpatialKey—accessed at: http://www.spatialkey.com/support/tutorials/visualize-and-map-salesforce-leads-with-spatialkey-part-ii/; accessed on Jul. 19, 2010, 8 pages.
Welcome to PowerPoint 2007, accessed 2008, 20 pages, http://www.computerbook.nl/pdf/9780470040591.pdf.
Wempen, F., “PowerPoint 2007 Bible”; Feb. 27, 2007, excerpt, 27 pages.
Weverka, “PowerPoint 2007 All-in-One Desk Reference for Dummies”—Wiley Publishing, Jan. 2007, 8 pages.
ZuiPrezi Ltd.; “ZuiPrezi Nonlinear Presentation Editor”; http://zuiprezi.kibu.hu/; 2007; 2 pgs.
Chinese Sixth Office Action Received for Chinese Patent Application No. 200980131157.5, dated Dec. 11, 2014, 9 Pages.
“Japanese Office Action Issued in Japanese Patent Application No. 2011-523026”, dated Dec. 22, 2015, 8 Pages.
“Japanese Office Action Issued in Japanese Patent Application No. 2015-039999”, dated Jan. 27, 2016, 6 Pages.
Office Action dated Mar. 3, 2016, in U.S. Appl. No. 12/184,174, 27 pgs.
“Office Action Issued in Japanese Patent Application No. 2016-147342”, dated Aug. 28, 2017, 7 Pages.
Chilean Office Action dated Oct. 26, 2016, in Application 282-2011, 2 pgs.
Office Action dated Dec. 1, 2016, in U.S. Appl. No. 12/184,174, 26 pgs.
The Screen Capture Tool by Help and Manual, archived Mar. 13, 2006 by the Internet Wayback Machine, downloaded Nov. 28, 2016 from https://web.archive.org/web/20060313150929/http://www.helpandmanual.com/help/help_toc.html?hm_advanced_tools_capture.htm.
Office Action Issued in European Patent Application No. 09803312.9, dated Feb. 17, 2017, 7 Pages.
Office Action dated Jul. 12, 2017, in U.S. Appl. No. 12/184,174, 18 pgs.
“Search Report Issued in European Patent Application No. 09807033.7”, dated Dec. 6, 2017, 9 Pages.
“Adobe Connect”, Retrieved From https://en.wikipedia.org/wiki/Adobe_Connect, Sep. 16, 2010, 3 Pages.
“Adobe ConnectNow”, Retrieved From https://web.archive.org/web/20101031034349/http://www.adobe.com/acom/connectnow/, Oct. 2010, 10 Pages.
“An Overview of Aabel3 Features”, Retrieved From: https://web.archive.org/web/20101112054102/http://www.gigawiz.com/Aabel.html, Jul. 21, 2010, 19 Pages.
“Aquatic Sugar: The Children's Interface, Translated for Adults”, Retrieved From http://www.olpcnews.com/software/operating_system/aquatic_sugar_childrens_interface.html, Nov. 7, 2007, 5 Pages.
“Cisco Context-Aware Mobility Solution: Presence Applications”, Retrieved From https://web.archive.org/web/20110810211819/http://www.cisco.com/en/US/solutions/collateral/ns340/ns394/ns348/ns788/brochure_c22-497557.html, Sep. 7, 2010, 5 Pages.
“Datapoint—Version 1.1”, Retrieved From: http://www.filedudes.com/DataPoint-download-20853.html, May 22, 2005, 2 Pages.
“Description for SharePoint Meeting Manager”, Retrieved From http://www.softpicks.net/software/Business/Project-Management/SharePoint-Meeting-Manaaer-47146.htm, Jul. 27, 2009, 2 Pages.
“Free PhotoMesa 3.1.2 (Windows)”, Retrieved From https://web.archive.org/web/20071209231951/http://www.windsorinterfaces.com/photomesa.shtml, Dec. 2007, 3 Pages.
“GoToMeeting”, Retrieved From https://web.archive.org/web/20101022044223/http://www.gotomeeting.com/fec/online_meeting, 2010, 1 Page.
“Live Meeting”, Published in Microsoft Corporation, Jan. 2005, pp. 1-17.
“Meet mimio—The Digital Meeting Assistant”, In White Paper, May 1999, 10 Pages.
“Meeting Center Using Video in Your Meetings”, Retrieved From https://web.archive.org/web/20130512141342/http://www.oucs.ox.ac.uk/webex/Windows/Video.pdf, May 13, 2009, 2 Pages.
“Meeting Management Software”, Retrieved From http://workingsmarter.typepad.com/my_weblog/2004/12/meeting_managem.html, Dec. 10, 2004, 2 Pages.
“Microsoft Office Communicator 2007 Gelling Started Guide”, Retrieved From http://www.ecu.edu/itcs/services/customcf/documents/communicator/Communicator2007-GettingStarted.pdf, Jul. 2007, 77 Pages.
“Mindshift Innovation”, Retrieved From http://mindshiftinnovation.blogspot.com/2007/09/seadragon.html, Oct. 4, 2007, 2 Pages.
“Online Calendar & Group Scheduling”, In MOSAIC Technologies, Retrieved on Apr. 24, 2009, 4 Pages.
“Final Office Action Issued in U.S. Appl. No. 11/260,515”, dated Dec. 11, 2009, 19 Pages.
“Final Office Action Issued in U.S. Appl. No. 11/260,515”, dated Feb. 24, 2011, 15 Pages.
“Non-Final Office Action Issued in U.S. Appl. No. 11/260,515”, dated Sep. 30, 2010, 18 Pages.
“Non-Final Office Action Issued in U.S. Appl. No. 11/260,515”, dated Mar. 3, 2009, 16 Pages.
“Final Office Action Issued in U.S. Appl. No. 12/472,101”, dated Mar. 28, 2012, 20 Pages.
“Non-Final Office Action Issued in U.S. Appl. No. 12/472,101”, dated Oct. 5, 2011, 16 Pages.
“Final Office Action Issued in U.S. Appl. No. 12/965,965”, dated Nov. 8, 2012, 12 Pages.
“Non-Final Office Action Issued in U.S. Appl. No. 12/965,965”, dated Dec. 20, 2013, 16 Pages.
“Non-Final Office Action Issued in U.S. Appl. No. 12/965,965”, dated Jun. 4, 2012, 12 Pages.
“Final Office Action Issued in U.S. Appl. No. 12/968,332”, dated Aug. 1, 2013, 19 Pages.
“Non-Final Office Action Issued in U.S. Appl. No. 12/968,332”, dated Jul. 23, 2012, 19 Pages.
“Office Action Issued in U.S. Appl. No. 12/968,332”, dated Dec. 5, 2013, 20 Pages.
“Non-Final Office Action Issued in U.S. Appl. No. 13/253,886”, dated Apr. 11, 2013, 13 Pages.
“Final Office Action Issued in U.S. Appl. No. 13/272,832”, dated Dec. 30, 2013, 18 Pages.
“Non-Final Office Action Issued in U.S. Appl. No. 13/272,832”, dated Aug. 12, 2013, 16 Pages.
“Office Action Issued in Japanese Patent Application No. 2011-523026”, dated Mar. 7, 2014, 4 Pages.
“Office Action Issued in Japanese Patent Application No. 2016-147342”, dated Apr. 24, 2018, 6 Pages.
“First Office Action Issued in Indian Patent Application No. 690/CHENP/2011”, dated May 30, 2018, 7 Pages.
Adams, et al., “Distributed Research Teams: Meeting Asynchronously in Virtual Space”, In Journal of Computer Mediated Communication, vol. 4, Issue 4, Jun. 1, 1999, 17 Pages.
Bell, et al., “Sensory Semantic User Interfaces (SenSUI) (position paper)”, In Proceedings of the 2nd International Conference on Semantic Sensor Networks, vol. 522, Oct. 20, 2009, 14 Pages.
Bunzel, Tom, “Using Quindi Meeting Capture”, Retrieved From http://www.informit.com/articles/article.aspx?p=170392&seqNum=220, Sep. 1, 2006, 3 Pages.
Derthick, et al., “An Interactive Visualization Environment for Data Exploration”, In Proceedings of Knowledge Discovery in Databases, Aug. 1997, 10 Pages.
Fernando, et al., “Narrowcasting Attributes for Presence Awareness in Collaborative Virtual Environments”, In the Sixth IEEE International Conference on Computer and Information Technology, Sep. 2006, 6 Pages.
Fruchter, Renate, “Brick & Bits & Interaction (BBI)”, Retrieved From http://pbl.stanford.edu/Research/ResearchIW.html, 2001, 4 Pages.
Geyer, et al., “Activity Explorer: Activity-centric Collaboration from Research to Product”, In Proceedings of IBM Systems Journal, vol. 45, Issue: 4, 2006, 23 Pages.
Greenberg, et al., “Human and Technical Factors of distributed Group Drawing Tools”, In Interacting with Computers, vol. 4, Issue 3, Dec. 1, 1992, pp. 364-392.
Hupfer, et al., “Introducing Collaboration into an Application Development Environment”, In Proceedings of the ACM Conference on Computer Supported Cooperative Work, Nov. 6, 2004, 4 Pages.
Ionescu, et al., “Workspace Navigator: Tools for Capture, Recall and Reuse using Spatial Cues in an Interactive Workspace”, In Stanford Technical Report, TR2002-04, 2002, 16 Pages.
Ju, et al., “Where the Wild Things Work: Capturing Shared Physical Design Workspaces”, In Proceedings of the ACM Conference on Computer Supported Cooperative Work, Nov. 6, 2004, pp. 533-541.
Kang, et al., “Effects of Lateral Charge Spreading on the Reliability of TANOS (TaN/AlO/SiN/Oxide/Si) NAND Flash Memo”, IEEE 45th Annual International Reliability Physics Conference, Jan. 2007, 4 Pages.
Karlson, et al., “Courier: A Collaborative Phone-Based File Exchange System”, In Proceedings of TechReport, Jan. 1, 2008, 17 Pages.
Kim, et al., “CMPT 481/811—SmartMeeting: Automatic Meeting Recording System”, Retrieved From http://www.cs.usask.ca/grads/hyk564/homePage/811/CMPT%20811%20final.doc, 2004, 7 Pages.
Lai, et al., “Fluorinated ALD Al203 Gate Dielectrics by CF4 Plasma”, In Proceedings of 2005 International Semiconductor Device Research Symposium, Dec. 7, 2005, 2 Pages.
Lai, et al., “Study of the Erase Mechanism of MANOS (Metal/Al2O3/SiN/SiO2/Si) Device”, In IEEE Electron Device Letters, vol. 28, Issue 7, Jul. 2007, 3 Pages.
Lee, et al., “A Novel SONOS Structure of Si02/SiN/Al2O3 with TaN Metal Gate for Multi-Giga Bit Flash Memories”, In International Electron Devices Meeting, Dec. 8, 2003, 4 Pages.
Lu, et al., “Non-Volatile Memory Technology—Today and Tomorrow”, In Proceedings of the 13th Physical and Failure Analysis of Integrated Circuits, Jul. 3, 2006, 6 Pages.
Mitrovic, et al., “Adaptive User Interface for Mobile Devices”, In International Workshop on Design, Specification, and Verification of Interactive Systems, Jun. 12, 2002, 15 Pages.
Peddemors, et al., “Presence, location and Instant Messaging in a Context-Aware Application Framework”, In the 4th International Conference on Mobile Data Management (MDM2003), Dec. 16, 2002, 6 Pages.
Piekarski, et al., “Through-Walls Collaboration”, In IEEE Pervasive Computing, vol. 8, Issue 3, Jul. 17, 2009, 8 Pages.
Rudnicky, et al., “Intelligently Integrating Information from Speech and Vision to Perform Light-weight Meeting Understanding”, In International Workshop on Multimodal Multiparty Meeting Processing, Oct. 2005, pp. 79-84.
Shaw, Glenna R., “Create Pan and Zoom Effects in PowerPoint”, Retrieved From: https://support.office.com/en-us/article/create-pan-and-zoom-effects-in-powerpoint-689715d0-6787-4d40-9872-99d5b3087946, 2007, 10 Pages.
Watson, Richard, “What is Mobile Presence?”, Retrieved From: http://technews.tmcnet.com/reseller/topics/unified-communications/articles/54033-what-mobile-presence.htm, Apr. 10, 2009, 4 Pages.
Werle, et al., “Active Documents Supporting Teamwork in a Ubiquitous Computing Environment”, In PCC Workshop, 2001, 4 Pages.
Yu, et al., “Who Said What When? Capturing Important Moments of a Meeting”, In CHI'10 Extended Abstracts on Human Factors in Computing Systems, Apr. 10, 2010, 7 Pages.
Zenghong, et al., “Context Awareness and Modeling in Self-Adaptive Geo-Information Visualization”, Retrieved From https://icaci.org/files/documents/ICC_proceedings/ICC2009/html/nonref/17_1.pdf, Aug. 30, 2010, 13 Pages.
Wen, Xin, “Microsoft.NET Strategy-All-Out MSN Approaches (Part I), MSN Explorer, A Beautiful Butterfly that Flies into the Window”, In Publication of China Academic Journal Electronic Publishing House, Jan. 1994, pp. 49-52.
Wen, Xin, “Microsoft.NET Strategy-All-out MSN Approaches (Part II), Smoke of Gunpowder Rises Again in MSN Messenger Instant Messaging Market”, In Publication of the China Academic Journal Electronic Publishing House, Jan. 1994, pp. 49-52.
“Full Analysis of New Face, Notes/Domino R5.05 Sametime 2.0”, In Notes Domino Magazine of Softbank Publishing Inc., vol. 12, Issue 50, Dec. 1, 2000, pp. 73-82.
“Ketchum Portal Uses Plumtree, eRoom Technology to Collaborate With Staff, Clients”, In Publication of I/S Analyzer Case Studies, United Communications Group, vol. 40, Issue 1, Jan. 2001, pp. 7-10.
“Lotus Notes (R5) Client—Calendaring, Personal Calendar”, Retrieved From: http://web.archive.org/web/20011102175413/http://www.rhsmith.umd.edu/tr/LNR5Cal.htm, Retrieved Date: Nov. 2, 2001, 7 Pages.
“Screen Shots”, In Lotus Notes 6, Screenshots of Release 6.02 CFI, Mail, Calendar interface, Jun. 9, 2003, 5 Pages.
“Screen Shots of Microsoft Outlook”, Jan. 1999, 3 Pages.
“Windows NetMeeting”, Retrieved From: http://web.archive.org/web/20030421050139/http://publish.edu.uwo.ca/rick.kitto/resource_files/Housekeeping/Netmeeting.PDF, Apr. 21, 2003, 11 Pages.
“Office Action Issued in European Patent Application No. 04013149.2”, dated May 30, 2005, 3 Pages.
“Office Action Issued in European Patent Application No. 06101313.2”, dated Apr. 17, 2007, 1 Page.
“Office Action Issued in European Patent Application No. 06110218.2”, dated Dec. 13, 2007, 3 Pages.
“Office Action Issued in European Patent Application No. 06110218.2”, dated Jul. 15, 2010, 4 Pages.
“Office Action Issued in European Patent Application No. 06110218.2”, dated Sep. 13, 2011, 4 Pages.
“Office Action Issued in European Patent Application No. 06110218.2”, dated Jul. 16, 2013, 3 Pages.
“Office Action Issued in European Patent Application No. 06110218.2”, dated Mar. 12, 2007, 4 Pages.
“Office Action Issued in European Patent Application No. 06110218.2”, dated Dec. 17, 2008, 5 Pages.
“Search Report Issued in European Patent Application No. 06110218.2”, dated Jul. 24, 2006, 7 Pages.
“Office Action Issued in European Patent Application No. 09807033.7”, dated Nov. 16, 2018, 7 Pages.
“Final Office Action Issued in U.S. Appl. No. 10/607,780”, dated Feb. 7, 2008, 15 Pages.
“Non Final Office Action Issued in U.S. Appl. No. 10/607,780”, dated Jun. 18, 2007, 14 Pages.
“Final Office Action Issued in Japanese Patent Application No. 2011-523026”, dated Nov. 5, 2014, 4 Pages.
“Non Final Office Action Issued in U.S. Appl. No. 11/073,404”, dated Oct. 2, 2008, 8 Pages.
“Final Office Action Issued in U.S. Appl. No. 11/074,885”, dated Jun. 23, 2009, 14 Pages.
“Non Final Office Action Issued in U.S. Appl. No. 11/074,885”, dated May 2, 2008, 8 Pages.
“Non Final Office Action Issued in U.S. Appl. No. 11/074,885”, dated Nov. 28, 2008, 15 Pages.
“Final Office Action Issued in U.S. Appl. No. 11/074,972”, dated Dec. 24, 2008, 18 Pages.
“Non Final Office Action Issued in U.S. Appl. No. 11/074,972”, dated Jul. 8, 2009, 22 Pages.
“Non Final Office Action Issued in U.S. Appl. No. 11/074,972”, dated Jun. 10, 2008, 15 Pages.
“Final Office Action Issued in U.S. Appl. No. 11/166,771”, dated Sep. 11, 2008, 23 Pages.
“Non Final Office Action Issued in U.S. Appl. No. 11/166,771”, dated Jan. 29, 2008, 17 Pages.
“Non Final Office Action Issued in U.S. Appl. No. 11/166,910”, dated Mar. 26, 2008, 15 Pages.
“Final Office Action Issued in U.S. Appl. No. 11/167,065”, dated Dec. 27, 2007, 10 Pages.
“Non Final Office Action Issued in U.S. Appl. No. 11/167,065”, dated Sep. 22, 2008, 10 Pages.
“Non Final Office Action Issued in U.S. Appl. No. 11/167,065”, dated Jul. 2, 2007, 10 Pages.
“Non Final Office Action Issued in U.S. Appl. No. 12/472,101”, dated Sep. 16, 2014, 10 Pages.
“Final Office Action Issued in U.S. Appl. No. 12/558,507”, dated Jun. 3, 2015, 20 Pages.
“Final Office Action Issued in U.S. Appl. No. 12/558,507”, dated Feb. 28, 2014, 17 Pages.
“Final Office Action Issued in U.S. Appl. No. 12/558,507”, dated Oct. 2, 2012, 17 Pages.
“Final Office Action Issued in U.S. Appl. No. 12/558,507”, dated Jul. 14, 2016, 18 Pages.
“Final Office Action Issued in U.S. Appl. No. 12/558,507”, dated Dec. 15, 2017, 20 Pages.
“Final Office Action Issued in U.S. Appl. No. 12/558,507”, dated Nov. 2, 2018, 20 Pages.
“Non Final Office Action Issued in U.S. Appl. No. 12/558,507”, dated Dec. 23, 2015, 17 Pages.
“Non Final Office Action Issued in U.S. Appl. No. 12/558,507”, dated Nov. 6, 2014, 18 Pages.
“Non Final Office Action Issued in U.S. Appl. No. 12/558,507”, dated May 8, 2012, 14 Pages.
“Non Final Office Action Issued in U.S. Appl. No. 12/558,507”, dated Aug. 21, 2013, 14 Pages.
“Non Final Office Action Issued in U.S. Appl. No. 12/558,507”, dated Jun. 28, 2018, 21 Pages.
“Non Final Office Action Issued in U.S. Appl. No. 12/558,507”, dated Feb. 24, 2017, 18 Pages.
“Final Office Action Issued in U.S. Appl. No. 12/965,965”, dated Jun. 5, 2014, 13 Pages.
“Final Office Action Issued in U.S. Appl. No. 12/965,965”, dated Mar. 11, 2015, 17 Pages.
“Non Final Office Action Issued in U.S. Appl. No. 12/965,965”, dated Oct. 2, 2014, 14 Pages.
“Final Office Action Issued in U.S. Appl. No. 12/968,332”, dated Jul. 17, 2014, 23 Pages.
“Non Final Office Action Issued in U.S. Appl. No. 12/968,332”, dated Oct. 9, 2014, 23 Pages.
“Non Final Office Action Issued in U.S. Appl. No. 13/253,886”, dated Aug. 14, 2014, 15 Pages.
“Final Office Action Issued in U.S. Appl. No. 13/271,148”, dated Jul. 17, 2015, 18 Pages.
“Non Final Office Action Issued in U.S. Appl. No. 13/271,148”, dated Dec. 4, 2014, 31 Pages.
“Final Office Action Issued in U.S. Appl. No. 13/272,832”, dated Apr. 20, 2015, 66 Pages.
“Non Final Office Action Issued in U.S. Appl. No. 13/272,832”, dated Oct. 31, 2014, 17 Pages.
“Non Final Office Action Issued in U.S. Appl. No. 14/225,234”, dated Jun. 17, 2016, 11 Pages.
“Non Final Office Action Issued in U.S. Appl. No. 14/225,234”, dated Jul. 18, 2014, 5 Pages.
“First Office Action Issued in Chinese Patent Application No. 200410069436.2”, dated Jun. 8, 2007, 15 Pages.
“Second Office Action Issued in Chinese Patent Application No. 200410069436.2”, dated Oct. 17, 2008, 12 Pages.
“Third Office Action Issued in Chinese Patent Application No. 200410069436.2”, dated Apr. 10, 2009, 10 Pages.
“Office Action Issued in Japanese Patent Application No. 2004-190395”, dated Jun. 15, 2010, 8 Pages.
“Office Action Issued in Japanese Patent Application No. 2006-030252”, dated Aug. 9, 2011, 11 Pages.
“First Office Action Issued in Chinese Patent Application No. 200610003730.2”, dated Sep. 18, 2009, 17 Pages.
“Second Office Action Issued in Chinese Patent Application No. 200610003730.2”, dated Jun. 28, 2010, 7 Pages.
“Third Office Action Issued in Chinese Application No. 200610003730.2”, dated Oct. 27, 2010, 7 Pages.
“Office Action Issued in Russian Patent Application No. 2011103151”, dated May 31, 2013, 5 Pages.
“First Office Action and Search Report Issued in Chinese Patent Application No. 201210376181.9”, dated Nov. 2, 2014, 16 Pages.
“Office Action Issued in Indian Patent Application No. 261/DEL/2006”, dated Mar. 31, 2015, 2 Pages.
“Office Action Issued in Indian Patent Application No. 75/CHENP/2011”, dated Jun. 27, 2018, 6 Pages.
“Office Action Issued in Indian Patent Application No. 998/DEL/2004”, dated May 12, 2015, 2 Pages.
Anderson, Ron, “Far-Flung Firms Will Find ERoom's Workspace a Comfortable Place to Meet”, In Network Computing, vol. 12, Issue 2, Jan. 22, 2001, pp. 34-36.
Callas, Jon, “Identity-Based Encryption with Conventional Public-Key Infrastructure”, Retrieved From: https://web.archive.org/web/20051218070552/http://middleware.internet2.edu/pki05/proceedings/callas-conventional_ibe.pdf, Feb. 18, 2005, 14 Pages.
Curran, Kevin, “Peer-to-Peer Networking Collaboration Within Education”, In Journal of Educational Multimedia and Hypermedia, vol. 11, Issue 1, Nov. 2002, pp. 21-30.
Darrow, Barbara, “Web Services Key to Groove 2.5”, In Publication of CRN, Issue 1018, Oct. 28, 2002, pp. 7-10.
Ewalt, David M., “A New Way of Collaborating-Business Processes”, In Publication of the Information Week, Issue 916, Nov. 25, 2002, pp. 46-48.
Freed, Judy, “Using Microsoft Outlook A Beginner's Guide Email and Calendars”, In Publication of University of North Carolina at Charlotte, Sep. 19, 2002, 22 Pages.
Hiroki, Ito, “Sharing Information and Schedule Without Using a Server, Fully Using P2P Groupware”, In Internet Magazine, Issue 92, Sep. 1, 2002, pp. 132-148.
Jern, et al., “Visual Data Navigators—Collaboratories”, In Proceedings of the 1st International Symposium on 3D Data Processing Visualization and Transmission, Jun. 19, 2002, pp. 66-69.
Marsic, Ivan, “Data-Centric Collaboration for Wired and Wireless Platforms”, In Journal of Computing and Information Technology, vol. 10, Issue 3, Sep. 2002, pp. 151-156.
Menezes, et al., “Identification and Entity Authentication”, In Handbook of Applied Cryptography by CRC Press, Dec. 31, 1997, pp. 385-424.
Takehisa, et al., “Development of APEX Office Application”, In Proceedings of NEC Research and Development, vol. 43, Issue 4, Oct. 2002, pp. 295-299.
Zha, et al., “Web-Based Collaborative Framework and Environment for Designing and Building Robotic Systems”, In Proceedings of the IEEE International Conference on Robotics and Automation, vol. 2, May 11, 2002, pp. 2196-2201.
Zhang, et al., “Anonymous Public-Key Certificates for Anonymous and Fair Document Exchange”, In Proceedings of the IEEE Communications, vol. 147, Issue 6, Dec. 11, 2000, pp. 345-350.
“Non Final Office Action Issued in U.S. Appl. No. 12/558,507”, dated Apr. 19, 2019, 17 Pages.
Related Publications (1)
Number Date Country
20150253941 A1 Sep 2015 US
Continuations (2)
Number Date Country
Parent 13361009 Jan 2012 US
Child 14617659 US
Parent 12189583 Aug 2008 US
Child 13361009 US