HK1218981B - Visualization interface for information object system - Google Patents

Description

Visual interface of information object system

Federally funded research

This application originates in part from research conducted on behalf of the Defense Advanced Research Projects Agency ("DARPA") of the United States Department of Defense in connection with DARPA Subject #SB072-032.

Priority claim

This application claims priority to and the benefit of U.S. Provisional Application Serial No. 61/787,688, filed March 15, 2013, which is incorporated herein by reference in its entirety.

This application also claims priority to and the benefit of U.S. Utility Application Serial No. 14/208,346, filed March 13, 2014, which is incorporated herein by reference in its entirety.

Technical Field

The present disclosure relates to, but is not limited to, visualization interfaces for information object systems.

background

Information is stored on computers in files and other data formats. Various applications can use files or other data formats to display information in a way that is helpful for people to understand. Applications can further display the relationships between separate pieces of information in a way that is helpful for people to understand.

Overview

Various techniques are disclosed for presenting information to a user through a user interface of a client application executed on a client computing device. Data is stored on a collaboration server as a series of information objects. The client application can present the information stored in the series of information objects using any one or more of the methods disclosed herein.

In one embodiment, a non-transitory computer-readable medium embodying a program is provided, the program comprising: code for generating a user interface on a client computing device; code for querying a collaboration server for an information object to be rendered within the user interface on behalf of a user in response to a request to render an information object; code for obtaining form data from the information object received from the collaboration server; and code for rendering the information object within the user interface based at least in part on the form data of the information object. In any one or more embodiments, the program may further comprise code for obtaining an identification of a related information object from the information object; code for querying the collaboration server for the related information object; and code for rendering the related information object within the user interface. In any one or more embodiments, the program may further comprise code for rendering an indication of a relationship between the information object and the related information objects within the user interface. In any one or more embodiments, the program may further comprise code for obtaining modifications to the information object; code for transmitting the modifications to the collaboration server; code for rendering the modified version of the information object within the user interface in response to receiving a first notification from the collaboration server that the modifications are valid; and code for rendering an error message within the user interface in response to receiving a second notification from the collaboration server that the modifications are invalid. In any one or more embodiments, the program may further comprise code for generating a new information object in response to receiving data from a data source; code for creating an information object reference linking the information object to the new information object; and code for transmitting the information object, the new information, and the information object reference to the collaboration server. In any one or more embodiments, a data source includes an electronic device that generates data and transmits the data to a computing device. In any one or more embodiments, an information object includes a unique identifier, attributes, an information object reference, form data, and a function.

In one embodiment, a system is provided that includes a computing device and an application executable on the computing device, the application including: logic for generating a user interface on a client computing device; logic for querying a collaboration server for an information object to be rendered within the user interface on behalf of a user in response to a request to render an information object; logic for obtaining form data from the information object received from the collaboration server; and logic for rendering the information object within the user interface based at least in part on the form data of the information object. In any one or more embodiments, the application may also include logic for obtaining an identification of a related information object from the information object; logic for querying the collaboration server for the related information object; and logic for rendering the related information object within the user interface. In any one or more embodiments, the application may also include logic for rendering an indication of a relationship between the information object and the related information objects within the user interface. In any one or more embodiments, the application may also include logic for obtaining modifications to the information object; logic for sending the modifications to the collaboration server; logic for rendering the modified version of the information object within the user interface in response to receiving a first notification from the collaboration server that the modification is valid; and logic for rendering an error message within the user interface in response to receiving a second notification from the collaboration server that the modification is invalid. In any one or more embodiments, the application may further include logic for generating a new information object in response to receiving data from a data source; logic for creating an information object reference linking the information object to the new information object; and logic for transmitting the information object, the new information, and the information object reference to the collaboration server. In any one or more embodiments, the data source includes an electronic device that generates and transmits the data to the computing device. In any one or more embodiments, the information object includes a unique identifier, attributes, an information object reference, formal data, and a function.

In an embodiment, a method is provided that includes: generating a user interface on a client computing device via a computing device; querying a collaborative server, via the computing device, on behalf of a user, for an information object to be rendered within the user interface in response to a request to render an information object; obtaining, via the computing device, form data from the information object received from the collaborative server; and rendering, via the computing device, the information object within the user interface based at least in part on the form data of the information object. In one or more embodiments, the method further includes: obtaining, via the computing device, an identification of a related information object from the information object; querying the collaborative server, via the computing device, for the related information object; and rendering, via the computing device, the related information object within the user interface. In one or more embodiments, the method further includes rendering, via the computing device, an indication of a relationship between the information object and the related information objects within the user interface. In one or more embodiments, the method further includes: obtaining, via the computing device, a modification to the information object; sending, via the computing device, the modification to the collaborative server; rendering, via the computing device, a modified version of the information object within the user interface in response to receiving, from the collaborative server, a first notification that the modification is valid; and rendering, via the computing device, an error message within the user interface in response to receiving, from the collaborative server, a second notification that the modification is invalid. In one or more embodiments, the method further comprises: generating, via the computing device, a new information object in response to receiving data from a data source; creating, via the computing device, an information object reference linking the information object to the new information object; and sending, via the computing device, the information object, the new information, and the information object reference to the collaboration server. In one or more embodiments, the information object comprises a unique identifier, attributes, an information object reference, form data, and a function.

BRIEF DESCRIPTION OF THE DRAWINGS

Many aspects of the present disclosure may be better understood with reference to the accompanying drawings. The components in the accompanying drawings are not necessarily to scale, but rather are emphasized to clearly illustrate the principles of the present disclosure. Moreover, in the accompanying drawings, like reference numerals represent corresponding components throughout the several views.

FIG. 1 is a diagram of a networked environment according to various embodiments of the present disclosure.

2 is a diagram of information objects depicted in the networked environment of FIG. 1 , according to various embodiments of the present disclosure.

3A-G are diagrams of examples of user interfaces rendered by a client in the networked environment of FIG. 1 , according to various embodiments of the present disclosure.

4 is a flow diagram illustrating one example of functionality implemented as part of a client application and a collaboration server executing in the networked environment of FIG. 1 , according to various embodiments of the present disclosure.

5 is a flow diagram illustrating one example of functionality implemented as part of a client application and a collaboration server executing in the networked environment of FIG. 1 , according to various embodiments of the present disclosure.

6 is a flow diagram illustrating one example of functionality implemented as part of a client application and a collaboration server executing in the networked environment of FIG. 1 , according to various embodiments of the present disclosure.

7 is a flow diagram illustrating one example of functionality implemented as part of a client application and a collaboration server executing in the networked environment of FIG. 1 , according to various embodiments of the present disclosure.

8 is a flow diagram illustrating one example of functionality implemented as part of a client application and a collaboration server executing in the networked environment of FIG. 1 , according to various embodiments of the present disclosure.

9 is a schematic block diagram providing one example illustration of a computing environment for use in the networked environment of FIG. 1 , according to various embodiments of the present disclosure.

DETAILED DESCRIPTION

Concept maps and mind maps often facilitate better examination of existing knowledge structures, allowing for more rapid identification of misunderstandings or relationships requiring deeper analysis. Computer-based concept mapping tools can enhance higher-quality analysis by creating structured representations of complex conceptual domains. In this manner, using concept maps and mind map presentations, both content creators and consumers are expected to more quickly assess the analytical integrity and value of the information and analysis at hand, and thus determine whether further refinement of the analysis is necessary.

In the following discussion, a general description of the system and its components is provided, followed by a discussion of its operation.

