ECMA-363 (Universal 3D File Format) - Revision history

Tdn32 at 14:15, 8 March 2010

2010-03-08T14:15:02Z

Tdn32 at 14:09, 8 March 2010

2010-03-08T14:09:47Z

Tdn32 at 14:08, 8 March 2010

2010-03-08T14:08:33Z

Tdn32 at 14:06, 8 March 2010

2010-03-08T14:06:49Z

Tdn32 at 14:05, 8 March 2010

2010-03-08T14:05:48Z

Tdn32 at 16:41, 4 March 2010

2010-03-04T16:41:49Z

Tdn32 at 16:41, 4 March 2010

2010-03-04T16:41:29Z

Tdn32 at 16:26, 4 March 2010

2010-03-04T16:26:09Z

Tdn32 at 14:57, 4 March 2010

2010-03-04T14:57:28Z

Tdn32 at 14:46, 4 March 2010

2010-03-04T14:46:21Z

← Older revision		Revision as of 14:15, 8 March 2010
Line 149:		Line 149:
	'''References:'''		'''References:'''
	* 3D meshes into the U3D format- Meshlab[[http://meshlab.sourceforge.net/]]		* 3D meshes into the U3D format- Meshlab[[http://meshlab.sourceforge.net/]]
		+	* Universal 3D Sample Software [[http://sourceforge.net/projects/u3d/]]
		+	* VRML model to 3D PDF Tutorial [[http://www.dayel.com/2009/11/embedding-a-3d-figure-into-a-pdf/]]

← Older revision		Revision as of 14:09, 8 March 2010
Line 148:		Line 148:

	'''References:'''		'''References:'''
		+	* 3D meshes into the U3D format- Meshlab[[http://meshlab.sourceforge.net/]]

@@ Line 66: / Line 66: @@
 ** MeshLab
-'''Magic numbers:''' The first block is the File Header Block. The File Header Block is the only required block for a U3D file. The File Header Block is followed by declaration blocks. Contains the string UD3 at the begining of the file.
+'''Magic numbers:''' The first block is the File Header Block. The File Header Block is the only required block for a U3D file. The File Header Block is followed by declaration blocks. Contains the string U3D at the begining of the file.
 * '''Standardization:''' Standard ECMA-363 [[http://www.ecma-international.org/publications/standards/Ecma-363.htm]]

@@ Line 66: / Line 66: @@
 ** MeshLab
-'''Magic numbers:''' The first block is the File Header Block. The File Header Block is the only required block for a U3D file. The File Header Block is followed by declaration blocks.
+'''Magic numbers:''' The first block is the File Header Block. The File Header Block is the only required block for a U3D file. The File Header Block is followed by declaration blocks. Contains the string UD3 at the begining of the file.
 * '''Standardization:''' Standard ECMA-363 [[http://www.ecma-international.org/publications/standards/Ecma-363.htm]]
@@ Line 77: / Line 77: @@
 '''File classification:'''
-* '''Type {Binary, Text}:''' Binary
+* '''Type {Binary, Text}:''' Both
 * '''Raster data:'''
 ** '''Raster data 2D:'''

@@ Line 65: / Line 65: @@
 ** DAZ Studio
 ** MeshLab
 * '''Standardization:''' Standard ECMA-363 [[http://www.ecma-international.org/publications/standards/Ecma-363.htm]]

@@ Line 138: / Line 138: @@
 *** '''Is Supported:''' False
 **** '''Description:''' N/A
-** '''Non-manifold boundary representations:''' *** '''Is Supported:''' False
+** '''Non-manifold boundary representations:'''
 **** '''Description:''' N/A
 * '''Material transparency:'''

@@ Line 77: / Line 77: @@
 * '''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.
+** '''Raster data 2D:'''
-*** '''Is Supported:''' [[File Classification Raster Data 2D - Is Supported::]] - Is the feature supported in the engineering format?
+*** '''Is Supported:'''False
-*** '''Description:''' [[File Classification Raster Data 2D - Description::]] - This field is used to describe the support or lack of support of the feature.
+*** '''Description:''' N/A
-** '''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.
+** '''Raster data 3D:'''
-*** '''Is Supported:''' [[File Classification Raster Data 3D - Is Supported::]] - Is the feature supported in the engineering format?
+*** '''Is Supported:''' False
-*** '''Description:''' [[File Classification Raster Data 3D - Description::]] - This field is used to describe the support or lack of support of the feature.
+*** '''Description:''' N/A
-* '''Geometric representation:''' - Section describes whether or not the engineering format supports geometric representations.
+* '''Geometric representation:'''
-** '''Implicit representation:''' - Section describes whether or not the engineering format supports implicit representations.
+** '''Implicit representation:'''
-*** '''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.
+*** '''Implicit surfaces:'''
-**** '''Is Supported:''' [[File Classification Implicit Surfaces - Is Supported::]] - Is the feature supported in the engineering format?
+**** '''Is Supported:''' False
-**** '''Description:''' [[File Classification Implicit Surfaces - Description::]] - This field is used to describe the support or lack of support of the feature.
+**** '''Description:''' N/A
-*** '''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.
+*** '''Implicit curves:'''
-**** '''Is Supported:''' [[File Classification Implict Curves - Is Supported::]] - Is the feature supported in the engineering format?
+**** '''Is Supported:''' False
-**** '''Description:''' [[File Classification Implicit Curves - Description::]] - This field is used to describe the support or lack of support of the feature.
+**** '''Description:''' N/A
-*** '''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.
+*** '''Point set:'''
-**** '''Is Supported:''' [[File Classification Point Set - Is Supported::]] - Is the feature supported in the engineering format?
+**** '''Is Supported:''' True
-**** '''Description:''' [[File Classification Point Set - Description::]] - This field is used to describe the support or lack of support of the feature.
+**** '''Description:''' The renderable point group contains a set of renderable point sets. Each renderable point set is associated with a different shader list in the shader group. The renderable point set consists of a vertex array. Each vertex in the vertex array contains all of the per vertex attributes (such as position, normal, texture coordinates, etc.) for that vertex. Each vertex in
-** '''Mesh:''' - Section describes whether or not the engineering format supports mesh.
+the vertex array is drawn according to the parameters of the shaders in the shader list.
-*** '''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
+** '''Mesh:'''
-**** '''Is Supported:''' [[File Classification Mainfold Surface Meshes - Is Supported::]] - Is the feature supported in the engineering format?
+*** '''Manifold surface meshes:'''
-**** '''Description:''' [[File Classification Manifold Surface Meshes - Description::]] - This field is used to describe the support or lack of support of the feature.
+**** '''Is Supported:''' False
-*** '''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
+**** '''Description:''' N/A
-**** '''Is Supported:''' [[File Classification Manifold Volume Meshes - Is Supported::]] - Is the feature supported in the engineering format?
+*** '''Manifold volume meshes:'''
-**** '''Description:''' [[File Classification Manifold Volume Meshes - Description::]] - This field is used to describe the support or lack of support of the feature.
+*** '''Is Supported:''' False
-*** '''Non-manifold meshes:''' - Can the format support non-manifold meshes? Example: A format that supports meshes that are not manifolds
+**** '''Description:''' N/A
-**** '''Is Supported:''' [[File Classification Non-manifold Meshes - Is Supported::]] - Is the feature supported in the engineering format?
+*** '''Non-manifold meshes:'''
-**** '''Description:''' [[File Classification Non-manifold Meshes - Description::]] - This field is used to describe the support or lack of support of the feature.
+*** '''Is Supported:''' False
-** '''Parametric representation:''' - Section describes whether or not the engineering format supports parametric representations.
+**** '''Description:''' N/A
-*** '''Parametric surfaces:''' - Can the format support parametric surfaces? Example: A format that can contain surfaces that are generated with parametric equations supports parametric surfaces.
+** '''Parametric representation:'''
-**** '''Is Supported:''' [[File Classification Parametric Surfaces - Is Supported::]] - Is the feature supported in the engineering format?
+*** '''Parametric surfaces:'''
-**** '''Description:''' [[File Classification Parametric Surfaces - Description::]] - This field is used to describe the support or lack of support of the feature.
+*** '''Is Supported:''' False
-*** '''Parametric curves:''' - Can the format support parametric curves? Example: A format that can contain curves that are generated with parametric equations supports parametric curves.
+**** '''Description:''' N/A
-**** '''Is Supported:''' [[File Classification Parametric Curves - Is Supported::]] - Is the feature supported in the engineering format?
+*** '''Parametric curves:'''
-**** '''Description:''' [[File Classification Parametric Curves - Description::]] - This field is used to describe the support or lack of support of the feature.
+*** '''Is Supported:''' False
-** '''Contour sets:''' - Can the format support contour sets?
+**** '''Description:''' N/A
-*** '''Is Supported:''' [[File Classification Contour Sets - Is Supported::]] - Is the feature supported in the engineering format?
+** '''Contour sets:'''
-*** '''Description:''' [[File Classification Contour Sets - Description::]] - This field is used to describe the support or lack of support of the feature.
+*** '''Is Supported:''' False
-** '''NURBS:''' - Can the format support Non Uniform Rational Basis Splines? Examples: The engineering formats IGES, STEP, ACIS, and PHIGS
+**** '''Description:''' N/A
-*** '''Is Supported:''' [[File Classification NURBS - Is Supported::]] - Is the feature supported in the engineering format?
+** '''NURBS:'''
-*** '''Description:''' [[File Classification NURBS - Description::]] - This field is used to describe the support or lack of support of the feature.
+*** '''Is Supported:''' True
-* '''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.
+*** '''Description:''' This extension adds a Free-Form Surface Object to the U3D File Format specification that adds support for Uniform and Non-Uniform, Rational and Non-Rational Free-Form Curves and Surfaces.
-** '''Is Supported:''' [[File Classification Multi-resolution Models - Is Supported::]] - Is the feature supported in the engineering format?
+* '''Multi-resolution models:'''
-** '''Description:''' [[File Classification Multi-resolution Models - Description::]] - This field is used to describe the support or lack of support of the feature.
+** '''Is Supported:''' True
-* '''Dynamics:''' - Section describes whether or not the engineering format supports dynamics.
+** '''Description:''' CLOD Description describes the range of resolutions available for the continuous level of detail mesh.
-** '''Kinematics:''' - Can the format support kinematics? Example: Does the format allow model parts to rotate?
+* '''Dynamics:'''
-*** '''Is Supported:''' [[File Classification Kinematics - Is Supported::]] - Is the feature supported in the engineering format?
+** '''Kinematics:'''
-*** '''Description:''' [[File Classification Kinematics - Description::]] - This field is used to describe the support or lack of support of the feature.
+*** '''Is Supported:''' True
-** '''Assembly:''' - Can the format support assembly? Example: Does the format allow the assembly instructions to be explicitly specified with a model?
+*** '''Description:''' Bone structure used in animation and inverse kinematics
-*** '''Is Supported:''' [[File Classification Assembly - Is Supported::]] - Is the feature supported in the engineering format?
+** '''Assembly:'''
-*** '''Description:''' [[File Classification Assembly - Description::]] - This field is used to describe the support or lack of support of the feature.
+*** '''Is Supported:''' False
-** '''Force(s):''' - Can the format support forces? Example: Does the format support acceleration forces?
+**** '''Description:''' N/A
-*** '''Is Supported:''' [[File Classification Force - Is Supported::]] - Is the feature supported in the engineering format?
+** '''Force(s):'''
-*** '''Description:''' [[File Classification Force - Description::]] - This field is used to describe the support or lack of support of the feature.
+*** '''Is Supported:''' False
-* '''Boundary representation''' - Can the format support models with boundary representations?
+**** '''Description:''' N/A
-** '''Manifold surface boundary representations:''' - Can the format support manifold surface boundary representations? Example: The engineering format STEP
+* '''Boundary representation'''
-*** '''Is Supported:''' [[File Classification Manifold Surface Boundary Representation - Is Supported::]] - Is the feature supported in the engineering format?
+** '''Manifold surface boundary representations:'''
-*** '''Description:''' [[File Classification Manifold Surface Boundary Representation - Description::]] - This field is used to describe the support or lack of support of the feature.
+*** '''Is Supported:''' False
-** '''Manifold volume boundary representations:''' - Can the format support manifold volume boundary representations? Example: The engineering format STEP
+**** '''Description:''' N/A
-*** '''Is Supported:''' [[File Classification Manifold Volume Boundary Representation - Is Supported::]] - Is the feature supported in the engineering format?
+** '''Manifold volume boundary representations:'''
-*** '''Description:''' [[File Classification Manifold Volume Boundary Representation - Description::]] - This field is used to describe the support or lack of support of the feature.
+*** '''Is Supported:''' False
-** '''Non-manifold boundary representations:''' - Can the format support non-manifold boundary representations? Example: The engineering format STEP
+**** '''Description:''' N/A
-*** '''Is Supported:''' [[File Classification Non-manifold Boundary Representation - Is Supported::]] - Is the feature supported in the engineering format?
+** '''Non-manifold boundary representations:''' *** '''Is Supported:''' False
-*** '''Description:''' [[File Classification Non-manifold Boundary Representation - Description::]] - This field is used to describe the support or lack of support of the feature.
+**** '''Description:''' N/A
-* '''Material transparency:''' - Can the format support transparency? Example: Does the format allow models to have a clear window in a car?
+* '''Material transparency:'''
-** '''Is Supported:''' [[File Classification Material Transparency - Is Supported::]] - Is the feature supported in the engineering format?
+** '''Is Supported:''' True
-** '''Description:''' [[File Classification Material Transparency - Description::]] - This field is used to describe the support or lack of support of the feature.
+** '''Description:''' Opacity is a measure of on object’s transparency. The value is used when alpha blending. Higher Opacity means the object is less transparent and objects behind it will be less visible. The normal range of opacity is 0.0 (invisible) to 1.0 (completely opaque). Values outside this range are allowed.
-'''References:''' [[References::]] - A list of references regarding any aspects of this engineering format; any reading material supplemental to this page.
+'''References:'''

@@ Line 41: / Line 41: @@
 Surfaces.
-'''Example(s):''' [[Example::Example Template]] - Information and example models of the engineering format.
+'''Example(s):'''
 '''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
 ** Siemens PLM Software [[http://en.wikipedia.org/wiki/Siemens_PLM_Software]] Process Simulate
-* '''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.
 *** '''Is Supported:''' [[File Classification Raster Data 2D - Is Supported::]] - Is the feature supported in the engineering format?

@@ Line 6: / Line 6: @@
 '''Date released:''' June 2007
-'''Date:''' December 2004
+'''Date:''' August 2005
 '''Creator(s):''' Ecma International [[http://www.ecma-international.org/default.htm]]
@@ Line 32: / Line 32: @@
 '''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
+* 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.
 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.
@@ Line 44: / Line 43: @@
 '''Example(s):''' [[Example::Example Template]] - Information and example models of the engineering format.
-'''Identifier:''' [[Identifier::]] - A URL or other identifier that refers to the engineering format.
+'''Identifier:''' Standard ECMA-363 [[http://www.ecma-international.org/publications/standards/Ecma-363.htm]]
-'''Documentation:''' [[Documentation::Documentation Template]] - Information in general about the engineering format.
+'''Documentation:''' 4st Edition : June 2007 [[http://www.ecma-international.org/cgi-bin/counters/unicounter.pl?name=ECMA-363_4thedition&deliver=http://www.ecma-international.org/publications/files/ECMA-ST/ECMA-363%204th%20edition.pdf]]
-'''File Extensions:''' [[File Extension::]] - Extensions of the engineering format, excluding the dot.
+'''File Extensions:''' .u3d
-'''Applications:''' - Applications that the engineering format uses.
+'''Applications:'''
-* '''Native application(s):''' [[Native Application::Engineering Format Application Template]] - Applications which are primarily designed to specifically run this engineering format.
+* '''Native application(s):'''
 * '''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.

@@ Line 25: / Line 25: @@
 '''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 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 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. [[http://www.ecma-international.org/publications/standards/Ecma-363.htm]]
+* The U3D file format specification does not address run-time extensibility of an implementation of the U3D architecture. [[http://www.ecma-international.org/publications/standards/Ecma-363.htm]]
 '''History:'''