<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Текст Знак";
margin:0cm;
margin-bottom:.0001pt;
font-size:9.0pt;
font-family:"Courier New";
mso-fareast-language:EN-US;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Текст выноски Знак";
margin:0cm;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.EmailStyle17
{mso-style-type:personal;
font-family:"Times New Roman","serif";
color:windowtext;
font-weight:normal;
font-style:normal;
text-decoration:none none;}
span.a
{mso-style-name:"Текст выноски Знак";
mso-style-priority:99;
mso-style-link:"Текст выноски";
font-family:"Tahoma","sans-serif";
mso-fareast-language:RU;}
span.a0
{mso-style-name:"Текст Знак";
mso-style-priority:99;
mso-style-link:Текст;
font-family:"Courier New";}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:2.0cm 42.5pt 2.0cm 3.0cm;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=RU link=blue vlink=purple><div class=WordSection1><p class=MsoPlainText><span lang=EN-US>Hi Alan,<o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-US><o:p> </o:p></span></p><p class=MsoPlainText><span lang=EN-US>> I have a theory on format adoption. What i've seen over the years is that simple formats rule. One might even say dead formats rule as they don't change. I suspect there is a threshold of effort that turns supporting a format from a simple project to one that must be approved. My going theory is that any format you can implement in < 1 week just get's done. Above that it must be approved and that starts a larger discussion.<o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-US><o:p> </o:p></span></p><p class=MsoPlainText><span lang=EN-US>Yes, that is definitely a good point.<o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-US><o:p> </o:p></span></p><p class=MsoPlainText><span lang=EN-US>> If you choose to spec X3D for your project I'd recommend being very focused in your usage. Spec a simple set of components, require one encoding, then write a document that brings all the information into one place to help adopters.<o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-US><o:p> </o:p></span></p><p class=MsoPlainText><span lang=EN-US>OK, well noted, thank you, written down to the doc.<o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-US><o:p> </o:p></span></p><p class=MsoPlainText><span lang=EN-US>Best regards,<o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-US>Maxim Fedyukov, PhD<o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-US>CEO, Texel Inc.<o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-US>+7.910.403.27.01<o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-US>max@texel.graphics<o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-US><o:p> </o:p></span></p><p class=MsoPlainText><span lang=EN-US><o:p> </o:p></span></p><p class=MsoPlainText><span lang=EN-US>From: Alan Hudson [mailto:alan@shapeways.com] <o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-US>Sent: Wednesday, December 28, 2016 5:57 PM<o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-US>To: Maxim Fedyukov<o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-US>Cc: Vincent Marchetti; X3D Graphics public mailing list; doug sanden<o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-US>Subject: Re: [x3d-public] Current X3D adoption<o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-US><o:p> </o:p></span></p><p class=MsoPlainText><span lang=EN-US>I have a theory on format adoption. What i've seen over the years is that simple formats rule. One might even say dead formats rule as they don't change. I suspect there is a threshold of effort that turns supporting a format from a simple project to one that must be approved. My going theory is that any format you can implement in < 1 week just get's done. Above that it must be approved and that starts a larger discussion. <o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-US><o:p> </o:p></span></p><p class=MsoPlainText><span lang=EN-US>I was never very successful in convincing everyone to keep X3D simple and am certainly to blame for some of its bloat. If you choose to spec X3D for your project I'd recommend being very focused in your usage. Spec a simple set of components, require one encoding, then write a document that brings all the information into one place to help adopters. <o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-US><o:p> </o:p></span></p><p class=MsoPlainText><span lang=EN-US><o:p> </o:p></span></p><p class=MsoPlainText><span lang=EN-US>On Tue, Dec 27, 2016 at 10:51 PM, Maxim Fedyukov <max@texel.graphics> wrote:<o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-US>Vincent, Doug, thank you for your opinions and comments.<o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-US><o:p> </o:p></span></p><p class=MsoPlainText><span lang=EN-US>> Maxim,<o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-US>> https://standards.ieee.org/develop/indconn/3d/bodyprocessing.html<o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-US>very interesting.<o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-US>> Q. do you have a list of technical requirements for body processing?<o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-US>> -Doug<o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-US><o:p> </o:p></span></p><p class=MsoPlainText><span lang=EN-US>The current stage is exactly the formation of a list of technical requirements for 3D body processing. So I'm gathering the proposition with every option, current pros and contras and the future projections, as the first standard publishing is planned for Q4 2017.<o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-US><o:p> </o:p></span></p><p class=MsoPlainText><span lang=EN-US>What puzzles me even more is the widespread adoption of VRML, even in quite new software, which appeared much later than 2005, but still they have chosen to aim their efforts at adding the support for VRML and/or VRML2, but not X3D. Do you have an understanding or opinion why this happens?<o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-US><o:p> </o:p></span></p><p class=MsoPlainText><span lang=EN-US>Best regards,<o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-US>Maxim Fedyukov, PhD<o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-US>CEO, Texel Inc.<o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-US>+7.910.403.27.01<o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-US>max@texel.graphics<o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-US><o:p> </o:p></span></p><p class=MsoPlainText><span lang=EN-US><o:p> </o:p></span></p><p class=MsoPlainText><span lang=EN-US>-------- Original message --------<o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-US>From: Vincent Marchetti <vmarchetti@kshell.com> <o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-US>Date: 12/27/16 16:34 (GMT+03:00) <o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-US>To: Maxim Fedyukov <max@texel.graphics>, X3D Graphics public mailing list <x3d-public@web3d.org> <o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-US>Subject: Re: [x3d-public] Current X3D adoption <o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-US><o:p> </o:p></span></p><p class=MsoPlainText><span lang=EN-US>Maxim<o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-US><o:p> </o:p></span></p><p class=MsoPlainText><span lang=EN-US>The question as to why a software application, particularly a commercial or closed product, chooses to support an exchange or export format is best answered by those who directly manage the development of those applications. I am sure it involves sales and business development objectives as much or more than direct technical merit. In the open source and third-party spheres X3D is widely supported. Direct X3D support by open source packages includes the two you mentioned (Blender, Meshlab), as well as by Open Cascade,VTK, and Cura 3D Printing software. There are also a variety of commercial and open source translation products that provide a route from the native formats of popular commercial products into X3D. There is a comprehensive list of applications at http://www.web3d.org/x3d/content/examples/X3dResources.html#Conversions and the Web3D Consortium website at http://www.web3d.org has additional slide sets and presentations detailing workflows to create X3D content from common commercial and open source software.<o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-US><o:p> </o:p></span></p><p class=MsoPlainText><span lang=EN-US>Vince Marchetti<o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-US>KShell Analysis & Web3D Consortium<o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-US><o:p> </o:p></span></p><p class=MsoPlainText><span lang=EN-US>> On Dec 27, 2016, at 6:39 AM, Maxim Fedyukov <max@texel.graphics> wrote:<o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-US>> <o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-US>> Hello,<o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-US>> <o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-US>> I'm writing you as the file format subteam lead of IEEE 3D Body Processing<o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-US>> working group<o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-US>> (https://standards.ieee.org/develop/indconn/3d/bodyprocessing.html).<o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-US>> Exploring the formats to include into standard recommendations, I see that<o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-US>> X3D seems to be one of the best candidates. But the main concern here is<o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-US>> that X3D has not received a wide acceptance of notable software applications<o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-US>> besides Blender and MeshLab. Why is it so?<o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-US>> <o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-US>> Best regards,<o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-US>> Maxim Fedyukov, PhD<o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-US>> CEO, Texel Inc.<o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-US>> +7.910.403.27.01<o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-US>> max@texel.graphics<o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-US>> <o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-US>> <o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-US>> _______________________________________________<o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-US>> x3d-public mailing list<o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-US>> x3d-public@web3d.org<o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-US>> http://web3d.org/mailman/listinfo/x3d-public_web3d.org<o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-US><o:p> </o:p></span></p><p class=MsoPlainText><span lang=EN-US>_______________________________________________<o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-US>x3d-public mailing list<o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-US>x3d-public@web3d.org<o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-US>http://web3d.org/mailman/listinfo/x3d-public_web3d.org<o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-US><o:p> </o:p></span></p></div></body></html>