<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:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@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:0in;
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.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:1149514073;
mso-list-type:hybrid;
mso-list-template-ids:1483900882 67698705 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
{mso-level-text:"%1\)";
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></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=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Hello Maxim,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>I mentioned some more comments. Here are my humble musings. Hopefully there are not to many omissions. Corrections are welcome.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Looking at the provided link it seems that the standards committee is interested in various technologies. The 3D Body Scanning Technologies conference link gives a synopsis. The standardization goals seem to focus on fashion, health and wellness. Industry is invited. I assume that a standard would be proposed that would allow for the integration of various scanning, kinematics, modelling and simulation technologies. <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>I suggest that you look up the Medicine Meets Virtual Reality conference.[ MMVR]. This has lots of topics of interest, especially from the medical simulation field. Also you can look at just about and simulation conference. The Summersim conference [www.scs.org] generally has a medical simulation track with telemedicine and simulation use cases.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>The best course is to accept Joe Williams invitation. Also look into the Medical and Mixed Augmented Reality groups.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>So, the core 3-D XML for “Virtual People” is being addressed. The Web3D consortium has lots of industry participation.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>So, you need a 3-D file format. Then you need a viewer. Then you need 3-D Modeling and animation systems that export to the chosen format.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>The Viewer: The current crop of VR/MR/AR activity is geared towards commercial competition. Occulus, Google, Sony, Microsoft. That means competing and most likely non interoperable proprietary file formats, API’s and Headset hardware drivers. It is irrelevant whether this is good or bad. That means that the potential viewers are most likely to be inherently non-interoperable. If one industry entity or consortium in the headset market dominates then the viewer standards will have to support the dominant hardware/software which will most likely force a proprietary file format to be the standard file format.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>If the viewer is web based and not headset then WebGL is possible. The Web3D consortium may have a WebGL AR solution.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>3-D Modeling and Animation: I think that in general the normal dominant formats are STL, OBJ, 3DS, DXF/DWG, VRML97 ( since we are in the X3D mailing list …</span><span style='font-size:11.0pt;font-family:Wingdings;color:#1F497D'>J</span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'> )with FBX, IGES,STEP, LWO and Collada (game format) thrown in. But most modeling and animation systems already support import or export or both with respect to these formats. Plus others of course since applications have their target domains. So, really, the only issue is how well the systems import or export these file formats so that your VR/AR/MR “world” does not crash the viewer.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>3-D File formats: VRML97/X3D is an ISO standard. IGES is an ANSI/ASME/Mil-STD. STL is proprietary but really is widely adopted. STEP is an ISO standard. All the others are widely adopted proprietary file formats.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>So,<o:p></o:p></span></p><p class=MsoListParagraph style='text-indent:-.25in;mso-list:l0 level1 lfo1'><![if !supportLists]><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><span style='mso-list:Ignore'>1)<span style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>VRML97/X3D plus working group extensions related to bodies is a royalty free ISO standard. I am assuming that is why it is being looked at for a core component of any IEEE body standard.<o:p></o:p></span></p><p class=MsoListParagraph style='text-indent:-.25in;mso-list:l0 level1 lfo1'><![if !supportLists]><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><span style='mso-list:Ignore'>2)<span style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>IEEE is trying to generate VR and AR standards which is why the original poster started this thread.<o:p></o:p></span></p><p class=MsoListParagraph style='text-indent:-.25in;mso-list:l0 level1 lfo1'><![if !supportLists]><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><span style='mso-list:Ignore'>3)<span style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>3-D scanners tend to output STL or VRML97 or OBJ. Others of course but I suspect that these are at least 3 important ones, especially if medical objects are printed. My body was scanned at SIGGRAPH last august and I got STL and OBJ files.<o:p></o:p></span></p><p class=MsoListParagraph style='text-indent:-.25in;mso-list:l0 level1 lfo1'><![if !supportLists]><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><span style='mso-list:Ignore'>4)<span style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>All Modeling and Animation systems pay attention to a core suite of formats but they REALLY WANT YOU TO USE THEIR DEFAULT FILE FORMAT. If you are a conspiracy theorist that translates into “are you having trouble converting or importing or exporting or viewing – why not use out file format and our viewer”.<o:p></o:p></span></p><p class=MsoListParagraph style='text-indent:-.25in;mso-list:l0 level1 lfo1'><![if !supportLists]><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><span style='mso-list:Ignore'>5)<span style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>If the IEES body standard has VRML97/X3D plus STL and OBJ compatibility at a minimum with suggested compatibility with the others listed above [3DS, DXF/DWG, IGES, STEP and Collada] then starting the standardization process may have minimal risks.<o:p></o:p></span></p><p class=MsoListParagraph style='text-indent:-.25in;mso-list:l0 level1 lfo1'><![if !supportLists]><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><span style='mso-list:Ignore'>6)<span style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Also, once you have the creation and viewing standards you need to incorporate some sort of dominant simulation standard for distributed simulation. You can try SISO [www.sisostds.org] or EUROSIS.<o:p></o:p></span></p><p class=MsoListParagraph style='text-indent:-.25in;mso-list:l0 level1 lfo1'><![if !supportLists]><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><span style='mso-list:Ignore'>7)<span style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>DIS-Java-VRML (which already exists) anyone…</span><span style='font-size:11.0pt;font-family:Wingdings;color:#1F497D'>J</span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p></o:p></span></p><p class=MsoListParagraph style='text-indent:-.25in;mso-list:l0 level1 lfo1'><![if !supportLists]><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><span style='mso-list:Ignore'>8)<span style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>The simulation community just can’t seem to kill off DIS. But HLA is one future just like X3D is one future of VRML97.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Good luck in your standards endeavors.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>John<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> x3d-public [mailto:x3d-public-bounces@web3d.org] <b>On Behalf Of </b>Maxim Fedyukov<br><b>Sent:</b> Wednesday, December 28, 2016 6:52 AM<br><b>To:</b> Vincent Marchetti; X3D Graphics public mailing list; doug sanden<br><b>Subject:</b> Re: [x3d-public] Current X3D adoption<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span style='font-size:18.0pt;font-family:"Arial","sans-serif"'>Vincent, Doug, thank you for your opinions and comments.<o:p></o:p></span></p><div><div><p class=MsoNormal><span style='font-size:18.0pt;font-family:"Arial","sans-serif"'><o:p> </o:p></span></p></div><div><p class=MsoNormal><span style='font-size:18.0pt;font-family:"Arial","sans-serif"'>> Maxim,<o:p></o:p></span></p></div><p class=MsoNormal><span style='font-size:18.0pt;font-family:"Arial","sans-serif"'>> <a href="https://standards.ieee.org/develop/indconn/3d/bodyprocessing.html">https://standards.ieee.org/develop/indconn/3d/bodyprocessing.html</a><o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:18.0pt;font-family:"Arial","sans-serif"'>very interesting.<br>> Q. do you have a list of technical requirements for body processing?<br>> -Doug<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:18.0pt;font-family:"Arial","sans-serif"'><o:p> </o:p></span></p></div><p class=MsoNormal><span style='font-size:18.0pt;font-family:"Arial","sans-serif"'>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><div><p class=MsoNormal><span style='font-size:18.0pt;font-family:"Arial","sans-serif"'><o:p> </o:p></span></p><div><div><div><p class=MsoNormal><span style='font-size:18.0pt;font-family:"Arial","sans-serif"'>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></div></div><p class=MsoNormal><span style='font-size:18.0pt;font-family:"Arial","sans-serif"'><o:p> </o:p></span></p></div><div><p class=MsoNormal><span style='font-size:18.0pt;font-family:"Arial","sans-serif"'>Best regards,<br>Maxim Fedyukov, PhD<br>CEO, Texel Inc.<br><a href="tel:+7.910.403.27.01">+7.910.403.27.01</a><br><a href="mailto:max@texel.graphics">max@texel.graphics</a><o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:18.0pt;font-family:"Arial","sans-serif"'><o:p> </o:p></span></p></div></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><div><p class=MsoNormal><span style='color:black'>-------- Original message --------<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='color:black'>From: Vincent Marchetti <<a href="mailto:vmarchetti@kshell.com">vmarchetti@kshell.com</a>> <o:p></o:p></span></p></div><div><p class=MsoNormal><span style='color:black'>Date: 12/27/16 16:34 (GMT+03:00) <o:p></o:p></span></p></div><div><p class=MsoNormal><span style='color:black'>To: Maxim Fedyukov <<a href="mailto:max@texel.graphics">max@texel.graphics</a>>, X3D Graphics public mailing list <<a href="mailto:x3d-public@web3d.org">x3d-public@web3d.org</a>> <o:p></o:p></span></p></div><div><p class=MsoNormal><span style='color:black'>Subject: Re: [x3d-public] Current X3D adoption <o:p></o:p></span></p></div><div><p class=MsoNormal><span style='color:black'><o:p> </o:p></span></p></div></div><p class=MsoNormal style='margin-bottom:12.0pt'>Maxim<br><br>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 <a href="http://www.web3d.org/x3d/content/examples/X3dResources.html#Conversions">http://www.web3d.org/x3d/content/examples/X3dResources.html#Conversions</a> and the Web3D Consortium website at <a href="http://www.web3d.org">http://www.web3d.org</a> has additional slide sets and presentations detailing workflows to create X3D content from common commercial and open source software.<br><br>Vince Marchetti<br>KShell Analysis & Web3D Consortium<br><br>> On Dec 27, 2016, at 6:39 AM, Maxim Fedyukov <<a href="mailto:max@texel.graphics">max@texel.graphics</a>> wrote:<br>> <br>> Hello,<br>> <br>> I'm writing you as the file format subteam lead of IEEE 3D Body Processing<br>> working group<br>> (<a href="https://standards.ieee.org/develop/indconn/3d/bodyprocessing.html">https://standards.ieee.org/develop/indconn/3d/bodyprocessing.html</a>).<br>> Exploring the formats to include into standard recommendations, I see that<br>> X3D seems to be one of the best candidates. But the main concern here is<br>> that X3D has not received a wide acceptance of notable software applications<br>> besides Blender and MeshLab. Why is it so?<br>> <br>> Best regards,<br>> Maxim Fedyukov, PhD<br>> CEO, Texel Inc.<br>> +7.910.403.27.01<br>> <a href="mailto:max@texel.graphics">max@texel.graphics</a><br>> <br>> <br>> _______________________________________________<br>> x3d-public mailing list<br>> <a href="mailto:x3d-public@web3d.org">x3d-public@web3d.org</a><br>> <a href="http://web3d.org/mailman/listinfo/x3d-public_web3d.org">http://web3d.org/mailman/listinfo/x3d-public_web3d.org</a><o:p></o:p></p></div></body></html>