1 , a networked environment 100 is shown according to various embodiments. The networked environment 100 includes a computing environment 103 and a client computing device 106 in data communication with each other via a network 109. The network 109 includes, for example, the Internet, an intranet, an extranet, a wide area network (WAN), a local area network (LAN), a wired network, a wireless network, or other suitable network, or any combination of two or more such networks.

The computing environment 103 may include, for example, a server computer or any other system that provides computing power. Alternatively, the computing environment 103 may utilize multiple computing devices that may be used, for example, arranged in one or more server groups or computer groups or other arrangements. Such computing devices may be located in a single device or may be distributed among many different geographical locations. For example, the computing environment 103 may include multiple computing devices that together may include cloud computing resources, grid computing resources, and/or any other distributed computing arrangement. In some cases, the computing environment 103 may correspond to an elastic computing resource, wherein the assigned capacity of processing, network, storage, or other computing-related resources may change over time.

According to various embodiments, various applications and/or other functions may be executed in the computing environment 103. In addition, various data may be stored in a data repository 111 accessible to the computing environment 103. The data repository 111 may represent a plurality of data repositories 111, as may be appreciated. The data stored in the data repository 111 may be related to the operation of the various applications and/or functional entities described below, for example.

Components executing on computing environment 103 include, for example, collaboration server 113 and other applications, services, processes, systems, engines, or functions not discussed in detail herein. Collaboration server 113 is executed to allow one or more users to create and share one or more information objects 116 and possibly other data.

The data stored in the data repository 111 includes, for example, one or more information objects 116 and possibly other data.

Information objects 116 are data storage objects that are structured to model data based on relationships between individual pieces of information. Thus, an information object 116 may include a set of associations with other information objects 116 to indicate data relationships. For example, a link between two information objects 116 may indicate data dependencies, structural hierarchies, or other associations between the data modeled by two or more information objects 116. Information objects 116 may also be combined and/or derived from other information objects to represent these relationships. Thus, most information objects 116 may be created from or represented by a combination of other information objects 116.

However, some types or categories of information objects 116 may be reserved for specific types of data that cannot be easily represented as a combination of two or more other information objects 116. For example, repeating blocks of data such as images, sound, video, compressed data, and encrypted data may require reserved or unique instances of information objects 116 that act as wrappers for the underlying data. Continuous streams of data, such as a stream of data from a sensor, may also require unique or reserved instances of information objects 116 to represent the streamed data because streamed data has a beginning but not necessarily an end.

Client computing device 106 represents a plurality of client computing devices that can be coupled to network 109. Client computing device 106 may comprise, for example, a processor-based system, such as a computer system. Such a computer system may be embodied in a desktop computer, a laptop computer, a personal digital assistant, a cellular telephone, a smartphone, a set-top box, a music player, a web tablet, a tablet computer system, a game console, an e-book reader, or other devices with similar capabilities. Client computing device 106 may include a display 119. Display 119 may comprise, for example, one or more devices such as a liquid crystal display (LCD) display, a gas plasma-based flat panel display, an organic light emitting diode (OLED) display, an LCD projector, or other types of display devices.

The client computing device 106 can be configured to execute various applications, such as the client application 123 and/or other applications. The client application 123 can be executed in the client computing device 106 to, for example, access network content provided by the computing environment 103 and/or other servers, thereby rendering the user interface 300 on the display 119. To this end, the client application 123 can include, for example, a browser, a dedicated application, etc., and the user interface 300 can include a network page, an application screen, etc. The client computing device 106 can be configured to execute applications other than the client application 123, such as an email application, a social networking application, a word processor, a spreadsheet, and/or other applications.

Additionally, one or more sensors and other data feeds 126 may be in network communication with the collaboration server 113 or the client application 123. Sensors and other data feeds may include any electronic device capable of generating or recording data and transmitting the data to the collaboration server 113. Examples of sensors and other data feeds 126 include accelerometers, temperature sensors or thermostats, video or web cameras, microphones, noise sensors, pressure sensors, gauges, timers, flow meters, light sensors, outputs or results of applications or programs, and other such devices or programs.

While FIG1 depicts a network-centric configuration representing a client-server model, other configurations are not excluded. For example, in some embodiments, the client computing device 106 may be a computing device located within the computing environment 103. In various embodiments, the client application 123 may be located in the computing environment 103 along with the collaboration server 113, but the client application 123 may deliver or render the user interface 300 on the display 119 of the client computing device 106. In other embodiments, the collaboration server 113, the data repository 111, and the client application 123 may all be located on a single computing device, such as the client computing device 106, or a single computer within the computing environment 103.

Next, a general description is provided of the operation of the various components of the networked environment 100. Initially, the client application 123 generates a request for one or more information objects 116 for use in a presentation, report, or similar document.

Upon receiving the requested information object 116, the client application 123 presents the requested information object 116 to the user through the user interface 300. The user may interact with the information object 116 as desired.

For example, a user may select one or more information objects 116 as the basis for a presentation. Each information object 116 may correspond to a slide image or chart within the presentation.

Alternatively, a user can interact with an information object 116 to select a sub-information object 116 or otherwise "drill down" to view underlying data related to the information object 116. For example, a user can select an information object 116 labeled "bacteria." Within the information object 116 labeled "bacteria," a list of bacteria can be provided. Each list corresponds to a sub-information object. If a user selects a sub-information object 116, information related to the sub-information object 116 can be presented to the user, where such information was previously not visible to the user.

In another non-limiting example, a user may choose to create one or more information objects 116 to represent data or information that is not currently in the system. Continuing with the bacteria example, a user may choose to create a new information object 116 related to the "bacteria" information object 116 to represent a recently discovered bacterium. Furthermore, in some embodiments of the present disclosure, the newly created information object 116 may be uploaded to the collaboration server 113 for storage in the data repository 111 for future use by the user or other users.

2 , which shows a depiction of the data structure of an information object 116. Each information object 116 has at least one unique identifier 203 that uniquely identifies a particular instance of the information object 116 within the data repository 111 ( FIG. 1 ). Each information object 116 also includes content 206. Included within the content 206 of an information object 116 may be one or more information object references, such as information object reference 209 a through information object reference 209 n. The content 206 of an information object 116 may also include attributes 213 that describe the information object 116. Additionally, the information object 116 may include form data 216 and a plurality of functions 219.

Unique identifier 203 can be a unique alphanumeric number, such as the result of a cryptographic hash function, or can be a unique number generated by collaboration server 113 ( FIG. 1 ) when information object 116 is created. For example, collaboration server 113 can apply a cryptographic hash function, such as a version of the Secure Hash Algorithm, to information object 116 to generate unique identifier 203. In another example, collaboration server 113 can increment a counter when information object 116 is created and then set unique identifier 203 equal to the value of the counter. In some embodiments, both approaches can be combined to minimize the risk of collisions from the cryptographic hash function or duplicate counter values due to integer overflow errors. For example, a counter can be incremented and the value added to the beginning or appended to the end of the result of the cryptographic hash function to create unique identifier 203.

The content 206 corresponds to data represented by the information object 116, which may include one or more information object references 209a...n and/or one or more attributes 213. Each information object reference 209a...n points to or links to a related information object 223. The related information object 223 may correspond to information that is part of the information object 116 or is related in some way to the information object 223. For example, the information object 116 representing the country "Russia" may have an information object reference 209 that links the information object 116 to the related information 223 corresponding to the city "Moscow." The information object 116 representing "Russia" may also include a second information object reference 209 to a related information object 223 representing a list of countries and a third information object reference 209 to a related information object 223 representing "Communism."

