Difference between revisions of "ECMA-363 (Universal 3D File Format)"

From GICL Wiki
Jump to: navigation, search
Line 41: Line 41:
 
Surfaces.
 
Surfaces.
  
'''Example(s):''' [[Example::Example Template]] - Information and example models of the engineering format.
+
'''Example(s):'''
 +
* Ala.u3d (57 kB) [[http://jmol.sourceforge.net/demo/3dscenes/Ala.u3d]]
 +
* Ala_s.u3d(32 kB) [[http://jmol.sourceforge.net/demo/3dscenes/Ala_s.u3d]]
 +
* 1HEL.u3d(0.85 MB)[[http://jmol.sourceforge.net/demo/3dscenes/1HEL.u3d]]
 +
* 1HEL_s.u3d(0.56 MB) [[http://jmol.sourceforge.net/demo/3dscenes/1HEL_s.u3d]]
  
 
'''Identifier:''' Standard ECMA-363 [[http://www.ecma-international.org/publications/standards/Ecma-363.htm]]
 
'''Identifier:''' Standard ECMA-363 [[http://www.ecma-international.org/publications/standards/Ecma-363.htm]]
Line 57: Line 61:
 
** Pdftex  with the movie15 [[http://en.wikipedia.org/w/index.php?title=Movie15&action=edit&redlink=1]] package
 
** Pdftex  with the movie15 [[http://en.wikipedia.org/w/index.php?title=Movie15&action=edit&redlink=1]] package
 
** Siemens PLM Software [[http://en.wikipedia.org/wiki/Siemens_PLM_Software]] Process Simulate  
 
** Siemens PLM Software [[http://en.wikipedia.org/wiki/Siemens_PLM_Software]] Process Simulate  
 +
** Photoshop CS3
 +
** Poser 7
 +
** DAZ Studio
 +
** MeshLab
  
* '''Interoperable applications:''' [[Interoperable Application::Engineering Format Application Template]] - Applications which can read or write files of this format, but are not native applications for the format.
+
* '''Standardization:''' Standard ECMA-363 [[http://www.ecma-international.org/publications/standards/Ecma-363.htm]]
  
'''Magic numbers:''' [[Magic Numbers::]] - Unique identifying characters at the beginning of files for this engineering format.
+
* '''Adoption:''' The goal is a universal standard for three-dimensional data of all kinds, to facilitate data exchange. The consortium promoted also the development of an open source library for facilitating the adoption of the format. The format is natively supported by the PDF format and 3D objects in U3D format can be inserted into PDF documents and interactively visualized by Acrobat Reader (since version 7).
  
'''Format(s):''' [[Format::]] - The MIME file types.
+
** '''Licensing and patent claims:''' N/A
  
'''Rights:''' [[Rights::]] - The name or type of the license for the engineering format. Examples: BSD-style license, Apache License, Proprietary license
+
'''Typical use:''' CAD
  
'''Sustainability Factors:''' - Facts about the sustainability of this particular engineering format.
+
'''File classification:'''
 
+
* '''Type {Binary, Text}:''' Binary
* '''Standardization:''' [[Standardization::]] - Information regarding standardization attempts with this format.
+
* '''Raster data:'''  
 
+
* '''Adoption:''' [[Adoption::]] - Information about how this format has been adopted by other organizations.
+
 
+
** '''Licensing and patent claims:''' [[Licensing and patent claims::]] - Any licenses or patent claims that the engineering format makes.
+
 
+
* '''Self-documentation:''' [[Self-documentation::]] - Any self-documentation capabilities of the format.
+
 
+
* '''External dependencies:''' [[External dependencies::]] - Anything that the format depends on outside of its control to function.
+
 
+
* '''Technical protection considerations:''' [[Technical protection considerations::]] - Any considerations that are necessary when it comes to technical protection.
+
 
+
'''Typical use:''' [[Typical use::]] - Keywords that describe the format's typical use. Examples: CAD and CAM
+
 
+
'''File classification:''' - Specific properties that pertain to this engineering format.
+
* '''Type {Binary, Text}:''' [[File Classification Type::]] - The type of file, choices are binary and text.
+
* '''Raster data:''' - Section describes whether or not the engineering format supports raster data.
+
 
** '''Raster data 2D:''' - Can the format support 2D raster data? Example: A format that can contain 2D pixelated data supports 2D raster data.
 
** '''Raster data 2D:''' - Can the format support 2D raster data? Example: A format that can contain 2D pixelated data supports 2D raster data.
 
*** '''Is Supported:''' [[File Classification Raster Data 2D - Is Supported::]] - Is the feature supported in the engineering format?
 
*** '''Is Supported:''' [[File Classification Raster Data 2D - Is Supported::]] - Is the feature supported in the engineering format?

Revision as of 12:26, 4 March 2010

Title(s): ECMA-363: Universal 3D File Format

Version ID: 4th Edition

Date released: June 2007

Date: August 2005

Creator(s): Ecma International [[1]]

Contributor(s): Technical Committee 43 (TC43), Intel, Boeing, HP, Adobe Systems, Bentley Systems, Right Hemisphere

Relationships: promote the development of 3D graphics for use in various industries, specifically at this time manufacturing as well as construction and industrial plant design

  • Previous Version(s):
  • 1st Edition : December 2004 [[2]]
  • 2st Edition : August 2005 [[3]]
  • 3st Edition : June 2006 [[4]]
  • 4st Edition : June 2007 [[5]]
  • Syntax Format(s): The U3D run-time architecture may be extended by new objects not defined in this document. These new objects shall be in the class of modifier objects within a modifier chain. File format

requirements for the new objects are in 9.4.6 New Object Type and 9.4.7 New Object Block [[6]]

Description: This Standard defines the syntax and semantics of the Universal 3D file format, an extensible format for downstream 3D CAD repurposing and visualization, useful for many mainstream business applications. Salient features of the U3D file format described in this document include: execution architecture that facilitates optimal run-time modification of geometry, continuous-level-of-detail, domain-specific compression, progressive data streaming and playback, free-form surfaces, key-frame and bones-based animation, and extensibility of U3D format and run-time.

  • The U3D file format specification does not address issues regarding rendering of 3D content.
  • The U3D file format specification does not address issues regarding reliability of the transport layer or communications channel. It is assumed that reliability issues will be addressed by a different protocol layer.
  • The U3D file format specification does not address run-time extensibility of an implementation of the U3D architecture. [[7]]

History:

  • In 2004, Ecma International formed Technical Committee 43 (TC43) to specify Universal 3D (U3D) File Format specification. The Universal 3D File Format specification is primarily intended for downstream 3D CAD repurposing and visualization purposes. The 1st Edition of the U3D File Format was adopted by the General Assembly of December 2004.
  • In 2005, TC43 added file format extensibility to the 2nd Edition of the U3D File Format specification. The 2nd Edition of the U3D File Format was submitted to ISO/IEC for fast-track processing.
  • In 2006, changes were made as a result of comments received during the ISO/IEC DIS ballot process.
  • In 2007, TC43 added the Free-Form Curve and Surface Extension to the 4th Edition of the U3D File Format specification that adds support for Uniform and Non-Uniform, Rational and Non-Rational Free-Form Curves and

Surfaces.

Example(s):

  • Ala.u3d (57 kB) [[8]]
  • Ala_s.u3d(32 kB) [[9]]
  • 1HEL.u3d(0.85 MB)[[10]]
  • 1HEL_s.u3d(0.56 MB) [[11]]

Identifier: Standard ECMA-363 [[12]]

Documentation: 4st Edition : June 2007 [[13]]

File Extensions: .u3d

Applications:

  • Native application(s):
    • Adobe Acrobat Extended
    • Adobe Acrobat Pro
    • Bentley Systems MicroStation
    • Pdftex with the movie15 [[14]] package
    • Siemens PLM Software [[15]] Process Simulate
    • Photoshop CS3
    • Poser 7
    • DAZ Studio
    • MeshLab
  • Standardization: Standard ECMA-363 [[16]]
  • Adoption: The goal is a universal standard for three-dimensional data of all kinds, to facilitate data exchange. The consortium promoted also the development of an open source library for facilitating the adoption of the format. The format is natively supported by the PDF format and 3D objects in U3D format can be inserted into PDF documents and interactively visualized by Acrobat Reader (since version 7).
    • Licensing and patent claims: N/A

Typical use: CAD

File classification:

  • Type {Binary, Text}: Binary
  • Raster data:
    • Raster data 2D: - Can the format support 2D raster data? Example: A format that can contain 2D pixelated data supports 2D raster data.
      • 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.
    • Raster data 3D: - Can the format support 3D raster data? Example: A format that can contain 2D pixelated data of a 3D model supports 3D raster data.
      • 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.
  • Geometric representation: - Section describes whether or not the engineering format supports geometric representations.
    • 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: - 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: - 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: - Is the feature supported in the engineering format?
        • Description: - 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: - 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: - 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: - 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: - 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: - 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: - 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: - 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: - 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: - 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: - 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: - 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: - 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: - Is the feature supported in the engineering format?
    • Description: - This field is used to describe the support or lack of support of the feature.

References: - A list of references regarding any aspects of this engineering format; any reading material supplemental to this page.