<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=iso-8859-2"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><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:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
font-size:10.0pt;
font-family:"Courier New";}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;}
span.EmailStyle22
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.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:1903522777;
mso-list-template-ids:1223336856;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1
{mso-list-id:1985886062;
mso-list-template-ids:2134535372;}
@list l1:level1
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:"Courier New";
mso-bidi-font-family:"Times New Roman";}
@list l1:level3
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1:level4
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1:level5
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1:level6
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1:level7
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1:level8
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1:level9
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
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 style='word-wrap:break-word'><div class=WordSection1><p class=MsoNormal>Leonard, thanks very much for sharing these excellent constructive comments. Very helpful.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>We will continue working on this comparison document in order to hopefully achieve best-possible clarity and correctness.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>One important clarification I can offer now: while X3D4 ISO draft international specification references ISO-draft glTF 2 specification, cross-referencing glTF extension capabilities and permitting them in X3D players is certainly allowed.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Next session is regular weekly call, Friday 8 SEP, 09-1000 pacific. All participation welcome.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal style='margin-left:.5in'><i>Consortium and community members are welcome to participate. As usual, we meet each Friday.<o:p></o:p></i></p><p class=MsoNormal style='margin-left:.5in'>• X3D Working Group, Fridays 0900-1000 pacific<o:p></o:p></p><p class=MsoNormal style='margin-left:.5in'>• https://us02web.zoom.us/j/81634670698?pwd=a1VPeU5tN01rc21Oa3hScUlHK0Rxdz09<o:p></o:p></p><p class=MsoNormal style='margin-left:.5in'><o:p> </o:p></p><p class=MsoNormal style='margin-left:.5in'><i>Web3D Consortium membership has value. Please consider joining to maximize your ability to benefit and influence</i>.<o:p></o:p></p><p class=MsoNormal style='margin-left:.5in'>• Join the Web3D Consortium<o:p></o:p></p><p class=MsoNormal style='margin-left:.5in'>• https://www.web3d.org/join<o:p></o:p></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Courier New"'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Courier New"'>all the best, Don<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Courier New"'>-- <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Courier New"'>Don Brutzman Naval Postgraduate School, Code USW/Br brutzman@nps.edu<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Courier New"'>Watkins 270, MOVES Institute, Monterey CA 93943-5000 USA +1.831.656.2149<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Courier New"'>X3D graphics, virtual worlds, Navy robotics https://</span> <span style='font-size:10.0pt;font-family:"Courier New"'>faculty.nps.edu/brutzman<o:p></o:p></span></p></div><p class=MsoNormal><o:p> </o:p></p><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b>From:</b> x3d-public <x3d-public-bounces@web3d.org> <b>On Behalf Of </b>Leonard Daly<br><b>Sent:</b> Thursday, September 8, 2022 4:21 PM<br><b>To:</b> x3d-public@web3d.org<br><b>Subject:</b> Re: [x3d-public] X3D glTF feature comparison [was: X3D Working Group Minutes, 2 SEP ...]<o:p></o:p></p></div></div><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal>These messages were all on the public list and referenced glTF. <o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>I passed on to 3D Formats WG of Khronos (manages glTF Specification) for comments and provided a summary and links to the relevant messages from the mailing list and documents. There were links to 3 messages (the initial message, the updated PDF, and Michalis' comments.] and the Google Sheet document. I gave a chance for people to comment, especially on features of glTF.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>The comments from one individual follow.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal><span style='color:blue'>Some feedback from my side:(unfortunately I only checked the comments in [3] after writing this - there's definitely some overlap)</span><o:p></o:p></p><ul type=disc><li class=MsoNormal style='mso-margin-top-alt:auto;margin-bottom:12.0pt;mso-list:l1 level1 lfo3'><span style='color:blue'>It looks like while the X3D side counts their annexes in, glTF extension mechanism is ignored for the glTF side (otherwise a good amount of the "NO"s would either be "YES" or "possible through extensions"). I think an equal comparison would either exclude X3D annexes or include glTF extensions.</span><o:p></o:p></li><li class=MsoNormal style='mso-margin-top-alt:auto;margin-bottom:12.0pt;mso-list:l1 level1 lfo3'><span style='color:blue'>While it's mentioned that X3D is an ISO standard it's omitted that glTF is also an ISO standard.</span><o:p></o:p></li><li class=MsoNormal style='mso-margin-top-alt:auto;margin-bottom:12.0pt;mso-list:l1 level1 lfo3'><span style='color:blue'>I'm not sure what <i>Metadata structures: partial, in separate files</i> means for glTF - there's at least one extension for that.</span><o:p></o:p></li><li class=MsoNormal style='mso-margin-top-alt:auto;margin-bottom:12.0pt;mso-list:l1 level1 lfo3'><i><span style='color:blue'>glTF: Transmission format designed for applications rendering using WebGL or OpenGLES.</span></i><span style='color:blue'> is incorrect in my opinion, I think glTF is explicitly not tied to a specific rendering backend, quite the contrary.</span><o:p></o:p></li><li class=MsoNormal style='mso-margin-top-alt:auto;margin-bottom:12.0pt;mso-list:l1 level1 lfo3'><i><span style='color:blue'>glTF: Always changing to support the fast changing GPU, a delivery system for highly optimized mesh data for rendering. </span></i><span style='color:blue'>kind of omits that glTF is also an ISO standard and not "always changing". The extension mechanism allows for flexibility but the core is (rightfully) rigid.</span><o:p></o:p></li><li class=MsoNormal style='mso-margin-top-alt:auto;margin-bottom:12.0pt;mso-list:l1 level1 lfo3'><span style='color:blue'>One thing that bothers me in a lot of Khronos communication around glTF is the focus on "efficient transmission from server to client" and similar. Alternate wordings are "The JPEG of 3D" and so on. Lots of companies have started to adopt glTF as an interchange format as well (including us), not just for last-mile delivery. I don't think it strengthens glTF as a whole to "fight against that" in communication and continually emphasizing that the format is somehow only suitable for last-mile delivery.<br>(compare also lots of the USDZ vs. glTF discussions at this year's Siggraph)<br>I understand this is a bigger discussion but wanted to mention it here nonetheless. Almost all of the "Technology Comparison Summaries" entries revolve around that, hinting at glTF not being a good format for anything else.</span><o:p></o:p></li><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level1 lfo3'><span style='color:blue'>Related to the above and some more of the "NO"s: we're happily using glTF extensions for composition of files, inline use of glbs inside glbs, and so on, there's nothing blocking extensions from doing that. (I understand glXF tries to specify that as separate format but still don't fully understand why)</span><o:p></o:p></li></ul></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Leonard Daly<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><div><div><div><div><div><p class=MsoNormal>Michalis thank you for your note. Please be assured we that we have zero desire to overstate or incorrectly characterize anything. Our previously sent draft did not receive any responses. You saw our best effort update to it. Happy to continue improving. Can we meet during this Friday’s meeting?<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Thanks, Don<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Search for my handheld device<o:p></o:p></p></div></div></div><div id=ms-outlook-mobile-signature><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div></div></div></div><div class=MsoNormal align=center style='text-align:center'><hr size=1 width="98%" align=center></div><div id=divRplyFwdMsg><p class=MsoNormal><b><span style='color:black'>From:</span></b><span style='color:black'> Michalis Kamburelis </span><a href="mailto:michalis.kambi@gmail.com"><michalis.kambi@gmail.com></a><span style='color:black'><br><b>Sent:</b> Tuesday, September 6, 2022 6:47:04 AM<br><b>To:</b> Brutzman, Donald (Don) (CIV) </span><a href="mailto:brutzman@nps.edu"><brutzman@nps.edu></a><span style='color:black'><br><b>Cc:</b> X3D Public Mailing List (</span><a href="mailto:x3d-public@web3d.org">x3d-public@web3d.org</a><span style='color:black'>) </span><a href="mailto:x3d-public@web3d.org"><x3d-public@web3d.org></a><span style='color:black'><br><b>Subject:</b> Re: [x3d-public] X3D Working Group Minutes, 2 SEP 2022: X3D glTF feature comparison</span> <o:p></o:p></p><div><p class=MsoNormal> <o:p></o:p></p></div></div><div><div><p class=MsoNormal>NPS WARNING: *external sender* verify before acting.<br><br><br>Hello,<br><br>I read the <a href="https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.google.com%2Fspreadsheets%2Fd%2F1x0DnRtg33AuOA_aSl70L41Gq5m6TFt4t%2Fedit%23gid%3D1010586376&data=05%7C01%7Cbrutzman%40nps.edu%7Cda60c5a36b2b4caf4a4f08da91f0d9ef%7C6d936231a51740ea9199f7578963378e%7C0%7C0%7C637982762822205320%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000%7C%7C%7C&sdata=9LP0xGTWczl6oqr%2Bub7r4wI8Tiv8gNp9vMW7Lsb0138%3D&reserved=0">https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.google.com%2Fspreadsheets%2Fd%2F1x0DnRtg33AuOA_aSl70L41Gq5m6TFt4t%2Fedit%23gid%3D1010586376&data=05%7C01%7Cbrutzman%40nps.edu%7Cb04d8dc972cb4f8430be08da900e5efe%7C6d936231a51740ea9199f7578963378e%7C0%7C0%7C637980688655942200%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=IqmTBR8XcyQT4f3uVk0Gp8rJJb7PvLoB7PcnVg5kiqw%3D&reserved=0</a><br>and have a number of comments. (sorry -- this is another of Michalis'<br>long emails :) ).<br><br>My main objections are to the initial sections "Value Proposition" and<br>"Technology Comparison Summaries". To be frank, a lot of the content<br>there seems to be written with the mindset "X3D is better than glTF,<br>so let's list all the ways how it is better". Some statements are<br>unclear (and the lack of clarity seems to suggest that X3D is better),<br>some are just untrue IMHO. To be clear, in my opinion, indeed X3D<br>*has* some strengths over glTF, and same goes for the other way<br>around, glTF did some stuff better than X3D.<br><br>A fair comparison of X3D vs glTF would be helpful (I have written it<br>myself too, but never published :) ). But the table above is not very<br>fair, it tries to push the agenda "X3D is better" a bit too much. Let<br>me point out what I think should be improved:<br><br>1. "Value Proposition" - in general, the goals listed for X3D are<br>broad (wide variety of applications...), while the goals and use-cases<br>listed for glTF are narrow (efficient transmission, appropriate if you<br>want to view in web browser).<br><br>This does not reflect reality in my experience. Neither does it<br>reflect glTF mission statements at the beginning of<br><a href="https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fregistry.khronos.org%2FglTF%2Fspecs%2F2.0%2FglTF-2.0.html&data=05%7C01%7Cbrutzman%40nps.edu%7Cda60c5a36b2b4caf4a4f08da91f0d9ef%7C6d936231a51740ea9199f7578963378e%7C0%7C0%7C637982762822205320%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000%7C%7C%7C&sdata=5nzetpe6jHtHkNTNzNcdi%2BGwVESQ7mbq3gvaaly%2Fbrg%3D&reserved=0">https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fregistry.khronos.org%2FglTF%2Fspecs%2F2.0%2FglTF-2.0.html&data=05%7C01%7Cbrutzman%40nps.edu%7Cb04d8dc972cb4f8430be08da900e5efe%7C6d936231a51740ea9199f7578963378e%7C0%7C0%7C637980688655942200%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=BRIUyLBNBkdzH7%2BEE9UDB73gL4NmcVEiErOn%2FU01WLg%3D&reserved=0</a> , "glTF is<br>an API-neutral runtime asset delivery format. glTF bridges the gap<br>between 3D content creation tools and modern graphics applications by<br>providing an efficient, extensible, interoperable format for the<br>transmission and loading of 3D content.".<br><br>The practical fact, IMHO, is that glTF is here exactly like X3D. It's<br>just a format for 3D models, it can be used with a variety of<br>applications, on any platforms (certainly not only to view the models<br>in web browser; e.g. game engines, including Castle Game Engine, allow<br>to use glTF as 3D model format on desktops).<br><br>So I would suggest to place there the glTF statement I cited above<br>("glTF is an API-neutral runtime asset delivery format. glTF<br>bridges..."), and in general make this section simply honestly state:<br>the goals and usecases of X3D and glTF largely overlap. They are both<br>open standards for 3D models and can be used in a variety of<br>applications, use-cases, platforms.<br><br>2. "Technology Comparison Summaries" - in general, statements there<br>again suffer from "a bit unclear, in favor of X3D and disfavor of<br>glTF".<br><br>- X3D advantage: "X3D: Full Inline support for glTF features,<br>especially compressed geometry plus advanced lighting model planned<br>for X3D version 4." - in X3D we have it, but it is not complete as<br>this statement suggests. In particular we don't yet have in X3D spec<br>any way to specify binary per-vertex data or "compressed geometry".<br>This is a work in progress, with some browser-specific extensions, not<br>more yet ( <a href="https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmichaliskambi%2Fx3d-tests%2Fwiki%2FBinary-meshes&data=05%7C01%7Cbrutzman%40nps.edu%7Cda60c5a36b2b4caf4a4f08da91f0d9ef%7C6d936231a51740ea9199f7578963378e%7C0%7C0%7C637982762822205320%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000%7C%7C%7C&sdata=x6eJDmZhqdkIkRSyCNAhEGZxCtdUF7lQ1j%2BzQ%2BP7Q%2FM%3D&reserved=0">https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmichaliskambi%2Fx3d-tests%2Fwiki%2FBinary-meshes&data=05%7C01%7Cbrutzman%40nps.edu%7Cb04d8dc972cb4f8430be08da900e5efe%7C6d936231a51740ea9199f7578963378e%7C0%7C0%7C637980688655942200%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=0fQBGBo5fLqiC%2Fr73X%2B9ucLw7ihfq4oDT1L9pTowmHw%3D&reserved=0</a><br>). We have not yet figured out how 100% of glTF features express as<br>X3D (as I say explicitly on<br><a href="https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmichaliskambi%2Fx3d-tests%2Fwiki%2FConverting-glTF-to-X3D&data=05%7C01%7Cbrutzman%40nps.edu%7Cda60c5a36b2b4caf4a4f08da91f0d9ef%7C6d936231a51740ea9199f7578963378e%7C0%7C0%7C637982762822205320%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000%7C%7C%7C&sdata=kqK17tIiBw%2BeMAvTs0IIeT5IFWB86mnoAnDU2a2SfKg%3D&reserved=0">https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmichaliskambi%2Fx3d-tests%2Fwiki%2FConverting-glTF-to-X3D&data=05%7C01%7Cbrutzman%40nps.edu%7Cb04d8dc972cb4f8430be08da900e5efe%7C6d936231a51740ea9199f7578963378e%7C0%7C0%7C637980688655942200%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=Reum%2Bn0%2F8i5AnwiANMh%2BAJwct5u6OIyX7ErmGrif414%3D&reserved=0</a><br>).<br><br> I would suggest to change it to "X3D: Inline support for many glTF<br>features, especially advanced physically-based materials."<br><br>- "glTF: Transmission format designed for applications rendering using<br>WebGL or OpenGLES." This tries to suggest that glTF usefullness is<br>narrow. It is in conflict with actual glTF statement I cited above,<br>"glTF is an API-neutral runtime asset delivery format.". glTF makes<br>sense regardless if you use WebGL or OpenGLES. Yes, it used some<br>constants / naming from WebGL / OpenGLES, but it's fully implementable<br>and understandable in the context of any graphics API - including e.g.<br>Vulkan and Direct3D.<br><br> I would suggest to change it to "glTF is an API-neutral runtime<br>asset delivery format."<br><br>- "glTF: Always changing to support the fast changing GPU, a delivery<br>system for highly optimized mesh data for rendering." - not true, or<br>at least unclear statement. glTF is not "always changing". They care<br>about backward compatibility a *lot* and glTF 2.0 has been stable for<br>many years, without any breaking changes.<br><br> I would suggest to just remove this statement.<br><br>- "glTF: Backward compatibility, archivability, are not listed as<br>specification goals." - not true. In practice, of course they care<br>about backward compatibility. And it is mentioned in spec explicitly:<br><a href="https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fregistry.khronos.org%2FglTF%2Fspecs%2F2.0%2FglTF-2.0.html%23versioning&data=05%7C01%7Cbrutzman%40nps.edu%7Cda60c5a36b2b4caf4a4f08da91f0d9ef%7C6d936231a51740ea9199f7578963378e%7C0%7C0%7C637982762822205320%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000%7C%7C%7C&sdata=Qik7Pd5V%2B0TX5oN5IWvqjq3TAurJH0EKA%2FBaMdeiYXU%3D&reserved=0">https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fregistry.khronos.org%2FglTF%2Fspecs%2F2.0%2FglTF-2.0.html%23versioning&data=05%7C01%7Cbrutzman%40nps.edu%7Cb04d8dc972cb4f8430be08da900e5efe%7C6d936231a51740ea9199f7578963378e%7C0%7C0%7C637980688655942200%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=%2BxtVPG9WjSSqdnQFEZ%2FjLo%2F03m7IawhJ%2FDDrodLxMkc%3D&reserved=0</a> ,<br>"Any updates made to the glTF Specification in a minor version MUST be<br>backward and forward compatible....."<br><br> I would suggest to change this statement: "glTF: Backward<br>compatibility is addressed by the spec, any updates made to the glTF<br>Specification in a minor version MUST be backward and forward<br>compatible."<br><br>3. "Picking (touch/over TouchSensor, PickableGroup)" - glTF should<br>have "No". (So this part is wrong in favor of glTF). There's work to<br>introduce such features on top of glTF, but glTF spec does not have<br>it.<br><br>4. "Clipping planes" - glTF should have "No".<br><br>5. "Metadata Structures" - glTF does have it, in much the same way as X3D.<br><br>- Essentially anything can have additional informatiom, with key-value<br>or deeper structure:<br><a href="https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fregistry.khronos.org%2FglTF%2Fspecs%2F2.0%2FglTF-2.0.html%23reference-extras&data=05%7C01%7Cbrutzman%40nps.edu%7Cda60c5a36b2b4caf4a4f08da91f0d9ef%7C6d936231a51740ea9199f7578963378e%7C0%7C0%7C637982762822205320%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000%7C%7C%7C&sdata=69zqvGfu0Qz4P234%2F0ypY92j123fNqPBaQEom0BSiHQ%3D&reserved=0">https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fregistry.khronos.org%2FglTF%2Fspecs%2F2.0%2FglTF-2.0.html%23reference-extras&data=05%7C01%7Cbrutzman%40nps.edu%7Cb04d8dc972cb4f8430be08da900e5efe%7C6d936231a51740ea9199f7578963378e%7C0%7C0%7C637980688655942200%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=4RrMuXIvbjbaDpH80Dm2bKkgzlg7%2BoXunm9iSe3gNgY%3D&reserved=0</a><br>. This is quite similar in practice to how X3D MetadataXxx nodes are<br>used.<br><br>- There's also "asset" for per-file properties:<br><a href="https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fregistry.khronos.org%2FglTF%2Fspecs%2F2.0%2FglTF-2.0.html%23asset&data=05%7C01%7Cbrutzman%40nps.edu%7Cda60c5a36b2b4caf4a4f08da91f0d9ef%7C6d936231a51740ea9199f7578963378e%7C0%7C0%7C637982762822205320%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000%7C%7C%7C&sdata=lM7mbVqgl3V%2BZQd9X19wCjvsxPlmILuLMXdHMOG7ClE%3D&reserved=0">https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fregistry.khronos.org%2FglTF%2Fspecs%2F2.0%2FglTF-2.0.html%23asset&data=05%7C01%7Cbrutzman%40nps.edu%7Cb04d8dc972cb4f8430be08da900e5efe%7C6d936231a51740ea9199f7578963378e%7C0%7C0%7C637980688655942200%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=dmY4m20QxOcWIh4gMU3TVlpWX0AjRRfwTqqK6SiW3D8%3D&reserved=0</a> . This<br>is quite similar to common usage of X3D "META" statements.<br><br>- And the "extras" are mentioned above are really used in practice.<br>Blender exports Blender's "Custom properties" to glTF "extras". (Which<br>is actually better than Blender->X3D exporter, that doesn't write X3D<br>MetadataXxx, although it could.)<br><br>6. "Inline" - this is correct, glTF doesn't have it. But you can<br>mention <a href="https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FKhronosGroup%2FglXF&data=05%7C01%7Cbrutzman%40nps.edu%7Cda60c5a36b2b4caf4a4f08da91f0d9ef%7C6d936231a51740ea9199f7578963378e%7C0%7C0%7C637982762822205320%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000%7C%7C%7C&sdata=O3mCaUYy%2FcZLcjgZ9gR2nJXaRDoFBtp55oyz%2BOjk5u8%3D&reserved=0">https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FKhronosGroup%2FglXF&data=05%7C01%7Cbrutzman%40nps.edu%7Cb04d8dc972cb4f8430be08da900e5efe%7C6d936231a51740ea9199f7578963378e%7C0%7C0%7C637980688655942200%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=M1zkHjoZUoGzC0HGZNkba2HAcOXmAMfszDR8Rdr9Fv8%3D&reserved=0</a> -- it's not yet<br>officially endorsed, but it's an idea to address exactly this, i.e.<br>compose world from multiple glTF files.<br><br>7. Let me add some things I consider missing to have a good picture:<br><br>"Efficient representation of mesh in binary format"<br>X3D: not (yet!)<br>glTF: yes<br><br>"Cubemap textures, including generated cubemaps"<br>X3D: yes<br>glTF: no<br><br>"Lights"<br>X3D: yes<br>glTF: not in core spec (but in extensions)<br><br>"Environmental effects, like fog and background"<br>X3D: yes<br>glTF: no<br><br>"Full-featured and actively maintained Blender exporter, with support<br>for PBR materials, animations, skinned animations"<br>X3D: not (yet!)<br>glTF: yes<br><br>Regards,<br>Michalis<br><br>sob., 3 wrz 2022 o 01:10 Brutzman, Donald (Don) (CIV)<br><a href="mailto:brutzman@nps.edu"><brutzman@nps.edu></a> napisa³(a):<br>><br>> Spreadsheet PDF with corrected date (for today) attached.<br>><br>><br>><br>> all the best, Don<br>><br>> --<br>><br>> Don Brutzman Naval Postgraduate School, Code USW/Br <a href="mailto:brutzman@nps.edu">brutzman@nps.edu</a><br>><br>> Watkins 270, MOVES Institute, Monterey CA 93943-5000 USA +1.831.656.2149<br>><br>> X3D graphics, virtual worlds, Navy robotics https:// faculty.nps.edu/brutzman<br>><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></div><p class=MsoNormal><br><br><o:p></o:p></p><pre>_______________________________________________<o:p></o:p></pre><pre>x3d-public mailing list<o:p></o:p></pre><pre><a href="mailto:x3d-public@web3d.org">x3d-public@web3d.org</a><o:p></o:p></pre><pre><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></pre></blockquote><p><o:p> </o:p></p><div><p class=MsoNormal>-- <br><b><span style='font-size:13.5pt;color:#333366'>Leonard Daly</span></b><span style='color:#333366'><br>3D Systems & Cloud Consultant<br>President, Daly Realism - <i>Creating the Future</i> </span><o:p></o:p></p></div></div></body></html>