The attributes 213 of an information object 116 represent data stored within the information object 116, which may or may not be directly visible to a user as primary content. The attributes 213 of an information object 116 may include, for example, the username of the user who originally created the information object 116, the username of each user who modified the information object 116, a timestamp recording the creation of the information object 116 and/or the modification of the information object 116, the version of the interface standard supported by the information object 116 for use on the collaboration server 113 ( FIG. 1 ) or the client application 123 ( FIG. 1 ), a language and/or culture identification, and other such data. In some instances, the attributes 213 themselves may be represented by other information objects 116. For example, the username of the creator of an information object 116 may be represented by an information object 116 representing a user account.

The form data 216 corresponds to data necessary to represent or display the information object 116 on the display 119 ( FIG. 1 ). For example, the form data 216 may indicate the size of the information object 116 on the display 119, the position of the information object 116 on the display 119, the transparency value of the information object 116, whether individual related information objects in the related information objects 223 are overlaid on the information object or positioned below the information object on the display 119, and similar data or values. In some examples, the form data 216 may further specify a default manner in which the related information objects 223 are displayed relative to the information object 116 on the display 119.

Functions 219 correspond to programmatic interfaces, methods, or similar mechanisms through which the client application 123 ( FIG. 1 ) or the collaboration server 113 can interact with or otherwise manipulate the information object 116. For example, the functions 219 may include functions for making the information object 116 visible or invisible on the display 119, functions for editing or otherwise modifying the information object, functions for creating a new information object reference 209, or functions for otherwise linking the information object 116 to a related information object 223.

An information object 116 or related information object 223 may also have separate information object references 209 corresponding to the user interface elements represented by the information object, such as a navigation information object 226, a menu area information object 229, and a client device information object 233. For example, a navigation information object 226 may describe or define the structure of a currently selected information object 116 or the relationship of the currently selected information object 116 to other information objects 116. In some embodiments, a menu area information object 229 may describe or define various menus or other components of the user interface 300 ( FIG. 1 ) that can be used to interact with an information object 116, such as to edit, copy, or delete information 116. In some embodiments, a menu area information object 229 may also provide functionality for creating new information objects 116. Additionally, in some embodiments, a client device information object 233 may contain user and system-level settings, such as volume, display brightness, network connection settings, and other settings.

3A , an example user interface 300, designated herein as 300a, of the client application 123 ( FIG. 1 ) executing on the client computing device 106 is shown. As shown, the information object 116a can have other related information objects 116b, 116c, and 116d overlaid on top of the information object 116a, allowing the user to see the relationships between the information objects 116a, 116b, 116c, and 116d. Whichever information object 116 is currently selected by the user or otherwise in focus can have a corresponding navigation information object 226, menu area information object 229, and client computing device information object 233 displayed.

3B , an example user interface 300, herein designated 300 b, of the client application 123 ( FIG. 1 ) executing on the client computing device 106 is shown. On the right, a navigation information object 226 ( FIG. 2 ), herein designated as a navigation bar 226 b, is shown, including a plurality of information objects 116. In this particular user interface 300 b, the information object 116 is selected and displayed in the middle of the screen.

3C , an example user interface 300, designated herein as 300 c, of the client application 123 ( FIG. 1 ) executing on the client computing device 106 is shown. On the right, a navigation information object 226 ( FIG. 2 ), designated herein as 226 c, is shown that includes a plurality of information objects 116. In this particular user interface 300 c, the user selects another information object 116 and the user interface 300 c changes accordingly.

3D , an example user interface 300, designated herein as 300d, of the client application 123 ( FIG. 1 ) executing on the client computing device 106 is shown. This particular user interface 300d illustrates the ability of a user of the client application 123 to associate one or more information objects 116 ( FIG. 1 ) together.

3E , an example user interface 300, herein designated 300e, of a client application 123 ( FIG. 1 ) executing on a client computing device 106 ( FIG. 1 ) is shown. The user interface 300e displays a plurality of information objects 116, wherein each information object 116 includes information regarding one or more topics, each topic being embodied by a corresponding information object 116. In addition, relationships between the information objects 116 are depicted to accurately convey the relationship of the information.

Turning now to FIG3F , an example user interface 300, herein designated 300 f, of a client application 123 ( FIG1 ) executing on a client computing device 106 ( FIG1 ) is shown. The user interface 300 f depicts a presentation of child information objects 116. In this particular example, the user selects the E. coli information object depicted in user interface 300 e ( FIG3E ), which causes the client application 123 to bring the E. coli information object 116 to the forefront of the user interface 300 f. The other information objects 116 move to the background and/or become blurred, removing any focus or otherwise de-emphasizing them to avoid diverting the user's focus from the presented information objects 116.

3G , an example user interface 300, designated herein as 300g, of the client application 123 ( FIG. 1 ) executing on the client computing device 106 is shown. The user interface 300g depicts a user creating one or more information objects 116 ( FIG. 1 ). Such information objects 116 may be stored for future reference or may be used for purposes of creating presentations, reports, or similar documents.

FIG4 illustrates a flow chart that provides one example of the operation of a portion of the client application 123 and the collaboration server 113, according to various embodiments. It should be understood that the flow chart of FIG4 merely provides an example of many different types of functional arrangements that may be used to implement the operation of portions of the client application 123 and the collaboration server 113 as described herein. Alternatively, the flow chart of FIG4 may be viewed as an example of elements of a method implemented in the networked environment 100 ( FIG1 ), according to one or more embodiments.

Beginning with block 403, the client application 123 receives a selection of a "Create New" or similar option indicating that a user wishes to create a new information object 116 (FIG. 2) via the user interface 300 (FIG. 1) of the client application 123. In some implementations, for example, the user may make a selection to create a new information object 116 by interacting with the menu area information object 229 (FIG. 2).

Then, at block 406, the client application 123 creates a new information object 116 locally. In some embodiments, during the upload of the newly created information object 116 to the collaboration server 113, the new information object 116 can be cached locally for immediate use by the client application 123. In some embodiments, the client application 123 can further assign a unique identifier 203 (FIG. 2) to the newly created information object 116 and populate the content 206 (FIG. 2) and form data 216 (FIG. 2) with default values. For example, attributes 213 (FIG. 2) can be automatically populated with the user account information of the user who created the information object, and an information object reference 209 (FIG. 2) can be automatically created to represent the related information object 223 corresponding to the parent or sibling information object 116.

Continuing then to block 409, the client application 123 sends the newly created information object 116 to the collaboration server 113. In some embodiments, the newly created information object 116 may be serialized, for example by calling function 219 ( FIG. 2 ) of the information object 116 to serialize it, and then sending the serialized information object 116 to the collaboration server 113. In various embodiments, the client application 113 may instead send a copy of the unique identifier 203, the content 206, and the form data 216 to the collaboration server 113.

Next, referring to block 413, the collaboration server 113 determines whether the information corresponding to the newly created information object 116 is valid. For example, the collaboration server 113 may check for errors as part of the deserialization process. The collaboration server 113 may check to see if the data is correctly formatted. As another example, the collaboration server 113 may check to determine if the unique identifier 203 of the newly created information object 116 is a duplicate of the unique identifier 203 of an information object 116 that already exists in the data repository 111 ( FIG. 1 ), indicating that the newly created information object 116 is a duplicate or that there is a conflict between the unique identifiers 203 of the two information objects 116 that needs to be resolved. If the information is invalid, execution proceeds to block 446. However, if the information is valid, execution proceeds to block 416.

