Re: Starting Our Mission

Hi all,

I'll jump in here :) Nice to meet you all! Thank you for starting the
conversation!

I definitely agree with the idea of having this handle VR, AR and 3D on a
desktop. These three would future proof things to an extent. One other area
that'd be good to consider (which technically falls under AR) is mixed
reality and being able to track surfaces and position elements accordingly.
While not very common just yet, with HoloLens, Meta, Google Tango on
phones, Intel's RealSense camera, Magic Leap and whatever Apple has in
store, the expectation for this to be available functionality on our
displays is likely to be there in the future, so it'd be great to plan for
it ahead of time.

When it comes to building a schema and deciding how this would all work,
could I suggest following the work of A-Frame (aframe.io)? There'll be (and
already is) a huge number of web developers who'll understand how A-Frame
works and will have already integrated that into their websites.

As A-Frame is developing alongside the WebVR spec, I wonder if it'd be
beneficial to see whether the two streams can be one concept? Or am I
missing something about the idea of Declarative WebVR that differs from
what we'd be able to slowly evolve out from A-Frame?

Patrick Catanzariti

*-----------------------------------------------------------------------------------------*
*Web (Personal Portfolio):* http://www.patrickcatanzariti.com
*Web (PatCat Creative):* http://www.patcat.com
*Mob:* +61401197448
*Twitter:* @thatpatrickguy <https://twitter.com/thatpatrickguy>
*Facebook:* http://www.facebook.com/patrickcatanzariti
*Google+: *https://plus.google.com/+patrickcatanzariti
*-----------------------------------------------------------------------------------------*

On 1 December 2016 at 16:42, Leonard Daly <web3d@realism.com> wrote:

> While this group is called Declarative WebVR, it is likely that whatever
> is developed will also need to handle flat-3D (e.g., 3D objects displayed
> on a desktop) and Augmented Reality. Developers are not going to want to
> write one set of code for VR, another for flat-3D, and a third for
> augmented reality.
>
> That does not mean this should be an LCD (lowest common denominator)
> solution. A solution that has different capabilities depending on the
> application and hardware in use with rollbacks to simpler processing if the
> environment doesn't handle it.
>
> At this initial stage, I think it is important to only specify the
> technologies use by the environment (i.e., web pages and browsers) without
> trying to dictate how the technologies might constrain the desired
> capabilities. This is the time to dream.
>
> --
> *Leonard Daly*
> 3D Systems Architect & Cloud Consultant
> President, Daly Realism - *Creating the Future*
>