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

From Web3D.org
Jump to: navigation, search
m (Polygon reduction and geometric compression)
m (Network streaming)
Line 35: Line 35:
 
** Submitters can restrict access to patented submissions during member-only working group review, if desired
 
** Submitters can restrict access to patented submissions during member-only working group review, if desired
 
* TODO: Use cases and test examples can demonstrate whether http/https and local-file url retrieval are sufficient for a network protocol
 
* 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
+
** Other network protocols (Web sockets, P2P channels, etc.) might be possible, but only if security restrictions can be handled satisfactorily
  
 
== X3D Implementations ==
 
== X3D Implementations ==

Revision as of 22:10, 25 April 2012

Synopsis. Lots of work has been accomplished towards proper support of X3D Binary Compression for a wide variety of potential uses.

X3D appears to have have an 80% solution already available that meets various requirements for a general 3D transmission format.

Compression Standards

Polygon reduction and geometric compression

Binary 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.
  • 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
  • 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

X3D Implementations

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

Looking ahead

  • Web3D's X3D and CAD Working Groups each have member commitments to pursue this continued innovative work in 2012
  • TODO: An open workshop on 3D Transmission Formats might be a thorough way to compare candidate technologies to complete these capabilities
  • Consider common, sharable technical strategies with MPEG-4 and Collada