If execution proceeds to block 446, the collaboration server 113 generates an error message event and sends the error message to the client application 123. The error message may include an error code identifying the type or source of the error, a description of the error, and the cause of the error. In some embodiments, the error message itself may be an information object 116 representing the error and including applicable error information. In various embodiments, the collaboration server 113 may also log the error and any associated error information to a data repository 111 or log file for later analysis.

Moving on to block 416, the collaboration server 113 creates the information object 116 in the data store 111 using the information received from the client application 123. If necessary, the collaboration server 113 also creates any required parent or child information objects and any references or connections between the newly created information object 116 and other existing information objects 116.

Next, referring to block 419, the collaboration server 113 sends a notification to the client application 123 that the information object 116 has been created. This notification may be in the form of a message, an event notification, or other data format. Furthermore, in some embodiments, the collaboration server 113 may mark the newly created information object 116 as currently being modified or as having modification in progress for the newly created information object 116. This may lock the information object 116 while it is being modified or otherwise prevent the information object 116 from being modified by other users, applications, or processes.

Continuing to block 423, the client application 123 receives notification from the collaboration server 113 that an information object 116 has been created. In some embodiments, the notification may also include an indication that the newly created information object 116 is marked for editing or modification. If the newly created information object is marked for editing, the client application 123 may implement modifications to the client or local copy of the information object 116. For example, the client application 123 may mark fields of the newly created information object 116 as editable, implement various menu functions for the information object 116, or take similar actions.

Moving on to block 426, the client application 123 obtains one or more user modifications to the newly created information object 116. In some embodiments, the client application 123 can automatically save the user modifications. For example, the client application 123 can automatically send each change to the collaboration server 113, or the client application 123 can send the changes in batches to the collaboration server 113 on a periodic basis, such as every few minutes, every hour, or some other time period. The client application 123 can also save the changes or modifications to the newly created information object 116 locally on the client computing device 106 ( FIG. 1 ). When the user finishes modifying the newly created information object 116, the final set of changes is sent to the collaboration server 113. In some embodiments, the changes sent can be sent in a file format that records the changes between the copy of the information object 116 stored in the data repository 111 and the copy of the information object 116 stored on the client computing device 106. In various embodiments, the changes may instead be sent as a copy of the information object 116 stored locally on the client computing device 106 to replace the copy of the corresponding information object 116 stored in the data repository 111. In such embodiments, the copy of the information object 116 may be serialized and transmitted to the collaboration server 113.

Next, referring to block 429, the collaboration server 113 determines whether the information corresponding to the modified information object 116 is valid. For example, the collaboration server 113 may check for errors as part of the deserialization process. The collaboration server 113 may check to see if the data is correctly formatted. If the information is invalid, execution proceeds to block 446, described above. However, if the information is valid, execution proceeds to block 433.

Continuing then to block 433, the collaboration server 113 stores the modifications to the information object 116 in the data repository 111. In some embodiments, this may be accomplished by overwriting or replacing a previous copy of the information object 116 stored in the data repository 111. In other embodiments, the content of the information object 116 may be edited or updated rather than overwriting the information object 116 with a new copy or version.

Moving on to block 436, the collaboration server 113 sends a notification to the client application 123 that the update of the information object 116 is complete. The notification may be in the form of a message, an event notification, or other data format. In addition, the collaboration server 113 may mark the newly created information object 116 as editable so that other users or processes waiting to modify the information object 116 can do so.

Continuing with reference to block 439, the client application 123 receives notification that the update or change to the newly created information object 116 is complete. In some implementations, the client application 123 may lock or otherwise prevent the user from modifying the newly created information object 116 upon receiving the notification. Execution then proceeds to block 443, where the client application 123 renders the newly created information object 116.

FIG5 shows a flowchart that provides one example of the operation of a portion of the client application 123 and the collaboration server 113 according to various embodiments. It should be understood that the flowchart of FIG5 merely provides an example of many different types of functional arrangements that can be used to implement the operation of portions of the client application 123 and the collaboration server 113 as described herein. Alternatively, the flowchart of FIG5 can be viewed as an example of elements of a method implemented in the networked environment 100 ( FIG1 ) according to one or more embodiments.

Beginning with block 503, the client application 123 marks the information object 116 as editable. For example, the information object 116 ( FIG. 1 ) may have been locked for editing by the collaboration server 113 by another process or user. Accordingly, the information object 116 cannot be edited by the user of the client application 123 until the collaboration server 113 unlocks the information object 116 and communicates to the client application 123 that the information object 116 is freely editable.

After marking the information object 116 as editable, execution on the client application moves to block 506, where the client application 123 obtains the user's selection of the information object 116 for editing. The user may indicate to the client application 123 that the information object 116 is to be edited, for example, using a mouse click, a touch gesture, or other interaction.

Continuing to block 509 , the client application 123 obtains the unique identifier 203 ( FIG. 2 ) of the information object 116 . Upon obtaining, the client application 123 sends the unique identifier 203 to the collaboration server 113 .

Referring next to block 513, the collaboration server 113 determines whether the unique identifier 203 ( FIG. 2 ) is valid. For example, the collaboration server 113 may determine whether an information object 116 with the unique identifier 203 exists in the data repository 111 ( FIG. 1 ). If not, the collaboration server 113 may generate an error. As another example, the collaboration server 113 may further determine whether the information object 116 in the data repository 111 is an editable information object 116. If not, the collaboration server 113 may generate an error. If the collaboration server 113 determines that the unique identifier 203 is invalid, execution proceeds to block 543. However, if the information is valid, execution proceeds to block 516.

If execution proceeds to block 543, the collaboration server 113 generates an error message event and sends the error message to the client application 123. The error message may include an error code identifying the type or source of the error, a description of the error, and the cause of the error. In some embodiments, the error message itself may be an information object 116 representing the error and including applicable error information. In various embodiments, the collaboration server 113 may also log the error and any associated error information to a data repository 111 or log file for later analysis.

Moving on to block 516, the collaboration server 113 may mark the selected information object 116 as currently being modified or that modification of the selected information object 116 is in progress. This may lock the information object 116 while it is being modified or otherwise prevent the information object 116 from being modified by other users, applications, or processes. After locking the information object 116, the collaboration server 113 then sends a message to the client application 123 that the information object 116 may be edited.

Referring next to block 519, the client application 123 may enable modifications to be made to the client or local copy of the information object 116 in response to receiving the message from the collaboration server 113. For example, the client application 123 may mark fields of the selected information object 116 as editable, enable various menu functions for the information object 116, or take similar actions.

Continuing to block 523, the client application 123 obtains one or more user modifications to the selected information object 116. In some embodiments, the client application 123 can automatically save the user modifications. For example, the client application 123 can automatically send each change to the collaboration server 113, or the client application 123 can send the changes in batches to the collaboration server 113 on a periodic basis, such as every few minutes, every hour, or some other time period. The client application 123 can also save the changes or modifications to the selected information object 116 locally on the client computing device 106 ( FIG. 1 ). When the user finishes modifying the selected information object 116, the final set of changes is sent to the collaboration server 113. In some embodiments, the changes sent can be sent in a file format that records the changes between the copy of the information object 116 stored in the data repository 111 and the copy of the information object 116 stored on the client computing device 106. In various embodiments, the changes can alternatively be sent as a copy of the information object 116 stored locally on the client computing device 106 to replace the copy of the corresponding information object 116 stored in the data repository 111. In such an embodiment, a copy of the information object 116 may be serialized and transmitted to the collaboration server 113 .

Next, referring to block 526, the collaboration server 113 determines whether the information corresponding to the modified information object 116 is valid. For example, the collaboration server 113 may check for errors as part of the deserialization process. The collaboration server 113 may check to see if the data is correctly formatted. If the information is invalid, execution proceeds to block 543, described above. However, if the information is valid, execution proceeds to block 529.

