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

From Web3D.org
Jump to: navigation, search
m
m
Line 3: Line 3:
 
* '''Standards and implementations'''
 
* '''Standards and implementations'''
 
** Approved ISO standard [http://www.web3d.org/files/specifications/19776-3/V3.2/Part03/X3D_Binary.html Compressed Binary Encoding (CBE) for X3D]
 
** Approved ISO standard [http://www.web3d.org/files/specifications/19776-3/V3.2/Part03/X3D_Binary.html Compressed Binary Encoding (CBE) for X3D]
** Optional gzip compression and MIME Type definitionsptional gzip compression and MIME Type definitions are included for [http://www.web3d.org/files/specifications/19776-1/V3.2/Part01/concepts.html#X3DFilesAndTheWorldWideWeb .x3dz/.x3d.gz], [http://www.web3d.org/files/specifications/19776-2/V3.2/Part02/concepts.html#ClassicVRMLEncodedX3DFilesAndWWW .x3dvz/.x3dv.gz] and [http://www.web3d.org/files/specifications/19776-3/V3.1/Part03/concepts.html#X3DFilesAndTheWorldWideWeb .x3db.gz] file extensions
+
** Optional gzip compression and MIME Type definitionsptional gzip compression and MIME Type definitions are included for XML encoding [http://www.web3d.org/files/specifications/19776-1/V3.2/Part01/concepts.html#X3DFilesAndTheWorldWideWeb .x3dz/.x3d.gz], ClassicVRML encoding [http://www.web3d.org/files/specifications/19776-2/V3.2/Part02/concepts.html#ClassicVRMLEncodedX3DFilesAndWWW .x3dvz/.x3dv.gz] and Compressed Binary encoding [http://www.web3d.org/files/specifications/19776-3/V3.1/Part03/concepts.html#X3DFilesAndTheWorldWideWeb .x3db.gz] file extensions
 
*** Original compression technique of gzip compression for .wrl VRML called .wrz (TODO need reference)
 
*** Original compression technique of gzip compression for .wrl VRML called .wrz (TODO need reference)
 
** Based on ISO standard [http://en.wikipedia.org/wiki/Fast_Infoset Fast Infoset (FI)] for XML compression
 
** Based on ISO standard [http://en.wikipedia.org/wiki/Fast_Infoset Fast Infoset (FI)] for XML compression

Revision as of 02:42, 15 December 2011

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

  • Networking
    • Several capabilities are available 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
    • 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 patented submissions to working group while under consideration, 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
  • Looking ahead
    • Web3D's X3D and CAD Working Groups each have member commitments to pursue this continued innovative work in 2012
    • TODO: A workshop might be a rapid way to compare candidate technologies that might complete these capabilities
    • X3D appears to have have an 80% solution already available that meets various requirements for a general 3D transmission format