Abstract: A scene graph is provided which represents data and a set of processes thus providing an enhanced approach to the previously known scene graph concept. With this approach the scene graph becomes a rendering description of the data rather than a world description. Previously known scene graphs represent a structure of objects and their attributes. The scene graph has a notation of the traversing order, which together with the types of nodes, the nodes position, node functionality and node state determine the rendering order. Thus, any effects supported by the underlying rendering pipeline can be expressed directly in the scene graph by the user. An API is provided for the scene graph, controlling the actual rendering order and optimization to the user. The scene graph is extensible allowing the user to experiment and express new rendering algorithms in the scene graph semantic.

Abstract: A primary user interface is configured to receive uploaded data sets stored in a primary memory means each describing a 3D graphics data structure in a respective source format. A secondary user interface receives request messages from user clients and in response, provides the clients access to specified data sets. Upon receipt of a request message, an examining entity identifies a graphics rendering capability of the client originating the message, and investigates whether or not the client is equipped with a viewer capable of visualizing the requested data set. A viewer database contains software modules adapted to implement at least two different viewers, where each viewer is configured to visualize the stored data sets on at least one type of client.