Moving on to block 529, the collaboration server 113 stores the modifications to the information object 116 in the data repository 111. In some embodiments, this may be accomplished by overwriting or replacing a previous copy of the information object 116 stored in the data repository 111. In other embodiments, the content of the information object 116 may be edited or updated rather than overwriting the information object 116 with a new copy or version.

Next, with reference to block 533, the collaboration server 113 sends a notification to the client application 123 that the update to the information object 116 is complete. The notification may be in the form of a message, an event notification, or other data format. In addition, the collaboration server 113 may mark the selected information object 116 as editable so that other users or processes waiting to modify the information object 116 can do so.

Moving on to block 536, the client application 123 receives notification that the update or change to the selected information object 116 is complete. In some implementations, the client application 123 may lock or otherwise prevent the user from modifying the selected information object 116 upon receiving the notification. Execution then continues to block 539, where the client application 123 renders the modified information object 116.

FIG6 shows a flow chart that provides one example of the operation of a portion of the client application 123 and the collaboration server 113 according to various embodiments. It should be understood that the flow chart of FIG6 merely provides an example of many different types of functional arrangements that can be used to implement the operation of portions of the client application 123 and the collaboration server 113 as described herein. Alternatively, the flow chart of FIG6 can be viewed as an example of elements of a method implemented in the networked environment 100 ( FIG1 ) according to one or more embodiments.

Beginning with block 603, the client application 123 receives information or data to be imported into the system. For example, the client application 123 may receive a video file, an image file, a portable document format (PDF) document, a text document, an audio file, or some other type of file.

Then, at block 606, the client application 123 analyzes the file and locally creates an information object 116 based on the file. In some embodiments, during the upload of the newly created information object 116 to the collaboration server 113, the new information object 116 can be cached locally for immediate use by the client application 123. In some embodiments, the client application 123 can further assign a unique identifier 203 (FIG. 2) to the newly created information object 116 and populate the content 206 (FIG. 2) and form data 216 (FIG. 2) with default values. For example, attributes 213 (FIG. 2) can be automatically populated with the user account information of the user who created the information object, and information object references 209 (FIG. 2) can be automatically created to represent related information objects 223 corresponding to the parent or sibling information object 116. Furthermore, in some embodiments, the client application 123 can set the values of certain attributes 209 based on the file and can populate the content 206 and form data 216 with values based at least in part on the imported file.

Continuing then to block 609, the client application 123 sends the newly created information object 116 to the collaboration server 113. In some implementations, the newly created information object 116 may be serialized, for example, by calling function 219 ( FIG. 2 ) of the information object 116 to serialize it and then sending the serialized information object 116 to the collaboration server 113. In various implementations, the client application 113 may instead send a copy of the unique identifier 203, the content 206, and the form data 216 to the collaboration server 113.

Next, referring to block 613, the collaboration server 113 determines whether the information corresponding to the newly created information object 116 is valid. For example, the collaboration server 113 may check for errors as part of the deserialization process. The collaboration server 113 may check to see if the data is correctly formatted. As another example, the collaboration server 113 may check to determine if the unique identifier 203 of the newly created information object 116 is a duplicate of the unique identifier 203 of an information object 116 that already exists in the data repository 111 ( FIG. 1 ), indicating that the newly created information object 116 is a duplicate or that there is a conflict between the unique identifiers 203 of the two information objects 116 that needs to be resolved. If the information is invalid, execution proceeds to block 646. However, if the information is valid, execution proceeds to block 616.

If execution proceeds to block 646, the collaboration server 113 generates an error message event and sends the error message to the client application 123. The error message may include an error code identifying the type or source of the error, a description of the error, and the cause of the error. In some embodiments, the error message itself may be an information object 116 representing the error and including applicable error information. In various embodiments, the collaboration server 113 may also log the error and any associated error information to a data repository 111 or log file for later analysis.

Moving on to block 616, the collaboration server 113 creates the information object 116 in the data repository 111 using the information received from the client application 123. If necessary, the collaboration server 113 also creates any required parent or child information objects and any references or connections between the newly created information object 116 and other existing information objects 116.

Next, referring to block 619, the collaboration server 113 sends a notification to the client application 123 that the information object 116 has been created. This notification may be in the form of a message, event notification, or other data format. Furthermore, in some embodiments, the collaboration server 113 may mark the newly created information object 116 as currently being modified or as having modification in progress. This may lock the information object 116 while it is being modified or otherwise prevent the information object 116 from being modified by other users, applications, or processes.

Continuing to block 623, the client application 123 receives notification from the collaboration server 113 that an information object 116 has been created. In some embodiments, the notification may also include an indication that the newly created information object 116 is marked for editing or modification. If the newly created information object is marked for editing, the client application 123 may enable modifications to the client or local copy of the information object 116. For example, the client application 123 may mark fields of the newly created information object 116 as editable, enable various menu functions for the information object 116, or take similar actions.

Moving on to block 626, the client application 123 obtains one or more user modifications to the newly created information object 116. In some embodiments, the client application 123 can automatically save the user modifications. For example, the client application 123 can automatically send each change to the collaboration server 113, or the client application 123 can send the changes in batches to the collaboration server 113 on a periodic basis, such as every few minutes, every hour, or some other time period. The client application 123 can also save the changes or modifications to the newly created information object 116 locally on the client computing device 106 ( FIG. 1 ). When the user finishes modifying the newly created information object 116, the final set of changes is sent to the collaboration server 113. In some embodiments, the sent changes can be sent in a file format that records the changes between the copy of the information object 116 stored in the data repository 111 and the copy of the information object 116 stored on the client computing device 106. In various embodiments, the changes may instead be sent as a copy of the information object 116 stored locally on the client computing device 106 to replace the copy of the corresponding information object 116 stored in the data repository 111. In such embodiments, the copy of the information object 116 may be serialized and transmitted to the collaboration server 113.

Next, referring to block 629, the collaboration server 113 determines whether the information corresponding to the modified information object 116 is valid. For example, the collaboration server 113 may check for errors as part of the deserialization process. The collaboration server 113 may check to see if the data is correctly formatted. If the information is invalid, execution proceeds to block 646, described above. However, if the information is valid, execution proceeds to block 633.

Continuing then to block 633, the collaboration server 113 stores the modifications to the information object 116 in the data repository 111. In some embodiments, this may be accomplished by overwriting or replacing a previous copy of the information object 116 stored in the data repository 111. In other embodiments, the content of the information object 116 may be edited or updated rather than overwriting the information object 116 with a new copy or version.

Moving on to block 636, the collaboration server 113 sends a notification to the client application 123 that the update of the information object 116 is complete. The notification may be in the form of a message, an event notification, or other data format. In addition, the collaboration server 113 may mark the newly created information object 116 as editable so that other users or processes waiting to modify the information object 116 can do so.

Continuing with reference to block 639, the client application 123 receives notification that the update or change to the newly created information object 116 is complete. In some implementations, the client application 123 may lock or otherwise prevent the user from modifying the newly created information object 116 upon receiving the notification. Execution then proceeds to block 643, where the client application 123 renders the newly created information object 116.

FIG7 shows a flowchart that provides one example of the operation of a portion of the client application 123 and the collaboration server 113 according to various embodiments. It should be understood that the flowchart of FIG7 merely provides an example of many different types of functional arrangements that can be used to implement the operation of portions of the client application 123 and the collaboration server 113 as described herein. Alternatively, the flowchart of FIG7 can be viewed as an example of elements of a method implemented in the networked environment 100 ( FIG1 ) according to one or more embodiments.

