<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">X3DOM and Cobweb uses JavaScript to
provide the 3D capability. At this stage, everything browser-based
(including email clients) that displays 3D content uses JavaScript
and many use CSS.<br>
<br>
Anything else would need to be built into email clients. Since a
lot of email is read with web browsers, it would need to be built
into browsers too. All of that implies an agreed-upon standard to
transmitting and displaying 3D content. That is a couple of years
away -- at best.<br>
<br>
Leonard Daly<br>
<br>
<br>
<br>
<br>
</div>
<blockquote
cite="mid:CAGC3UEnUb_qoeyroqk5Zsi5Nb4EZX=M6LybmMiQ0dzi4Q3XJ_A@mail.gmail.com"
type="cite">
<div dir="auto">There are disadvantages to links as well.
<div dir="auto"><br>
</div>
<div dir="auto">Perhaps: lack of transparency as to where link
goes on phones.</div>
<div dir="auto"><br>
</div>
<div dir="auto">I am speaking of a limited subset of X3D which
does not include Script or CSS. Is there a profile without
these things we could use?</div>
<div dir="auto"><br>
</div>
<div dir="auto">John</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Dec 19, 2016 11:24 PM, "Webmaster"
<<a moz-do-not-send="true"
href="mailto:webmaster@web3d.org">webmaster@web3d.org</a>>
wrote:<br type="attribution">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
<div class="m_-7047486244273330082moz-cite-prefix">[Roy,
sent from a different account, please see if this makes
it to x3d-public.]<br>
<br>
<br>
On 12/19/2016 5:45 PM, Don Brutzman wrote:<br>
</div>
<blockquote type="cite">On 12/19/2016 12:50 PM, John
Carlson wrote: <br>
<blockquote type="cite">How do we achieve 3d email?
Must the MUA's include x3dom or cobweb as part of
their source code? <br>
</blockquote>
</blockquote>
<br>
Many people still like plain-text email. Most (perhaps
all) email clients disable all active content, especially
JavaScript. Not all CSS works in clients either. There are
two reasons for this.<br>
1) Not all email clients are keeping up with browsers
regarding the current standards level. Of course, this
does not apply for webmail (e.g., GMail)<br>
2) Security. An active client can communicate back to the
server informing the server that the person has read the
email and potentially interacted with it. Most email
clients won't load content that is not in the email for
the same reason. Until we are ready to address those
issues (keeping the recipient safe and somewhat anonymous)
the Consortium should not be trying to make this happen.
There are players far larger than we could ever imagine
that are fighting this battle for just 2D content. <br>
<br>
It would be best to use Don's recommendations of putting
links in an email from screen shots (or equivalent).<br>
<br>
Leonard Daly<br>
<br>
<br>
<br>
<blockquote type="cite"> <br>
URL links can work, permissions vary. <br>
<br>
<a moz-do-not-send="true"
class="m_-7047486244273330082moz-txt-link-freetext"
href="http://x3dgraphics.com/examples/X3dForAdvancedModeling/HelloWorldScenes/HelloWorld.x3d"
target="_blank">http://x3dgraphics.com/<wbr>examples/<wbr>X3dForAdvancedModeling/<wbr>HelloWorldScenes/HelloWorld.<wbr>x3d</a>
<br>
<br>
<a moz-do-not-send="true"
class="m_-7047486244273330082moz-txt-link-freetext"
href="http://x3dgraphics.com/examples/X3dForAdvancedModeling/HelloWorldScenes/HelloWorldIndex.html"
target="_blank">http://x3dgraphics.com/<wbr>examples/<wbr>X3dForAdvancedModeling/<wbr>HelloWorldScenes/<wbr>HelloWorldIndex.html</a>
<br>
<br>
<a moz-do-not-send="true"
class="m_-7047486244273330082moz-txt-link-freetext"
href="http://x3dgraphics.com/examples/X3dForAdvancedModeling/HelloWorldScenes/HelloWorldCobweb.html"
target="_blank">http://x3dgraphics.com/<wbr>examples/<wbr>X3dForAdvancedModeling/<wbr>HelloWorldScenes/<wbr>HelloWorldCobweb.html</a>
<br>
<br>
<a moz-do-not-send="true"
class="m_-7047486244273330082moz-txt-link-freetext"
href="http://x3dgraphics.com/examples/X3dForAdvancedModeling/HelloWorldScenes/HelloWorldX3dom.xhtml"
target="_blank">http://x3dgraphics.com/<wbr>examples/<wbr>X3dForAdvancedModeling/<wbr>HelloWorldScenes/<wbr>HelloWorldX3dom.xhtml</a>
<br>
<br>
Examples attached for current/future testing. <br>
<br>
Note that current incarnation of Cobweb only uses
url/src to load an external X3D scene. Variations
between X3DOM and Cobweb are both great for
experimentation/testing and also future topics for
harmonization/alignment. <br>
<br>
Since X3D is embedded within HTML, mail attachments can
work with X3DOM if allowed by a user's permissions for
mail client. Perhaps we will also need Web3D.org as a
"trusted" site for Cobweb and X3DOM .js/.css libraries
to be allowed within enterprise IT systems. <br>
<br>
We'll also have to get much smarter and more effective
on Cross Origin Resource Sharing (CORS) if we want to
enable cross-linked content. <br>
<br>
Sounds like this topic is far-enough along for its own
page on the website... <br>
<br>
all the best, Don <br>
<br>
<fieldset
class="m_-7047486244273330082mimeAttachmentHeader"></fieldset>
<br>
<pre>______________________________<wbr>_________________
x3d-public mailing list
<a moz-do-not-send="true" class="m_-7047486244273330082moz-txt-link-abbreviated" href="mailto:x3d-public@web3d.org" target="_blank">x3d-public@web3d.org</a>
<a moz-do-not-send="true" class="m_-7047486244273330082moz-txt-link-freetext" href="http://web3d.org/mailman/listinfo/x3d-public_web3d.org" target="_blank">http://web3d.org/mailman/<wbr>listinfo/x3d-public_web3d.org</a>
</pre>
</blockquote>
<p>
</p>
</div>
</blockquote></div></div>
</blockquote>
<p>
</p></body></html>