#Freewrl 3.1 mac software#

X3D functionality is defined in ISO/IEC 19775, which comprises two parts Part 1 defines the X3D format architecture and Part 2 defines a protocol, known as the Scene Authoring Interface (SAI) for manipulating an X3D instance and supporting user interactions with a 3D object or scene.

Separate the runtime architecture from the data encoding.

The scene graph is a tree structure that collects all aspects of a 3D scene in a hierarchical fashion, properly organizing geometry, appearance, animation, and event routing.Ī number of design objectives have guided the development of X3D: X3D uses a 'scene graph' to assemble all the nodes that make up the virtual environment being modeled. For example, in the XML encoding, nodes are represented as elements (see X3D example in XML encoding). Nodes are the basic building blocks for the physical encodings of an X3D file. The Appearance node can include one of a set of child nodes the possible children include nodes for Material, Texture, LineProperties, FillProperties, Shaders, etc. For example, each Shape node has a Geometry node and an Appearance node. Nodes contain fields a field may be a value, a set of values, or a child node. Some components are specialized, such as the CAD Geometry component others are essential to every application, such as the Shape component, which defines node types for associating geometry with visible properties.

#Freewrl 3.1 mac software#

Components act as modular collections of 'node types' that make it easier for software to gradually implement a range of X3D capabilities. Profiles appropriate for different application areas or markets are specified in annexes profile annexes list components that must be supported and other constraints. Examples of components are Shape, Appearance, Texturing, Lighting, Time, Geometr圓D, Geospatial, Navigation, Scripting.

To address this complexity, the X3D architecture is described in 35 chapters for conceptual 'components'. For example, digitized 3D models of museum artifacts typically do not need geospatial location and orientation in a global coordinate system as would be essential in a model of a city used by planners. Not all application areas need all features. See Notes below for a list of features from the standard's introduction. With the aim of supporting a wide variety of application areas, the architecture supports many functionalities and features. The Web3D Consortium provides two useful diagrams of the family of standards: firstly, a 'honeycomb' diagram of the current standards related to X3D and secondly, a newer diagram of relationships between X3D graphics specifications that serves as a roadmap, showing newer developments and indicating future plans.

X3D is also intended to be a universal interchange format for integrated 3D graphics and multimedia.' Development, testing, and maintenance of the family of X3D standards is undertaken by members of the not-for-profit Web3D Consortium, with standardization under the auspices of JTC1/SC24. X3D is intended for use on a variety of hardware devices and in a broad range of application areas such as engineering and scientific visualization, multimedia presentations, entertainment and educational titles, web pages, and shared virtual worlds. X3D evolved from the Virtual Reality Modeling Language (VRML) and, like VRML, is designed to support a virtual environment, but also to be applicable in many other 3D contexts.Īccording to the introduction to ISO/IEC/19557-1, the specification of the architecture and functionality of X3D, 'X3D is a software standard for defining interactive web- and broadcast-based 3D content integrated with multimedia. Information technology - Computer graphics, image processing and environmental data representation - Extensible (X3D) encodingsĮxtensible 3D (X3D) is a family of co-ordinated royalty-free open standards for file formats that can store representations of interactive 3D objects and scenes, with an associated run-time architecture for communicating the scenes and objects.