<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;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";
color:black;}
tt
{mso-style-priority:99;
font-family:"Courier New";}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:"Courier New";
color:black;}
.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>X_ITE has a wrapping tag around the X3D.</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:Leonard.Daly@realism.com">Leonard Daly</a><br><b>Sent: </b>Friday, February 1, 2019 1:43 PM<br><b>To: </b><a href="mailto:x3d-public@web3d.org">x3d-public@web3d.org</a><br><b>Subject: </b>Re: [x3d-public] Requirement for v4. one X3D element per Frame</p></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span style='color:black'>John,<o:p></o:p></span></p><div><p class=MsoNormal><span style='color:black'><o:p> </o:p></span></p></div><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><p class=MsoNormal><span style='color:black'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:black'>Are there other ways of seeing this? The use case is showing a scenegraph 4 times, twice as X3DOM, twice as X_ITE, twice as JS/DOM and twice as XML, trying to script various elements in scene.<o:p></o:p></span></p></blockquote><p><o:p> </o:p></p><p>There would be a problem having more than one possible interpreter for X3D. Each interpreter would try to interpret the same code without knowing that the other one was running. This is independent of any duplication of tag 'id' attributes. You could have each interpreter only look for code inside a unique (to them) tag. For example</p><p><tt><span style='font-size:10.0pt'><x3dom></span></tt><span style='font-size:10.0pt;font-family:"Courier New"'><br><tt> <x3d></tt><br><tt> :</tt><br><tt> :</tt><br><tt> </x3d></tt><br><tt></x3dom></tt></span></p><p><tt><span style='font-size:10.0pt'>and</span></tt></p><p><tt><span style='font-size:10.0pt'><x-ite></span></tt><span style='font-size:10.0pt;font-family:"Courier New"'><br><tt> <x3d></tt><br><tt> :</tt><br><tt> :</tt><br><tt> </x3d></tt><br><tt></x-ite></tt></span></p><p><o:p> </o:p></p><p>Though this seems awkward and kludgy.</p><p>Each X#D viewer application may choose (or not) to support multiple instances per page. That would be more a matter of handling their own internal data stores.</p><p>Note that for augmented reality applications using the ImmersiveWeb specification, the browser will enforce that the application runs full-screen. If these are loaded as iFrames, then the necessary permissions will need to be granted to the iFrame in order for that application to display.</p><p><o:p> </o:p></p><p>Leonard Daly</p><p><o:p> </o:p></p><p><o:p> </o:p></p><p><o:p> </o:p></p><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><p class=MsoNormal><span style='color:black'> <o:p></o:p></span></p><p class=MsoNormal><span style='color:black'>Can someone see a fault in this? Should I start porting my code over to this to see any difficulties? I know IFrames are difficult, but I think we should show our multicanvas apps with multiframes.<o:p></o:p></span></p><p class=MsoNormal><span style='color:black'> <o:p></o:p></span></p><p class=MsoNormal><span style='color:black'>Almost bedtime.<o:p></o:p></span></p><p class=MsoNormal><span style='color:black'> <o:p></o:p></span></p><p class=MsoNormal><span style='color:black'>John<o:p></o:p></span></p><p class=MsoNormal><span style='color:black'> <o:p></o:p></span></p><p class=MsoNormal><span style='color:black'><br><br><o:p></o:p></span></p><pre>_______________________________________________</pre><pre>x3d-public mailing list</pre><pre><a href="mailto:x3d-public@web3d.org">x3d-public@web3d.org</a></pre><pre><a href="http://web3d.org/mailman/listinfo/x3d-public_web3d.org">http://web3d.org/mailman/listinfo/x3d-public_web3d.org</a></pre></blockquote><p><o:p> </o:p></p><p class=MsoNormal><span style='color:black'>-- <br></span><b><span style='font-size:13.5pt;color:#333366'>Leonard Daly</span></b><span style='color:#333366'><br>3D Systems & Cloud Consultant<br>LA ACM SIGGRAPH Past Chair<br>President, Daly Realism - <i>Creating the Future</i> </span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal><span style='color:black'><o:p> </o:p></span></p></div></body></html>