Difference between revisions of "X3D Binary Compression Capabilities and Plans"

From Web3D.org
Jump to: navigation, search
Line 4: Line 4:
==Call For Contributions==
==Call For Contributions==
X3D solutions currently support a wide range of author requirements.   
X3D solutions currently support a wide range of author requirements.   
Further improvements and standards-based partnerships are possible for achieving broader industry interoperability.   
Further improvements and standards-based partnerships are possible for achieving broader industry interoperability.   

Revision as of 04:32, 2 April 2013

Motivation. Lots of work has already been accomplished using the X3D Compressed Binary Encoding (CBE) standard. X3D has numerous coherent approaches already available that meet author requirements for a general Web-based 3D transmission format. We are working to demonstrate and standardize multiple interoperable improvements in 2013.

Call For Contributions

X3D solutions currently support a wide range of author requirements. Further improvements and standards-based partnerships are possible for achieving broader industry interoperability.

To accomplish these achievable goals, we are building a draft Call For Contributions to further advance these technical capabilities for X3D.

  • The original X3D Compressed Binary Encoding Request For Proposals (RFP) from August 2003 can serve as a baseline for this new document. We are now requesting public review of those prior Requirements as part of drafting this Call
  • We will issue a Call For Contributions in April, review frequently, then review submissions at the Web3D Conference in June
  • Our strategic goal is to accomplish these reviews and integration during calendar year 2013.

Separate administrative requirements are necessary for all technology submissions prior to consideration.

  • The Intellectual Property Rights (IPR) protections for X3D specification.
  • Patented technologies can be considered, but only when eventual use will be royalty free for X3D use (if eventually accepted).
  • Submitters can restrict access to patented submissions during member-only working group review, if desired.

Defining example Use Cases and work-flow authoring requirements for compressed X3D scenes is helpful, providing useful criteria for evaluating technical capabilities. Use cases enable us to determine whether each possible improvement effectively meets a declared need.

  • TODO Web3D members will document common workflow practices and build an updated set of use cases

Existing Compression Usage for X3D and VRML97

A solid foundation exists for continued progress.

  • Approved ISO standard Compressed Binary Encoding (CBE) for X3D.
  • Optional, alternative gzip compression and MIME Type definitions for X3D.
  • Optional, alternative gzip compression for VRML97.
    • Original compression technique of applying gzip to .wrl compressed VRML97 files was called .wrz.
    • This emerged as a common practice when gzip was originally used. No formal specification of .wrz or corresponding mime type was produced.
    • Occasionally authors might also gzip .wrl files while retaining the .wrl file extension.

Polygon Reduction and Geometric Compression

Formal specifications:

Best practices and examples:

  • CAD Distillation Filter (CDF) technique allowing successive refinement of large X3D scenes into tighter X3D scenes.
  • A highly effective exemplar algorithm for Coding Polygon Meshes as Compressable ASCII is demonstrated in the Experimental Binary Compression examples.
  • Multiple CAD Distillation Filter (CDF) algorithms implemented in Xj3D and X3D-Edit as open-source.
  • The Chisel VRML Optimisation Tool has an excellent set of data-reduction tools for VRML that are worth repeating for X3D.
  • Multiple other conversion and translation tools available with supporting capabilities.
  • Following submission of candidate technologies, we will build a table of 3D graphics compression benchmark results, providing a full comparison of existing tools (compression ratio, computational complexity, memory usage, etc.)
  • MPEG4 capabilities are welcome, if IPR prerequisites are met. Discussion to date has indicated that Royalty Free (RF) solutions are not available.
  • TODO: Fraunhofer has multiple efforts reported in academic papers, need to confirm that all are reflected here

Data-Centric Binary Encodings

The X3D Compressed Binary Encoding (CBE) uses the ISO Fast Infoset (FI) standard to compress XML information, which is how the CBE maintains equivalent expressive power with other X3D scene encodings.

Network Streaming

  • Multiple capabilities are already available in X3D for flexible network transmission.
    • Anchor, Inline, LOD, LoadSensor, Script and Prototype nodes support successive retrieval of content once initial model is displayed.
  • TODO: Willing to consider further addition of progressive-mesh geometric streaming technologies, perhaps by a public Call for Contributions. Note however that an effective progressive-mesh approach is likely dependent on the availability of a corresponding mesh compression algorithm.
  • TODO: Use cases and test examples can demonstrate whether http/https and local-file url retrieval are sufficient for a network protocol.
    • Other network protocols (Web sockets, P2P channels, etc.) might be possible, but only if security restrictions can be handled satisfactorily.
    • Javascript Object Notation (JSON) might be suitable for simple streaming of X3D scene-graph data via Script node or external HTML page, which can be useful for progressive mesh and other incremental network-update approaches. Such possibilities are being actively discussed on the x3d-public mailing list.
    • JSON might have other uses as well, see Khronos work on Collada2JSON and glTF.
    • Further investigation is in progress.

X3D Implementations

The following tools implement the X3D Compressed Binary Encoding (CBE) standard.

We do not currently have a compression benchmark suite. We plan to automate conversions and comparisons, using Xj3D XIOT and other submissions, for cross-check interoperability and validation testing. We intend to automate such a suite using our many example scenes and nightly build (continuous integration) processes. This will automate the production of results summarized in the compression performance tables constructed as part of the call for technologies.

Looking Ahead

  • Web3D's X3D and CAD Working Groups each have member commitments to pursue this continued innovative work in 2013.
  • We are keen to consider common, sharable technical strategies with MPEG-4 and Collada. Web3D Consortium has been waiting for a response from The Khronos Group and MPEG standards SC 29 committee since a joint meeting at SIGGRAPH conference August 2012. To date, formal MPEG4 communications have indicated that a royalty-free solution is not possible.
  • TODO: An open meeting on 3D Transmission Formats might be a useful way to compare candidate technologies to complete these capabilities. We are preparing to hold a collaboration workshop immediately preceding the Web3D 2013 conference on Wednesday 19 June 2013 in San Sebastian Spain.