<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>Should the Inline be checked statically or dynamically for recursion? What if there’s a switch statement in the Inline which inlines the Inline some of the time?</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Should we allow fractals/graftals? <a href="https://www.youtube.com/watch?v=fXu74k-77kg">https://www.youtube.com/watch?v=fXu74k-77kg</a> How does one propose doing it without Inlines?<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Thanks,</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:brutzman@nps.edu">Brutzman, Donald (Don) (CIV)</a><br><b>Sent: </b>Wednesday, July 10, 2019 4:42 AM<br><b>To: </b><a href="mailto:johannes.behr@igd.fraunhofer.de">Behr, Johannes</a><br><b>Cc: </b><a href="mailto:Timo.Sturm@igd.fraunhofer.de">Sturm, Timo</a>; <a href="mailto:x3d-public@web3d.org">X3D Graphics public mailing list</a>; <a href="mailto:vmarchetti@ameritech.net">Vincent Marchetti</a><br><b>Subject: </b>[x3d-public] Inline, X3DUrlObject allowed to add additional filetypes, etc.</p></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>[cc: X3D mailing list]</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Thanks Johannes for an excellent specification recommendation. This has been added as Mantis issue 1257. Dick and I have agreed to include it and will review/refine prose together. Changes checked into github. Related changes and issues follow.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Am hoping we have integrated all known changes for X3DUrlObject and Inline.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Comments welcome for weekly working group review this coming Friday. Status maintained at</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal> X3Dv4 Implementations Status</p><p class=MsoNormal> http://www.web3d.org/x3dv4-implementations</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>----</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>* Inline allowed to load additional model types</p><p class=MsoNormal> http://www.web3d.org/member-only/mantis/view.php?id=1257</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>"The run-time system can support any number of 3D model resource types as long as those follow the abstract model definition [RFC2077], provide a registered content type (e.g. model/x3d-xml, model/gltf-bin, model/stl, etc.), and can be determined with some form of content negotiation [RFC7231]. The run-time system must support at least one X3D type (e.g. model/x3d-xml) but can also support and negotiate any number of X3D encodings and (optionally) non-X3D representation formats."</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>----</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>* 9.3.2 X3DUrlObject - Incorrectly restricts to valid X3D files</p><p class=MsoNormal> http://www.web3d.org/member-only/mantis/view.php?id=1171</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>"The results are undefined if the URL refers to a file that is not an X3D file, or if the X3D file contains an invalid scene."</p><p class=MsoNormal>to</p><p class=MsoNormal>"The results are undefined if the URL refers to a file that is not a supported file type, or if the file contains invalid content."</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>----</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>* 9.4.2 Inline - Security precaution</p><p class=MsoNormal> http://www.web3d.org/member-only/mantis/view.php?id=744</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>"Security precaution: it is an error for a model to Inline itself, directly or indirectly, in order to avoid nonterminating recursion. X3D players SHALL NOT honor self-referential Inline loops in order to avoid security vulnerabilities."</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>----</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>* Inline - Inline is silent about head, component, unit, and meta statements</p><p class=MsoNormal> http://www.web3d.org/member-only/mantis/view.php?id=1151</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>"NOTE When Inline is used to load a child scene, processing of the Inline content is as specified in the respective PROFILE, COMPONENT, UNIT, IMPORT, and EXPORT statements."</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>----</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>On 7/9/2019 1:44 PM, Behr, Johannes wrote:</p><p class=MsoNormal>> Attached is a updated “Inline Section” to be more consistent with the new open definition of model links.</p><p class=MsoNormal>> </p><p class=MsoNormal>> I would keep all change in the inline section. The X3DUrlObject definition is too ambiguous since it includes also non-Model-links like Audio and Video.</p><p class=MsoNormal>> </p><p class=MsoNormal>> Best regards</p><p class=MsoNormal>> Johannes</p><p class=MsoNormal>> [...]</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>all the best, Don</p><p class=MsoNormal>-- </p><p class=MsoNormal>Don Brutzman Naval Postgraduate School, Code USW/Br brutzman@nps.edu</p><p class=MsoNormal>Watkins 270, MOVES Institute, Monterey CA 93943-5000 USA +1.831.656.2149</p><p class=MsoNormal>X3D graphics, virtual worlds, navy robotics http://faculty.nps.edu/brutzman</p><p class=MsoNormal>_______________________________________________</p><p class=MsoNormal>x3d-public mailing list</p><p class=MsoNormal>x3d-public@web3d.org</p><p class=MsoNormal>http://web3d.org/mailman/listinfo/x3d-public_web3d.org</p><p class=MsoNormal><o:p> </o:p></p></div></body></html>