Beginning with block 703, the client application 123 receives a trigger event. A trigger event includes any event that indicates that the information object 116 associated with the trigger event should be modified. The trigger event may include, for example, a command received by the user interface 300 ( FIG. 1 ) to automatically arrange or layout the displayed information objects 116 according to one or more predetermined rules. The user interface may then send a trigger to the corresponding information objects 116 to modify their form data 216 according to the one or more predetermined rules. For example, the trigger event may indicate that the information objects 116 may change their position, size, or shape values stored in the form data 216.

Continuing to block 706 , the client application 123 retrieves the unique identifier 203 ( FIG. 2 ) of the information object 116 corresponding to the triggering event.

Next, referring to block 709, the collaboration server 113 determines whether the unique identifier 203 ( FIG. 2 ) is valid. For example, the collaboration server 113 may determine whether an information object 116 with the unique identifier 203 exists in the data repository 111 ( FIG. 1 ). If not, the collaboration server 113 may generate an error. As another example, the collaboration server 113 may further determine whether the information object 116 in the data repository 111 is an editable information object 116. If not, the collaboration server 113 may generate an error. If the collaboration server 113 determines that the unique identifier 203 is invalid, execution proceeds to block 739. However, if the information is valid, execution proceeds to block 713.

If execution proceeds to block 739, the collaboration server 113 generates an error message event and sends the error message to the client application 123. The error message may include an error code identifying the type or source of the error, a description of the error, and the cause of the error. In some embodiments, the error message itself may be an information object 116 representing the error and including applicable error information. In various embodiments, the collaboration server 113 may also log the error and any associated error information to a data repository 111 or log file for later analysis.

Moving on to block 713, the collaboration server 113 may mark the selected information object 116 as currently being modified or that modification of the selected information object 116 is in progress. This may lock the information object 116 while it is being modified or otherwise prevent the information object 116 from being modified by other users, applications, or processes. After locking the information object 116, the collaboration server 113 then sends a message to the client application 123 that the information object 116 may be edited.

Referring next to block 719, the client application 123 modifies the information object 116 in response to the trigger according to conditions associated with the trigger. In some implementations, while changes are being sent to the collaboration server 113, the changes can be automatically saved locally on the client computing device 106 (FIG. 1).

Next, referring to block 723, the collaboration server 113 determines whether the information corresponding to the modified information object 116 is valid. For example, the collaboration server 113 may check for errors as part of the deserialization process. The collaboration server 113 may check to see if the data is correctly formatted. If the information is invalid, execution proceeds to block 739, described above. However, if the information is valid, execution proceeds to block 526.

Moving on to block 726, the collaboration server 113 stores the modifications to the information object 116 in the data repository 111. In some embodiments, this may be accomplished by overwriting or replacing a previous copy of the information object 116 stored in the data repository 111. In other embodiments, the content of the information object 116 may be edited or updated rather than overwriting the information object 116 with a new copy or version.

Next, with reference to block 729, the collaboration server 113 sends a notification to the client application 123 that the update to the information object 116 is complete. The notification may be in the form of a message, an event notification, or other data format. In addition, the collaboration server 113 may mark the selected information object 116 as editable so that other users or processes waiting to modify the information object 116 can do so.

Moving on to block 733, the client application 123 receives notification that the update or change to the selected information object 116 is complete. In some implementations, the client application 123 may lock or otherwise prevent the user from modifying the selected information object 116 upon receiving the notification. Execution then continues to block 736, where the client application 123 renders the modified information object 116.

FIG8 shows a flowchart that provides one example of the operation of a portion of the client application 123 and the collaboration server 113 according to various embodiments. It should be understood that the flowchart of FIG8 merely provides an example of many different types of functional arrangements that can be used to implement the operation of portions of the client application 123 and the collaboration server 113 as described herein. Alternatively, the flowchart of FIG8 can be viewed as an example of elements of a method implemented in the networked environment 100 ( FIG1 ) according to one or more embodiments.

Beginning with block 803, the client application 123 receives data from a data source to be added to an existing information object 116 ( FIG. 1 ). The data source may include, for example, one or more sensors and/or other data feeds 126 ( FIG. 1 ). The data may be received as an information object 116 or a series of information objects 116. For example, a temperature sensor may record a series of temperatures and provide them to the client application 123 as a series of information objects 116 or as a single information object 116 representing a stream or series of temperature readings. In some embodiments, the sensors and/or other data feeds may provide the data as raw data that has not yet been processed into one or more information objects 116. Note also that in some embodiments, the sensors and/or other data feeds 126 may provide information directly to the collaboration server 113.

Referring next to block 806, the client application 123 verifies that the information provided by the one or more sensors and/or other data feeds 126 is valid. Verification of validity may depend on the type of information provided by the one or more sensors and/or other data feeds 126. If the data is received in the form of an information object 116, the client application 123 may determine whether the information object is formatted and constructed validly. If the data is received as raw data, the client application 123 may perform a validation check on the received data. If the received data is invalid, execution jumps to block 843. If the received data is valid, execution continues to block 809.

If execution jumps to block 843, the client application sends an error message to the sensor and/or other data feed 126 indicating that the received data or information object 116 is invalid. In some embodiments, the client application 123 may also generate an error message to be reproduced within the user interface 300 ( FIG. 1 ) and/or write the error or error message to a log. The process then terminates.

If, however, execution proceeds to block 809, the client application 123 calls one or more functions 219 ( FIG. 2 ) of the existing information object 116. As part of the calling process, the client application 123 may query or request a copy of the most recent or current version of the function 219 to be called from the collaboration server 113. For example, if the data provided by one or more sensors and/or other data feeds 126 is temperature data or a series of temperature readings, the client application 123 may call an “AddNewTemperatureReading” function 219 of the existing information object 116 to add the received data by adding an information object reference 209 ( FIG. 2 ) to the existing information object 116, creating an association between the existing information object 116. In some embodiments, a general “AddNewData” function 219 may be called to create an information object reference 209 between the received data and the existing information object 116.

Continuing to block 813, collaboration server 113 determines whether the provided data is valid. For example, collaboration server 113 may determine whether the arguments provided by client application 123 for the function 219 to be called are correct. Using the illustrative example of a temperature sensor, collaboration server 113 may determine whether client application 123 passed a temperature reading to "AddNewTemperatureReading" function 219 or whether client application 123 attempted to pass arguments unrelated to temperature data. As another example, collaboration server 113 may determine whether the request for the most current version of function 219 is valid. For example, the requested function may not exist or may be deprecated or removed from the current implementation of the system, and therefore, the function may no longer be available for invocation. In some embodiments, a subset of functions 219 may require enhanced or special permissions to execute, and collaboration server 113 must therefore determine whether client application 213 has the appropriate permissions to execute function 219. If collaboration server 113 determines that the request for the most current version of function 219 is invalid, execution proceeds to block 846. However, if the collaboration server 113 determines that the request is valid, execution continues to block 816 .

Jumping forward to block 846, the collaboration server 113 generates an error message event and sends the error message to the client application 123. The error message may include an error code identifying the type or source of the error, a description of the error, and the cause of the error. In some embodiments, the error message itself may be an information object 116 representing the error and including applicable error information. In various embodiments, the collaboration server 113 may also log the error and any associated error information to a data repository 111 ( FIG. 1 ) or a log file for later analysis.

