[x3d-public] Preprint of new WebComponent based approach to X3D and XML3D

[Michael Aratow]

I am able to download it.


On 6/17/16 4:53 AM, Philipp Slusallek wrote:
> Hi Roy,
>
> Yes, sorry for the late delivery of the paper. I did not get an error
> message from the list server and thus did not know that my email was
> indeed not distributed.
>
> Regarding the link: I have tried it from several network locations and
> browsers and it is working for me. Have you tried with http instead of
> https?
>
> It should work, and I cannot see a problem here. Does any one else have
> an issue with the link?
>
>
> Best,
>
> 	Philipp
>
> Am 17.06.2016 um 11:37 schrieb Roy Walmsley:
>> Philipp,
>>
>> Thank you for the link. However, I tried to access it, from various browsers, and was unsuccessful. Is there a problem with the server at your end?
>>
>> Regards,
>>
>> Roy
>>
>> -----Original Message-----
>> From: x3d-public [mailto:x3d-public-bounces at web3d.org] On Behalf Of Philipp Slusallek
>> Sent: 17 June 2016 06:13
>> To: 'X3D Graphics public mailing list'
>> Subject: [x3d-public] Preprint of new WebComponent based approach to X3D and XML3D
>>
>> [Resent, as the original email was apparently not relayed through the list]
>>
>> Hi,
>>
>> Here is the preprint of the paper I mentioned in my earlier emails:
>>     https://cloud.dfki.de/owncloud/index.php/s/CRQ9qhpQq2YSX6X
>>
>> Note, this is not meant as the final solution but more as a proof of concept and a first study of what can be done with modern Web technology for declarative 3D.
>>
>> What is exciting, though, is that we can already load an unmodified X3DOM scene and convert it to our WebComponents representation and its gets rendered interactively.
>>
>> We do not support routes or scripts, yet. But we can mix and match X3D and XML3D as we like, which is interesting and goes back to a discussion we had with the X3DOM group quite some time ago about the idea we had that a powerful enough core should be able to actually support both front ends. It now can!
>>
>> Of course, a lot is still missing and there are many design choices that would need to be made. We would be happy to have a discussion about how to proceed with this approach. Maybe even others would be interested in helping to implement more of X3D nodes and determine the right choices for doing so?
>>
>> *Constructive* comments are very welcome.
>>
>>
>> Best,
>>
>> 	Philipp
>>
>
>
> _______________________________________________
> x3d-public mailing list
> x3d-public at 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/20160617/d65710df/attachment.html>