<html 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 15 (filtered medium)"><style><!--
/* Font Definitions */
@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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style></head><body lang=EN-US link=blue vlink="#954F72"><div class=WordSection1><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Now that I think about it, it makes sense to use glTF as model for composability. Hmm.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>John</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Sent from <a href="https://go.microsoft.com/fwlink/?LinkId=550986">Mail</a> for Windows 10</p><p class=MsoNormal><o:p> </o:p></p><div style='mso-element:para-border-div;border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal style='border:none;padding:0in'><b>From: </b><a href="mailto:yottzumm@gmail.com">John Carlson</a><br><b>Sent: </b>Thursday, July 6, 2017 12:33 AM<br><b>To: </b><a href="mailto:x3d-public@web3d.org">X3D Graphics public mailing list</a><br><b>Subject: </b>Fwd: thinking about X3DJSONLD/X3DOM/glTF interoperability</p></div><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal>XSeen is taking the approach of treating glTF as a model. What are others doing? Is anyone considering the whole scenegraph? Why or why not? Is glTF as a model done because Three.js treats glTF as a mesh (I don't know if three.js does this or not)?</p><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>What do people think of the low level nature of glTF as opposed to X3D? While it makes it less understandable, I can see how keeping glTF low level would improve performance at the expense of file size. Has anyone compared and contrasted the two standards?</p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Are there glTF importer/exporters for blender yet? If not, why not?</p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>John</p><div><p class=MsoNormal><o:p> </o:p></p></div></div></div><p class=MsoNormal style='margin-left:4.8pt'>I’m thinking about glTF and X3DJSONLD interoperability since X3DOM is starting to support glTF (I think). What do you think the synergies might be?</p><p class=MsoNormal><o:p> </o:p></p></div></body></html>