[x3d-public] Again: 3d email

[Webmaster]

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.

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.

Leonard Daly




> There are disadvantages to links as well.
>
> Perhaps: lack of transparency as to where link goes on phones.
>
> 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?
>
> John
>
> On Dec 19, 2016 11:24 PM, "Webmaster" <webmaster at web3d.org 
> <mailto:webmaster at web3d.org>> wrote:
>
>     [Roy, sent from a different account, please see if this makes it
>     to x3d-public.]
>
>
>     On 12/19/2016 5:45 PM, Don Brutzman wrote:
>>     On 12/19/2016 12:50 PM, John Carlson wrote:
>>>     How do we achieve 3d email? Must the MUA's include x3dom or
>>>     cobweb as part of their source code?
>
>     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.
>     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)
>     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.
>
>     It would be best to use Don's recommendations of putting links in
>     an email from screen shots (or equivalent).
>
>     Leonard Daly
>
>
>
>>
>>     URL links can work, permissions vary.
>>
>>     http://x3dgraphics.com/examples/X3dForAdvancedModeling/HelloWorldScenes/HelloWorld.x3d
>>     <http://x3dgraphics.com/examples/X3dForAdvancedModeling/HelloWorldScenes/HelloWorld.x3d>
>>
>>
>>     http://x3dgraphics.com/examples/X3dForAdvancedModeling/HelloWorldScenes/HelloWorldIndex.html
>>     <http://x3dgraphics.com/examples/X3dForAdvancedModeling/HelloWorldScenes/HelloWorldIndex.html>
>>
>>
>>     http://x3dgraphics.com/examples/X3dForAdvancedModeling/HelloWorldScenes/HelloWorldCobweb.html
>>     <http://x3dgraphics.com/examples/X3dForAdvancedModeling/HelloWorldScenes/HelloWorldCobweb.html>
>>
>>
>>     http://x3dgraphics.com/examples/X3dForAdvancedModeling/HelloWorldScenes/HelloWorldX3dom.xhtml
>>     <http://x3dgraphics.com/examples/X3dForAdvancedModeling/HelloWorldScenes/HelloWorldX3dom.xhtml>
>>
>>
>>     Examples attached for current/future testing.
>>
>>     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.
>>
>>     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.
>>
>>     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.
>>
>>     Sounds like this topic is far-enough along for its own page on
>>     the website...
>>
>>     all the best, Don
>>
>>
>>     _______________________________________________
>>     x3d-public mailing list
>>     x3d-public at web3d.org <mailto:x3d-public at web3d.org>
>>     http://web3d.org/mailman/listinfo/x3d-public_web3d.org
>>     <http://web3d.org/mailman/listinfo/x3d-public_web3d.org>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20161220/bcf612cf/attachment.html>