[x3d-public] Proposed new Profile

[Leonard Daly]

It has been suggested that I expand on my blog post 
(http://realism.com/blog/proposed-x3d-profile-static-model) to include 
all X3D Nodes and how they fit into the existing specification and 
profile/component structure and where this profile differs. That work is 
available in the shared spreadsheet at 
https://docs.google.com/spreadsheets/d/1NjtfeaJl_JANCXKa0iFMW-e8S9crq4tVLViv-vPzdQw/edit?usp=sharing. 


In addition to the nodes in the proposed profile, this spreadsheet lists 
all X3D V3.3 nodes, their component, level (where the major 
functionality exists), and a subset of the existing X3D profiles showing 
which profiles contain that node. A [terse] reason is provided for any 
node not included in either the static or animated profile. In some 
cases an alternate node is listed.

The animated model profile still needs development. Information in this 
spreadsheet should not be taken as the definition of such a profile. At 
this time, it is just preliminary.

Leonard Daly



> Greg,
>
> The intent of the model profile is just to contain model information. 
> Viewpoints (ortho or otherwise) and ClipPlane  is not intrinsic to the 
> model, and (I believe) should not be included.
>
> ColorRGBA and Color are both included.
>
> I intentionally left out many/most of the other items listed because I 
> believed that the digital content creation (DCC) tool would easily 
> create 2D shapes. Can you please describe how you use the 2D geometry 
> nodes? Is there a reason that the various Line nodes could not be used?
>
> An issue I have with the pre-defined shapes (Box, Cylinder, Sphere, 
> Text, etc.) is that there are many ways to triangulate these. What one 
> person may consider to be a good triangulation is too course or too 
> fine for another and may also depend on the target device. Is 
> triangulation of these shapes an issue for you? Also, Text has the 
> added disadvantage of font management.
>
> I did not address X3D Statements. I agree that the UNIT statement is 
> an important part of a model format.
>
> Leonard Daly
>
>
>
>> On 1/22/2018 8:43 AM, Leonard Daly wrote:
>>>
>>> The existing X3D profiles were designed for run-time environments. 
>>> Since those original definitions, the marketplace has changed. There 
>>> is need of an open, standardized formats for models that supports 
>>> conversion to and from existing formats such as FBX, OBJ, glTF, and 
>>> others. There are some tools that do that conversion, but tend to be 
>>> expensive or limited in capability. To address this hole in the 3D 
>>> eco-system, I am proposing new profiles to handle the archive 
>>> storage for models. The first proposal is for static models. These 
>>> are models without articulation, joints, sliders, etc. The profile 
>>> supports the way models are built in the industrial/professional 
>>> world of games, entertainment, CAD, and medical -- at least to the 
>>> best of my understanding.
>>>
>>> The collection of nodes handles output functionality from Maya and 
>>> Blender plus other tools. It includes some advanced structures such 
>>> as NURBS, CAD, and Volume; and does not include simple structures as 
>>> simple geometry (Box, Sphere, etc.). I looked at what the tools 
>>> output and could not find instances where simple structures were 
>>> exported. This allows important features of the model (e.g., a NURBS 
>>> surface) to exist and triangulation to happen later in the process.
>>>
>>> The details are at 
>>> http://realism.com/blog/proposed-x3d-profile-static-model. The post 
>>> includes a list of included nodes sorted by their profile.
>>>
>>> -- 
>>> *Leonard Daly*
>>> 3D Systems & Cloud Consultant
>>> LA ACM SIGGRAPH Past 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
>> For reference, UCSF Chimera, a free molecular modeling program that 
>> exports X3D, uses the Interchange profile for static scenes with the 
>> following extra component levels listed in the header, depending on 
>> what is exported: Geometry2D: 2, Navigation: 3, Rendering: 5, Shape: 
>> 3, and Text: 1.  So please include Box, Sphere, OrthoViewpoint, 
>> ColorRGBA, ClipPlane, and Text in static scenes. And we would like to 
>> add, available in X3D 3.3: <unit category='length' name='ångström' 
>> conversionFactor='1e-10'/>.  So please include units in the profile 
>> description too.
>>
>>    HTH,
>>
>>    Greg
>>
>
> -- 
> *Leonard Daly*
> 3D Systems & Cloud Consultant
> LA ACM SIGGRAPH Past 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


-- 
*Leonard Daly*
3D Systems & Cloud Consultant
LA ACM SIGGRAPH Past Chair
President, Daly Realism - /Creating the Future/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20180124/349c6a16/attachment-0001.html>