Next, referring to block 816, the collaboration server 113 queries the data repository 111 to determine the most current version of the function 219 that the client application 123 is requested to execute. The collaboration server 113 then sends the code or logic for the most current version of the function 219 to the client application 123. In some embodiments, the function 219 may be sent as human-readable source code. In other embodiments, the function 219 may be serialized and sent to the client application 123.

Moving on to block 819, the client application 123 receives the latest version of the function 219 from the collaboration server 113. If the function 219 is provided as human-readable source code, the client application 123 may compile or interpret the human-readable source code into a machine-readable binary. If the function 219 is sent in serialized form, the function 219 may be deserialized by the client application 123. The client application 123 then executes the function 219.

Continuing then to block 823, the results of the function 219 executed in block 819 are sent to the collaboration server 113. In some implementations, the results may be sent as a collection of newly created data objects 116 or information objects 116.

Referring next to block 826, the collaboration server 113 determines whether the result of the function called in block 819 is valid. For example, the collaboration server 113 may determine whether the resulting information object 116 is correctly formatted. As another example, the collaboration server 113 may determine whether there is a conflict between the resulting one or more information objects 116 and any existing information objects 116 in the data repository 111. If the result is invalid, execution jumps to block 846, as previously described. If the result is valid, execution instead continues to block 829.

Moving on to block 829, the collaboration server 113 marks the initial information object 116 as modified. This locks or otherwise prevents the initial information object 116 from being modified by other client applications 123 or processes. The collaboration server then saves the data or information object 116 resulting from the function 219 executed in block 819 to the data repository 111, and also saves any modifications necessary to link the initial information object 116 to the newly created information object 116.

Continuing with block 833, the collaboration server 113 marks the corresponding information object 116 as modified, unlocking the information object 116 so that other client applications 123 or other processes can read or modify it. The collaboration server 113 then sends a message to the client application 123 indicating that all changes to the corresponding information object 116 are complete. Continuing with block 836, the client application 123 receives notification from the collaboration server 113 that the update of the information object 116 in the data repository 111 is complete. Continuing with block 839, the function 219 called in block 809 and executed in block 819 completes, and function 219 ends.

9, a schematic block diagram of a computing environment 103 according to an embodiment of the present disclosure is shown. The computing environment 103 includes one or more computing devices 900. Each computing device 900 includes, for example, at least one processor circuit having a processor 903 and a memory 906, both coupled to a local interface 909. To this end, each computing device 900 may include, for example, at least one server or similar device. The local interface 909 may include, for example, a data bus with an accompanying address/control bus or other bus structure as may be appreciated.

Stored in memory 906 are data and several components executable by processor 903. In particular, stored in memory 906 and executable by processor 903 are collaboration server 113 and possibly other applications. Also stored in memory 906 may be data repository 111 and other data. Furthermore, operating system 911 may be stored in memory 906 and executable by processor 903.

It should be understood that there may be other applications stored in the memory 906 and executable by the processor 903, as can be appreciated. Where any component discussed herein may be implemented in software, any of a variety of programming languages may be used, such as C, C++, C#, Objective C, Perl, PHP, Visual Ruby, or other programming languages.

A plurality of software components are stored in the memory 906 and are executable by the processor 903. In this regard, the term "executable" means a program file in a form that can ultimately be run by the processor 903. Examples of executable programs may be a compiled program, for example, which can be converted into machine code in a format that can be loaded into the random access portion of the memory 906 and run by the processor 903, source code that can be represented in a proper format, such as object code that can be loaded into the random access portion of the memory 906 and executed by the processor 903, or source code that can be interpreted by another executable program to generate instructions in the random access portion of the memory 906 and executed by the processor 903, etc. The executable program may be stored in any portion or component of the memory 1006, including, for example, random access memory (RAM), read-only memory (RAM), a hard drive, a solid-state drive, a USB flash drive, a memory card, an optical disk such as a compact disk (CD) or a digital versatile disk (DVD), a floppy disk, a magnetic tape, or other memory component.

Memory 906 is defined herein as including volatile and non-volatile memory and data storage components. Volatile components are those components that do not retain data values when power is lost. Non-volatile components are those components that retain data when power is lost. Therefore, memory 906 may include, for example, random access memory (RAM), read-only memory (RAM), hard drive, solid-state drive, USB flash drive, memory card accessed via a memory card reader, floppy disk accessed via a floppy disk drive, optical disk accessed via an optical disk drive, magnetic tape accessed via an appropriate tape drive and/or other memory components or any combination of two or more of these memory components. In addition, RAM may include, for example, static random access memory (SRAM), dynamic random access memory (DRAM) or magnetic random access memory (MRAM) and other such devices. ROM may include, for example, programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM) or other types of memory devices.

Furthermore, the processor 903 may represent a plurality of processors 903 and/or a plurality of processor cores, and the memory 906 may represent a plurality of memories 906 each operating in parallel processing circuits. In such a case, the local interface 909 may be an appropriate network that facilitates communication between any two of the plurality of processors 903, between any processor 903 and any memory 906, or between any two of the memories 906. The local interface 909 may include additional systems designed to coordinate this communication, including, for example, performing load balancing. The processor 903 may have an electrical or some other usable structure.

Although the collaboration server 113 and client application 123 and the various other systems described herein may be embodied in software or code executed by general-purpose hardware as discussed above, as an alternative, they may also be embodied in dedicated hardware or a combination of software/general-purpose hardware and dedicated hardware. If embodied in dedicated hardware, each may be implemented as a circuit or state machine using any one or a combination of a variety of technologies. These technologies may include, but are not limited to, discrete logic circuits having logic gates for implementing various logic functions when one or more data signals are applied, application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other components having appropriate logic gates. Such technologies are generally well known to those skilled in the art and, therefore, are not described in detail herein.

The present disclosure may describe the functionality and operations of a portion of the implementation of the collaboration server 113 or client application 123. If embodied in software, the functionality may represent a module, segment, or portion of code comprising program instructions for implementing the specified logical function. The program instructions may be embodied in the form of source code comprising human-readable statements written in a programming language or machine code comprising digital instructions recognizable by an appropriate execution system in a computer system or other system, such as processor 903. Machine code may be converted from source code, etc. If embodied in hardware, each block may represent a circuit or multiple interconnected circuits to implement the specified logical function.

Although a specific execution order of an application may be described, it should be understood that the execution order may differ from the order described. The functions described may be implemented simultaneously or in parallel with other functions described. Moreover, the functions may appear in an order different from the order described or depicted in this disclosure. In addition, in some embodiments, the functions described herein may be skipped or omitted. In addition, for the purpose of enhanced practicality, accounting, performance measurement, or providing troubleshooting, any number of counters, status variables, warning lights, or messages may be added to the logic flow described herein. It should be understood that all such variations are within the scope of this disclosure.

Furthermore, any logic or application described herein, including software or code, including the collaboration server 113 and the client application 123, may be embodied in any non-transitory computer-readable medium for use by or in conjunction with an instruction execution system, such as a processor 903 in a computer system or other system. In this sense, logic may include, for example, statements including instructions and declarations that can be retrieved from a computer-readable medium and executed by an instruction execution system. In the context of this disclosure, a "computer-readable medium" may be any medium that can contain, store, or maintain logic or an application described herein for use by or in conjunction with an instruction execution system.

Computer-readable media can include any of a variety of physical media, such as magnetic, optical, or semiconductor media. More specific examples of suitable computer-readable media include, but are not limited to, magnetic tape, magnetic floppy disks, magnetic hard drives, memory cards, solid-state drives, USB flash drives, or optical disks. Additionally, the computer-readable medium can be a random access memory (RAM), including, for example, a static random access memory (SRAM), a dynamic random access memory (DRAM), or a magnetic random access memory (MRAM). Additionally, the computer-readable medium can be a read-only access memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or other types of memory devices.

