VRML

Revision as of 16:01, 10 May 2009

Title(s): Virtual Reality Modeling Language also known as Virtual Reality Markup Language

Version ID: 2.0 / VRML97

Date released: 1997

Date: 15 May 1994

Creator(s): Sir Tim Berners-Lee

Contributor(s): The VRML Consortium, Inc.

Relationships: X3D

• Previous Version(s): First unofficial version: VRML94 first and only ISO version: VRML97

• Contains: Java, Javascript

• Syntax Format(s): - Any syntax formats that the engineering format may use.

• Family Format(s): none

Description: Specifies the vertexes and edges in 3D polygons along with the texture and lighting of the 3D objects, also sets behavior of objects

History: - Historical description depicting major events surrounding development, creation, and maintenance of this format.

Example(s):

 #VRML V2.0 utf8
 WorldInfo {
  title "Red Sphere"
  info ["This Web3D Content was created with Flux Studio, a Web3D authoring tool"
  "www.mediamachines.com"]
 }
 DEF Sphere1 Shape {
  appearance Appearance {
   material DEF Red Material {
    ambientIntensity 0.200
    shininess 0.200
    diffuseColor 1 0 0
   }
  }
  geometry DEF GeoSphere1 Sphere {
   radius 1.000
  } 
 }

Identifier: [[Identifier::ISO VRML97 ]]

Documentation: Documentation Template - Information in general about the engineering format.

File Extensions: wrl, wrz, vrml.

Applications: - Applications that the engineering format uses.

• Native application(s): Engineering Format Application Template - Applications which are primarily designed to specifically run this engineering format.

• Interoperable applications: Engineering Format Application Template - Applications which can read or write files of this format, but are not native applications for the format.

Magic numbers: - Unique identifying characters at the beginning of files for this engineering format.

Format(s): x-world/x-vrml.

Rights: - The name or type of the license for the engineering format. Examples: BSD-style license, Apache License, Proprietary license

Sustainability Factors: - Facts about the sustainability of this particular engineering format.

• Standardization: Standardized through ISO in 1997.

• Adoption: Never really adopted due to the lack of bandwidth and graphical capabilities in the 90's - Information about how this format has been adopted by other organizations.

• • Licensing and patent claims: None?.

• Self-documentation: - Any self-documentation capabilities of the format.

• External dependencies: - Anything that the format depends on outside of its control to function.

• Technical protection considerations: - Any considerations that are necessary when it comes to technical protection.

Typical use: Displaying 3d scenes embedded in web browsers.

File classification: - Specific properties that pertain to this engineering format.

• Type {Binary, Text}: Text.
• Raster data: - Section describes whether or not the engineering format supports raster data.
  • Raster data 2D:
    • Is Supported: No
    • Description:
  • Raster data 3D:
    • Is Supported: No
    • Description:
• Geometric representation: - Yes.
  • Implicit representation: - Section describes whether or not the engineering format supports implicit representations.
    • Implicit surfaces: - Can the format support implicit surfaces? Example: A format that can contain surfaces that are generated with mathematical equations that contain the independent variables x, y, and z, like x^2 + y^2 + z^2 * R^2 = 0, supports implicit surfaces.
      • Is Supported: No - Is the feature supported in the engineering format?
      • Description: - This field is used to describe the support or lack of support of the feature.
    • Implicit curves: - Can the format support implicit curves? Example: A format that can contain curves that are generated with mathematical equations that contain the independent variables x, y, and z, supports implicit curves.
      • Is Supported: No - Is the feature supported in the engineering format?
      • Description: - This field is used to describe the support or lack of support of the feature.
    • Point set: - Can the format support point sets? Example: A format that supports surfaces and lines that are generated by points that form triangles supports point sets.
      • Is Supported: Yes - Is the feature supported in the engineering format?
      • Description: Through the PointSet node type - This field is used to describe the support or lack of support of the feature.
  • Mesh: - Section describes whether or not the engineering format supports mesh.
    • Manifold surface meshes: - Can the format support manifold surface meshes? Example: A format that supports surfaces that are mathematical spaces in which every point has a neighborhood which resembles Euclidean space
      • Is Supported: No - Is the feature supported in the engineering format?
      • Description: - This field is used to describe the support or lack of support of the feature.
    • Manifold volume meshes: - Can the format support manifold volume meshes? Example: A format that supports volumes that are mathematical spaces in which every point has a neighborhood which resembles Euclidean space
      • Is Supported: No - Is the feature supported in the engineering format?
      • Description: - This field is used to describe the support or lack of support of the feature.
    • Non-manifold meshes: - Can the format support non-manifold meshes? Example: A format that supports meshes that are not manifolds
      • Is Supported: No - Is the feature supported in the engineering format?
      • Description: - This field is used to describe the support or lack of support of the feature.
  • Parametric representation: - Section describes whether or not the engineering format supports parametric representations.
    • Parametric surfaces: - Can the format support parametric surfaces? Example: A format that can contain surfaces that are generated with parametric equations supports parametric surfaces.
      • Is Supported: No - Is the feature supported in the engineering format?
      • Description: - This field is used to describe the support or lack of support of the feature.
    • Parametric curves: - Can the format support parametric curves? Example: A format that can contain curves that are generated with parametric equations supports parametric curves.
      • Is Supported: No - Is the feature supported in the engineering format?
      • Description: - This field is used to describe the support or lack of support of the feature.
  • Contour sets: - Can the format support contour sets?
    • Is Supported: No - Is the feature supported in the engineering format?
    • Description: - This field is used to describe the support or lack of support of the feature.
  • NURBS: - Can the format support Non Uniform Rational Basis Splines? Examples: The engineering formats IGES, STEP, ACIS, and PHIGS
    • Is Supported: Yes - Is the feature supported in the engineering format?
    • Description: - This field is used to describe the support or lack of support of the feature.
• Multi-resolution models: - Can the format support models with multiple resolutions? Examples: A format that supports a highly detailed and lowly detailed model simultaneously supports multi-resolution models.
  • Is Supported: No - Is the feature supported in the engineering format?
  • Description: - This field is used to describe the support or lack of support of the feature.
• Dynamics: - Section describes whether or not the engineering format supports dynamics.
  • Kinematics: - Can the format support kinematics? Example: Does the format allow model parts to rotate?
    • Is Supported: No - Is the feature supported in the engineering format?
    • Description: - This field is used to describe the support or lack of support of the feature.
  • Assembly: - Can the format support assembly? Example: Does the format allow the assembly instructions to be explicitly specified with a model?
    • Is Supported: No - Is the feature supported in the engineering format?
    • Description: - This field is used to describe the support or lack of support of the feature.
  • Force(s): - Can the format support forces? Example: Does the format support acceleration forces?
    • Is Supported: No - Is the feature supported in the engineering format?
    • Description: - This field is used to describe the support or lack of support of the feature.
• Boundary representation - Can the format support models with boundary representations?
  • Manifold surface boundary representations: - Can the format support manifold surface boundary representations? Example: The engineering format STEP
    • Is Supported: No - Is the feature supported in the engineering format?
    • Description: - This field is used to describe the support or lack of support of the feature.
  • Manifold volume boundary representations: - Can the format support manifold volume boundary representations? Example: The engineering format STEP
    • Is Supported: - Is the feature supported in the engineering format?
    • Description: - This field is used to describe the support or lack of support of the feature.
  • Non-manifold boundary representations: - Can the format support non-manifold boundary representations? Example: The engineering format STEP
    • Is Supported: - Is the feature supported in the engineering format?
    • Description: - This field is used to describe the support or lack of support of the feature.
• Material transparency: - Can the format support transparency? Example: Does the format allow models to have a clear window in a car?
  • Is Supported: Yes
  • Description: - This field is used to describe the support or lack of support of the feature.

References: [[References::[1], [2] ]]