Re: Request for meeting during TPAC

That would be great for us as long as it works for the XR folks. Dan




‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Wednesday, 28 August 2019 13:08, Janina Sajka <janina@rednote.net> wrote:

> Yes, shall we say 11:00 Friday?
> 

> Daniel Appelquist writes:
> 

> > That is usually the time we are doing our TAG sync at close to the end of TPAC. Is ther a chance we could do it in the session befoe lunch on Friday instead? Dan
> > ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
> > On Wednesday, 28 August 2019 12:54, Janina Sajka janina@rednote.net wrote:
> > 

> > > Hi, Daniel:
> > 

> > > Daniel Appelquist writes:
> > 

> > > > This sounds great to me. When do you want us there?
> > 

> > > How about Friday right after afternoon break, say about 3:30 PM? Would
> > > that work?
> > 

> > > Best,
> > 

> > > Janina
> > 

> > > > Dan
> > > > ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
> > > > On Tuesday, 27 August 2019 18:40, Janina Sajka janina@rednote.net wrote:
> > 

> > > > > Dear Colleagues:
> > 

> > > > > The Accessible Platform Architectures (APA) Working Group requests
> > > > > guidance from the TAG as outlined below. We believe a joint meeting with
> > > > > appropriate TAG members during TPAC could expedite our concerns most
> > > > > helpfully and are, therefore, requesting your assistance setting that
> > > > > conversation up.
> > 

> > > > > Here are the several topics we'd like to cover:
> > 

> > > > > 1.) Architecture in XR
> > 

> > > > > We need a better understanding of tradeoffs between the existing
> > > > > WebGL and emerging WebAssembly (WASM) and WebGPU approaches. Where's the best
> > > > > opportunity to support semantics in content? And what level of
> > > > > semantics is practicable?
> > 

> > > > > We have also invited members of Immersive Web to a
> > > > > conversation that will cover our concerns in this area.
> > 

> > > > > 2.) We have two Task Forces working toward eventual normative
> > > > > specifications and we want to be sure we're developing in a supportable
> > > > > and sustainable direction.
> > 

> > > > > a.) Our Pronunciation TF is working toward giving authors a
> > > > > reliable markup approach for specifying pronunciation by TTS
> > > > > engines. Please note their FPWD documents listed here:
> > 

> > > > > http://lists.w3.org/Archives/Public/public-apa/2019Aug/0044.html
> > 

> > > > > b.) Our Personalization TF is developing support for users
> > > > > who depend on Augmentative and alternative communication (AAC)
> > > > > assistive technologies. Their key document is here:
> > 

> > > > > https://www.w3.org/TR/personalization-semantics-1.0/
> > 

> > > > > Your guidance and help is gratefully appreciated.
> > 

> > > > > Janina Sajka, Chair
> > > > > Accessible Platform Architectures (APA)
> > > > > http://www.w3.org/wai/apa/
> > 

> > > > > 

> > 

> > > > 

> > 

> > > > > 

> > 

> > > > 

> > 

> > > > > Janina Sajka
> > 

> > > > > Linux Foundation Fellow
> > > > > Executive Chair, Accessibility Workgroup: http://a11y.org
> > 

> > > > > The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
> > > > > Chair, Accessible Platform Architectures http://www.w3.org/wai/apa
> > 

> > > --
> > 

> > > Janina Sajka
> > 

> > > Linux Foundation Fellow
> > > Executive Chair, Accessibility Workgroup: http://a11y.org
> > 

> > > The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
> > > Chair, Accessible Platform Architectures http://www.w3.org/wai/apa
> 

> --
> 

> Janina Sajka
> 

> Linux Foundation Fellow
> Executive Chair, Accessibility Workgroup: http://a11y.org
> 

> The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
> Chair, Accessible Platform Architectures http://www.w3.org/wai/apa