It should be emphasized that the above-described embodiments of the present disclosure are merely examples of possible implementations produced for a clear understanding of the principles of the present disclosure. Many variations and modifications may be made to the above-described embodiments without substantially departing from the spirit and principles of the present disclosure. All such modifications and variations are intended to be included herein within the scope of the present disclosure and protected by the following claims.

Claims (31)

1. A system for displaying information to a user, comprising: Modules used to generate user interfaces on client computing devices; A module for responding to a request to reproduce an information object by querying a collaboration server on behalf of the user for the information object to be reproduced within the user interface, wherein the information object represents at least one set of associations among a plurality of other information objects, and the information object includes formal data and functions: The formal data includes a set of specified values for reproducing the information objects within the user interface, at least in part, based on the set of associations between the plurality of other information objects, and The function includes a program interface for manipulating the information object; A module for extracting the formal data from the information object received from the collaboration server; and A module for reproducing the information object within the user interface, at least in part, based on the formal data of the information object. 2. The system of claim 1, further comprising: A module for obtaining the identifier of the relevant information object from the information object; A module for querying the relevant information object from the collaboration server; and A module for reproducing the relevant information object within the user interface based at least in part on the formal data extracted from the information object. 3. The system of claim 2 further includes a module for reproducing an indication of the relationship between the information object and the related information object within the user interface. 4. The system according to any one of claims 1-3, further comprising: A module for obtaining modifications to the information object; Module for sending the modifications to the collaboration server; A module for reproducing the modified version of the information object within the user interface in response to receiving a first notification from the collaboration server that the modification is valid; and A module for reproducing the error message within the user interface in response to receiving a second notification from the collaboration server that the modification is invalid. 5. The system according to any one of claims 1-3, further comprising: The module used to generate new information objects in response to data received from the data source; A module for creating information object references that link the information object to the new information object; and A module for sending the information object, the new information object, and the information object reference to the collaboration server. 6. The system of claim 4, further comprising: The module used to generate new information objects in response to data received from the data source; A module for creating information object references that link the information object to the new information object; and A module for sending the information object, the new information object, and the information object reference to the collaboration server. 7. The system of claim 5, wherein the data source includes an electronic device that generates data and transmits the data to the client computing device. 8. The system of claim 6, wherein the data source includes an electronic device that generates data and transmits the data to the client computing device. 9. The system according to any one of claims 1-3, 6-8, wherein the information object further includes at least one of a universally unique identifier and an information object reference. 10. The system of claim 4, wherein the information object further includes at least one of a universally unique identifier and an information object reference. 11. The system of claim 5, wherein the information object further includes at least one of a universally unique identifier and an information object reference. 12. A system for displaying information to a user, comprising: A computing device, the computing device including circuitry, wherein the circuitry includes: The logic circuitry that generates the user interface on the client computing device; In response to a request to reproduce an information object, the system queries a collaboration server on behalf of the user for the logic circuitry of the information object to be reproduced within the user interface, wherein the information object represents at least one set of associations among a plurality of other information objects, and the information object includes formal data and functions. The formal data includes a set of specified values for reproducing the information objects within the user interface, at least in part, based on the set of associations between the plurality of other information objects, and The function includes a program interface for manipulating the information object; Logic circuitry for extracting formal data from the information object received from the collaborative server; and The logic circuitry of the information object is reproduced within the user interface, at least in part, based on the formal data of the information object. 13. The system of claim 12, wherein the circuit further comprises: A logic circuit for obtaining the identifier of a related information object from the information object; Query the logic circuit of the relevant information object from the collaborative server; and The logic circuitry of the relevant information object is reproduced within the user interface, at least in part, based on the formal data extracted from the information object. 14. The system of claim 13, wherein the circuitry further comprises logic circuitry that reproduces an indication of the relationship between the information objects or the related information objects within the user interface. 15. The system according to any one of claims 12-14, wherein the circuit further comprises: The logic circuit that obtains the modification of the information object; The logic circuit that sends the modification to the collaboration server; Logic circuitry that reproduces the modified version of the information object within the user interface in response to receiving a first notification from the collaboration server that the modification is valid; and A logic circuit that reproduces an error message within the user interface in response to receiving a second notification from the collaboration server that the modification is invalid. 16. The system according to any one of claims 12-14, wherein the circuit further comprises: A logic circuit that generates a new information object in response to data received from a data source; Create a logic circuit that links the information object to an information object reference of the new information object; and The logic circuit that sends the information object, the new information object, and the information object reference to the collaboration server. 17. The system of claim 15, wherein the circuit further comprises: A logic circuit that generates a new information object in response to data received from a data source; Create a logic circuit that links the information object to an information object reference of the new information object; and The logic circuit that sends the information object, the new information object, and the information object reference to the collaboration server. 18. The system of claim 16, wherein the data source includes an electronic device that generates data and transmits the data to the computing device. 19. The system of claim 17, wherein the data source includes an electronic device that generates data and transmits the data to the computing device. 20. The system according to any one of claims 12-14, 17-19, wherein the information object further includes at least one of a universally unique identifier and an information object reference. 21. The system of claim 15, wherein the information object further includes at least one of a universally unique identifier and an information object reference. 22. The system of claim 16, wherein the information object further includes at least one of a universally unique identifier and an information object reference. 23. A method for displaying information to a user, comprising: A user interface is generated on the client computing device via a computing device; The computing device, in response to a request to reproduce an information object, queries a collaboration server on behalf of the user for the information object to be reproduced within the user interface, wherein the information object represents at least one set of associations among a plurality of other information objects, and the information object includes formal data and functions: The formal data includes a set of specified values for reproducing the information objects within the user interface, at least in part, based on the set of associations between the plurality of other information objects, and The function includes a program interface for manipulating the information object; Extracting the formal data from the information object received from the collaborative server via the computing device; and The information object is reproduced within the user interface via the computing device, at least in part, based on the formal data of the information object. 24. The method of claim 23, further comprising: The identifier of the relevant information object is obtained from the information object via the computing device; The computing device queries the collaborative server for the relevant information object; and The relevant information object is reproduced within the user interface via the computing device, at least in part, based on the formal data extracted from the information object. 25. The method of claim 24, further comprising reproducing, via the computing device, an indication of the relationship between the information object and the related information object within the user interface. 26. The method of any one of claims 23-25, further comprising: The information object is modified via the computing device; The modification is sent to the collaboration server via the computing device; In response to receiving a first notification from the collaboration server that the modification is valid, the computing device reproduces the modified version of the information object within the user interface; and The error message is reproduced within the user interface via the computing device in response to receiving a second notification from the collaboration server that the modification is invalid. 27. The method of any one of claims 23-25, further comprising: The computing device generates a new information object in response to receiving data from the data source; An information object reference is created via the computing device to link the information object to the new information object; and The information object, the new information object, and the information object reference are sent to the collaboration server via the computing device. 28. The method of claim 26, further comprising: The computing device generates a new information object in response to data received from the data source; An information object reference is created via the computing device to link the information object to the new information object; and The information object, the new information object, and the information object reference are sent to the collaboration server via the computing device. 29. The method of any one of claims 23-25 and 28, wherein the information object further includes at least one of a universally unique identifier and an information object reference. 30. The method of claim 26, wherein the information object further includes at least one of a universally unique identifier and an information object reference. 31. The method of claim 27, wherein the information object further includes at least one of a universally unique identifier and an information object reference.