[x3d-public] X3Dng Architecture Design

[Joe D Williams]

> ... capabilities made available in the X3D files are either 
> insufficient (e.g., lack of deformable skin animation) ..

Leonard, if you keep saying that [lack of deformable skin animation] I 
must report you for abuse of the HAnim and X3D standards.

Specifically, HAnim and X3D include two tools for deformable skin 
(mesh) animation: the skeleton-skin hookups where the controllers are 
Joint rotations, and the Displacer where the controller is a numerical 
weight input. And they can work together.

If you are not convinced that X3D does deformable skin animation using 
the same types of documentatation as every basic skeletal animation 
tool uses, then you have not even studied the problem or the standard, 
or even any examples.

> Vinton G. Cerf in the October 2016 issue of Communications of ACM 
> [1] laments that while significant art and cultural artifacts are 
> available from as far back as 17,300 years ago, our current content 
> is turning to unusable and perhaps unreadable dust during our lives

What did Dr Cerf wish to do abour that? Why is that true for you for 
X3D? How is the X3D format not durable? Depends upon the storage 
medium since X3D is juman readable. True, other archival formats are 
not so readable so are they are in more danger than X3D?
If you want want just a bunch of data sets with some validation and 
without much of a runtime, then look at collada.
X3D will always be able to use data from collada.

> The proposed systems architecture is to split the archival and 
> display into two separate categories.

Sorry, what is the proposal? Do you wish to split the data and the 
names of data?
X3D is an archival format, it just happens to also have a high 
performance runtime.
That should not be a penalty or reason to somehow create two different 
versions.

> It seems inescapable that our society will need to find its own 
> formula for underwriting the cost of preserving knowledge in media 
> that will have some permanence.

Smithsonian? Google drive? Usually, he would't talk unless he had some 
sort of plan in mind.

If you are interested in the idea that X3D should accept many 
different forms of data, then look over Don's shoulder as he is 
working on implementation of a plan to convert and use typical mocap 
data.

Good Luck,
Joe



----- Original Message ----- 
From: "Leonard Daly" <Leonard.Daly at realism.com>
To: "X3D Public" <x3d-public at web3d.org>
Sent: Tuesday, October 25, 2016 8:43 PM
Subject: [x3d-public] X3Dng Architecture Design


>I have published the next post on X3Dng. This one covers the systems
> architecture of how X3D can be used going forward. This post begins 
> to
> describe the systems architecture where archived content is 
> separated
> from display content.  The post is at
> http://realism.com/blog/purpose-x3d-architecture.
>
> The next posts will be a more detailed description of the Archive 
> and
> Display. After that I will start to get into the nodes supporting 
> both
> components.
>
>
> -- 
> *Leonard Daly*
> 3D Systems & Cloud Consultant
> LA ACM SIGGRAPH Chair
> President, Daly Realism - /Creating the Future/
>


--------------------------------------------------------------------------------


> _______________________________________________
> x3d-public mailing list
> x3d-public at web3d.org
> http://web3d.org/mailman/listinfo/x3d-public_web3d.org
>