Re: 3d favicons

Rik,

This is a great topic for the Immersive Web Community Group and nicely fits
into the new category of "directions beyond and separate from WebXR Device
API."

I second Nell's suggestion that you follow the usual process
<https://github.com/immersive-web/proposals/blob/master/README.md> of
starting out with a descriptive Issue in the proposals repo
<https://github.com/immersive-web/proposals/issues>.

>From there, I suggest that you ping the major stake holders in order to get
momentum and consensus behind the idea. Once there's clearly enough
interest and a general agreement to move forward, I'll create a separate
repo with an explainer document, sample code, and eventually pointers to
experimental implementations.

The general idea of the process is to get stake holders mostly on the same
page (including people from other working or community groups if necessary)
and then make a decision about how to take it through the W3C
recommendation process. A lot can happen between that first Issue and
moving into a working group!

favicons are a topic that I think has a lot of interest and a clear
utility, so I expect that it has a pretty good chance of getting the
attention of relevant stake holders, though most of them are already knee
deep in WebXR Device API implementations so it's sometimes tricky. :-)

- Trevor



On Fri, Aug 17, 2018 at 4:24 PM, Waliczek, Nell <nhw@amazon.com> wrote:

> This is something that I have heard several different folks express
> interest in.  The best way to move this forward would be to write up an
> issue on the Proposals Repo https://github.com/immersive-web/proposals .
> The write-up should have a clear description of the problem and a rough
> idea of how you’re thinking about trying to solve it.  A few paragraphs is
> more than sufficient; no need for a full explainer or idl of any sort yet.
>
>
>
> Another company will need to respond to the issue to say they’re
> interested in collaborating on design with intent to implement if agreement
> can be reached.  Initial design work can start in the issue, and, when
> ready, Trevor will open up a repo in the Immersive Web GitHub organization
> for you to start iterating on the design in more detail.
>
>
>
> I’m very excited that Magic Leap is seriously considering participating in
> standards design rather than taking an approach that would run the risk of
> fracturing the Immersive Web 😊
>
>
>
> Nell
>
>
>
> *From: *Rik Cabanier <rcabanier@magicleap.com>
> *Date: *Friday, August 17, 2018 at 3:34 PM
> *To: *"public-immersive-web@w3.org" <public-immersive-web@w3.org>
> *Subject: *3d favicons
> *Resent-From: *<public-immersive-web@w3.org>
> *Resent-Date: *Friday, August 17, 2018 at 3:32 PM
>
>
>
> All,
>
>
>
> We're interested in coming up with a standardized way of supporting 3D
> favicons so a website can have a 2D and a 3D icon.
>
> Helio [1] already implemented some support but we want to have a
> standardized solution that incorporates everyone's input.
>
>
>
> Is anyone else interested in pursuing this?
>
>
>
> Rik
>
>
>
> 1: https://www.magicleap.com/experiences/helio
>



-- 
Trevor F. Smith
Reality Research Engineer
Emerging Technologies @ Mozilla
trsmith@mozilla.com