Difference between revisions of "Web3D 2014 Workshops on X3D Evolution/Revolution"

From Web3D.org
Jump to: navigation, search
(X3D JSON)
(X3D JSON)
Line 86: Line 86:
  
 
* Technical quicklook
 
* Technical quicklook
 
 
** '''[http://www.json.org JSON]''': JavaScript Object Notation as an X3D encoding
 
** '''[http://www.json.org JSON]''': JavaScript Object Notation as an X3D encoding
 
 
** [http://web3d.org/pipermail/x3d-public_web3d.org/2014-July/thread.html#2854 assessment email thread]
 
** [http://web3d.org/pipermail/x3d-public_web3d.org/2014-July/thread.html#2854 assessment email thread]
 
 
** NPS will perform a detailed experimental comparison of ''data.json.gz'' to ''data.xml.exi'' examples
 
** NPS will perform a detailed experimental comparison of ''data.json.gz'' to ''data.xml.exi'' examples
 
 
** Relation to [https://www.khronos.org/gltf GlTF]
 
** Relation to [https://www.khronos.org/gltf GlTF]
  

Revision as of 21:00, 7 August 2014

The Web3D 2014 Conference program schedule includes multiple X3D Workshops on Future Graphics Standards.

Moderators: Don Brutzman (Naval Postgraduate School), Dick Puk (Intelligraphics) and Leonard Daly (Daly Realism).

This page elaborates on the agenda topics. We are collaboratively adding key points. Volunteer scribes will keep minutes so that a workshop report emerges.

X3D Compressed Binary Encoding (CBE) Geometric-Compression Algorithm Candidates

Scheduled time: 0900-1030. Goal outcomes:

Review and improve all published plans & milestones

Review Fraunhofer geometric-compression approach in detail, compare to all of the established X3D metrics

  • Demos, proposals

Summary of Efficient XML Interchange (EXI) data compression and XML Security to replace Fast Infoset (FI) in existing X3D CBE Specification

Fast Infoset (FI)

Fast Infoset was completed a few years before EXI. It compared favorably to 40 other forms of compression as part of the XML Binary Compression (XBC) effort leading up to EXI. Nevertheless FI is less efficient than EXI.

FI is used in the X3D Compressed Binary Encoding (CBE). EXI can directly replace it in the compression and decompression algorithms.

Efficient XML Interchange (EXI)

"Efficiency" means both size and speed. EXI has demonstrated compaction that always meets or beats the most commonly used compression techniques (zip and gzip). Additionally, because EXI decompression goes straight into memory rather than string characters, which then require significant additional parsing, decoding EXI is many times faster than other techniques. This approach also reduces memory requirements and power consumption on small devices. Alternative bit-centric compression schemes cannot take full advantage of those characteristics.

The World Wide Web Consortium (W3C) supervises these open standardization efforts with contributions by many companies, universities, agencies and individuals to continually improve these capabilities.

NPS student-driven research continues to provide significant explorations of XML-based compression and decompression techniques. Many opportunities are emerging.

Currently NPS participates in EXI working-group activities as liaison member for Web3D Consortium work.

OpenEXI Open-Source Java Implementation

We support open Web standards and actively contribute to the OpenEXI project.

Shall we have a public mesh “contest” or “bakeoff” to confirm that proposed approaches are ready for prime time?

  • Discussion please.

Decide on readiness to proceed with next milestones

  • Multiple tasks await, and sequencing among X3D 3.4, X3D 4.0 and MAR appears to be necessary.
  • Each of these areas appear to be pursuable in tandem without interference.
  • What work is proceeding?
  • Discussion please.

X3D 3.4 Evolution

Scheduled time: 1030-1200. Goal outcomes:

Review all planned technology additions

Determine technology and specification contributors, responsible working groups

  • Working groups and individual contributions are currently defining future goals and requirements.
  • CAD
  • H-Anim
  • Geospatial

X3D JSON

  • Technical quicklook
    • JSON: JavaScript Object Notation as an X3D encoding
    • assessment email thread
    • NPS will perform a detailed experimental comparison of data.json.gz to data.xml.exi examples
    • Relation to GlTF
  • Streaming considerations?
  • Where to define an X3D JSON encoding in X3D Specifications

Achieving two independent implementations and X3D scene conformance tests

Next steps and 2014 timeline

Lunch discussions

Scheduled time: 1200-1300. Participants will order lunch in the morning, sandwiches to be delivered to a good spot near the meeting room.

X3D 4.0 / X3DOM / HTML5 Revolution

Scheduled time: 1300-1500. Goal outcomes:

Review and improve all published plans & milestones

  • Major technology under consideration: HTML5/Declarative 3D/X3DOM
  • Major technology under consideration: Mixed and Augmented Reality (MAR) Continuum (formerly ARC)

Confirm status of technology components, add to v3.4 list as appropriate

Evolution/convergence strategy for X3D 4.0, X3DOM, HTML5

Lots of great progress! What's next? Discussion.

Mixed Augmented Reality (MAR) Reference Model

Status and plans quicklook.

  • ISO SC24/SC29 MAR Joint Ad Hoc Group (JAHG), Gerry Kim and Marius Preda
  • X3D MAR implementation exemplar efforts, Gun Lee and Timo Engelke
  • Flag any potential conflicts

Decide on next steps and milestones for 2014

  • Preview: ISO/IEC JTC1 SC24 meeting agenda, 18-22 August 2014, Seattle Washington

BIM/AEC/AM/CAD Initiatives

X3D Computer-Aided Design (CAD) Working Group

  • Agenda review and welcome discussion
  • Our game plan today: key points, demo, talk! repeat for each topic.

Progress and planned work

Recent activities and developments

  • Summary of accomplishments for past year
  • Standards group liaisons
  • Architecture Engineering Construction (AEC)
    • AEC Hackathon
    • CIS/2
  • Building Information Modeling (BIM)
    • BimServer by Dave Arendash
  • Additive Manufacturing File Format (AMFF)
    • Track down and link our meeting minutes assessment
    • Can we perform this work to map transformations between the two standards?
  • Cultural Heritage
    • Workshop, keynote, other activity coming up
    • Lots of shared imperatives for metadata modeling within X3D scenes

Additional topics welcome

Looking ahead

For the next year:

  • What common work can we do together?
  • What is our timetable of goals?
  • Who else should we be talking to?
  • What new features are needed?