[x3d-public] V4.0 Open discussion/workshop on X3D HTML integration
Philipp Slusallek
philipp.slusallek at dfki.de
Thu Jun 16 22:02:02 PDT 2016
[Resent, as the original email was apparently not relayed through the list]
Hi everyone,
I am not sure that I will be able to join the meeting, so let me present
some of our ideas in this context by email already. As you might know we
have done a lot of work on declarative 3D -- in the alternate universe
called XML3D. The reason for this unfortunate split, lies in the fact
that it has been rather difficult to bridge the gap between our ideas of
a minimum and generic extensions to HTML-5 to enable declarative 3D
while staying as close as possible to the current Web technology stack
on the one side and the need for backward compatibility that people
strived for in X3D(OM).
Now, there may be a quite interesting these two world views could be
resolved with each other. The basic idea for that was already proposed
and discussed between us and the X3DOM group: Merging X3DOM and XML3D by
identifying the (significant and large!) common core and a layering
X3D/XMl3D compatible interfaces on top of this (or eventually
identifying common set of Dec3D elements). Unfortunately, this idea was
not really picked up by anyone back then.
However, with newer technology like WebComponent (a version of
prototypes in HTML5) this now becomes a highly interesting and much more
practical option. We are actually exploring this right now. First
results look very promising and a first paper on this has just been
accepted for Web3D this year.
At the core of this approach we are using a clean interface to rendering
engines, where we use Three.js a default option. Other engines like game
engines or ray tracing etc. would be alternatives. (We are also
exploring server-based real-time ray tracing based on a generic
real-time synchronization layer between scene descriptions as one example.)
On top of this is a slightly refined generic data handling layer that is
derived from our Xflow. Xflow has been tremendously useful for us and
makes data management significantly easier than with the specialized
nodes in X3D. It is the perfect building block for WebComponents. We are
also integrating into this layer a programmable data processing engine
that is derived from our flexible shade.js compiler for programmable
shading.
Everything on top of this is essentially fair game for WebComponents
(similar to a-frame, but with mny more options). The more specialized
and often domain-specific nodes from X3D would be prime examples for
this. We have actually started to implemented some of the basic X3D
nodes already, plus the non-core XML3D nodes. Pretty much along the
lines of what we discussed with X3DOM several years ago. Given the
powerful underlying engine, it actually becomes rather straight forward
to implement these nodes as Web Components, especially the X3DOM subset.
But we are just starting.
We are even exploring having a public repository of WebComponents that
people could develop independently and that get automatically loaded
when referenced in a scene (subject to some security policy, of course).
Talk about leveraging the power of the distributed web :-).
We are finalizing the paper for the final version right now but can make
a preprint available as soon as this is ready. People would be more than
welcome to help design and develop this further. Maybe this could also
be an interesting basis for some of the work on X3D V4?
Best,
Philipp
Am 01.06.2016 um 00:40 schrieb Roy Walmsley:
> *X3D HTML integration*
>
> * *
>
> *X3D V4.0 Open discussion/workshop*
>
> * *
>
> *June 8^st 2016 at 1500-1700 UTC (0800-1000 PDT, 1500-1700 GMT,
> 1700-1900 CET)*
>
> * *
>
> A discussion/workshop on version 4.0 of X3D which aims to consider the
> following questions, and suggest potential solutions.
>
>
>
> · What level of X3D integration into HTML5 do we want?
>
> o Do we want to be fully integrated like SVG?
>
> · Do we want/need a DOM spec? If so:
>
> o Which DOM version should it be based on?
>
> o Do we want to fully support all DOM/HTML features?
>
> · Do we want to maximize the backwards compatibility of V4.0
> with V3.3? Or break away completely?
>
> o Do we want to retain SAI?
>
> · What features do we want? For example,
>
> o How is animation to be handled? The X3D way of TimeSensor and
> ROUTEs, or an HTML way, such as CSS3 animations, or else JavaScript?
>
> o How is user interaction to be handled? The X3D way of Sensors, or
> the HTML way with event handlers?
>
> o Do we need any different nodes? One example might be a mesh node?
>
> o Do we want Scripts and Prototypes in HTML5?
>
> o How do we want to handle styling?
>
> · What profile(s) do we need for HTML?
>
>
>
> The discussion/workshop will be held on the Web3D teleconference line.
> It is open to anyone interested in X3D. Please e-mail
> roy.walmsley at ntlworld.com <mailto:roy.walmsley at ntlworld.com> or
> brutzman at nps.edu <mailto:brutzman at nps.edu> for teleconference details.
>
>
>
> If you can’t join in the discussion, but would still like to contribute
> to the debate, your comments would be welcomed on the X3D public mailing
> list at x3d-public at web3d.org <mailto:x3d-public at web3d.org>.
>
>
>
> Roy Walmsley
>
> X3D WG Co-chair
>
>
>
> _______________________________________________
> x3d-public mailing list
> x3d-public at web3d.org
> http://web3d.org/mailman/listinfo/x3d-public_web3d.org
>
--
-------------------------------------------------------------------------
Deutsches Forschungszentrum für Künstliche Intelligenz (DFKI) GmbH
Trippstadter Strasse 122, D-67663 Kaiserslautern
Geschäftsführung:
Prof. Dr. Dr. h.c. mult. Wolfgang Wahlster (Vorsitzender)
Dr. Walter Olthoff
Vorsitzender des Aufsichtsrats:
Prof. Dr. h.c. Hans A. Aukes
Sitz der Gesellschaft: Kaiserslautern (HRB 2313)
VAT/USt-Id.Nr.: DE 148 646 973, Steuernummer: 19/673/0060/3
---------------------------------------------------------------------------
--
-------------------------------------------------------------------------
Deutsches Forschungszentrum für Künstliche Intelligenz (DFKI) GmbH
Trippstadter Strasse 122, D-67663 Kaiserslautern
Geschäftsführung:
Prof. Dr. Dr. h.c. mult. Wolfgang Wahlster (Vorsitzender)
Dr. Walter Olthoff
Vorsitzender des Aufsichtsrats:
Prof. Dr. h.c. Hans A. Aukes
Sitz der Gesellschaft: Kaiserslautern (HRB 2313)
VAT/USt-Id.Nr.: DE 148 646 973, Steuernummer: 19/673/0060/3
---------------------------------------------------------------------------
More information about the x3d-public
mailing list