w3cdevs Twitter archive for June 2021

June@VirtualW3C: workshops, meetings, W3Cx MOOC, etc. See https://www.w3.org/participate/eventscal.html

7 June - 2 July: @wot WG/IG meetings and testfest. See full agenda: https://www.w3.org/WoT/IG/wiki/F2F_meeting,_June_2021

22 June: new session of @w3cx #HTML5 Coding Essentials and Best Practices w/ Prof. @micbuffa on @edXOnline
https://www.edx.org/course/html5-coding-essentials-and-best-practices

18 June: deadline to register to the #W3CWorkshop on #smartcities: https://www.w3.org/2002/09/wbs/1/smartcities-ws-2021/

25 June: virtual @w3c Workshop on Smart Cities with pre-recorded talks, online discussions and interactive sessions https://w3c.github.io/smartcities-workshop/ #smartcities

Congrats to Heejin Chung (@Samsung), Avneesh Singh (@accessibledaisy), Eric Siow (@intel), @LeonieWatson (@TetraLogical), @cwilso (@Google) and Hongru (Judy) Zhu (@AlibabaGroup)!👏👏 https://twitter.com/w3c/status/1400734412782936067

These elected @ab participants join the continuing ones: @t (@mozilla), Tatsuya Igarashi (@Sony), @frivoal (#W3CInvitedExpert), @TzviyaSiegman (@wileyglobal) and @daithesong (@Apple).

The @ab's priorities in year 2021 are listed in https://www.w3.org/wiki/AB/2021_Priorities. One important discussion topic is related to #W3C's #Vision and #Strategy as presented last April to the @w3c membership https://youtu.be/0jSJYEHXBDs

Other topics include Legal entity, #Incubation, #inclusion, #globalization, #Diversity, and Process 2021 for which the @ab is now seeking review: https://twitter.com/w3c/status/1400485159808479236

7, 9 and 10 June: @sabouzah speaks @rightscon on accessible design, enhancing #UserExperience of #opensource tools for people with #disabilities and making usable technologies for non-left to right #Languages https://www.rightscon.org/program/

If you want to hear more about recent news on the Decentralized Identifiers work, watch @brent_zundel 's presentation on the topic he gave to W3C Members in May https://www.youtube.com/watch?v=NPqvqjMEGz0 https://twitter.com/w3c/status/1404713830740021250

Another document in the family of specifications describing #miniapps - this one about the lifecyle of mini apps, for the app as a whole, and individual pages in it https://twitter.com/w3c/status/1404715096547463169

The idea behind this lifecycle was presented in a talk we released a few months ago https://twitter.com/w3cdevs/status/1317782980052406277

To understand in more depth how #miniapps came to the family of Web standards, watch the just released discussion on “Mini-apps chartering and the Technical Architecture Group (@tag)” https://www.youtube.com/watch?v=1t73qWU6np8

Only a couple of weeks left to bring input on the new Process 2021 under consideration as the new rules to guide W3C standardization https://twitter.com/w3cdevs/status/1400739149024481283

if you need a quick refresh on what the W3C Process is https://twitter.com/w3cdevs/status/959076749291196416

And to learn more about what Process 2021 brings to the table, an earlier draft of it was presented at #w3cTPAC a few months ago https://twitter.com/w3cdevs/status/1338515804384600070

As a complement to the <audio> element allowing for basic streaming audio playback, the #WebAudio API facilitates complex audio processing and synthesizing. It gives #developers power and control in #audio production applications and game audio engines, for example.

Congrats to @padenot and @hochsays for the newly published @w3c #WebStandard "WebAudio API"! https://www.w3.org/TR/webaudio/ #timetoadopt https://twitter.com/w3c/status/1405494017190678537

To find out more what can be done with the WebAudio #API, check out this resource by @MDN:
https://developer.mozilla.org/en-US/docs/Web/API/Web_Audio_API/Using_Web_Audio_API

The #WebAudio API provides a rich set of modular blocks: auditory feedback in user interfaces, musical instruments, #soundtracks and effects for #entertainment and #gaming, teaching, spatial audio for #AR and #VR, online #audio editing apps, audio analysis and visualization, etc.

WebAudio is released as a standard, but that doesn't mean it is finished - The #w3c WebAudio #WorkingGroup is already working on updates, incl. new features - all of this happens in the spec #github repo:
https://github.com/WebAudio/web-audio-api

A curated list of awesome #WebAudio packages and demos can be found at: https://github.com/notthetup/awesome-webaudio

The early draft of the #WebRTC Encoded Transform API is at https://w3c.github.io/webrtc-encoded-transform/ and is developed, as usual, on github https://github.com/w3c/webrtc-encoded-transform

The #WebRTC Working Group is actively working on the specifications that enable end-to-end encryption in server-mediated calls in Web browsers (as FaceTime needs), in particular through the WebRTC Encoded Transform API (formerly known as Insertable Streams) https://twitter.com/w3c/status/1405152951283429379

Learn more about this work and in general what the #WebRTC Working Group has been up to in this presentation @jibrewery gave to W3C Members a few weeks ago https://www.youtube.com/watch?v=PQ5dGmqeuQI

If you participate and encounter challenges in your usage of the #WebAuthn stack, the Web Authentication Adoption Community Group would love to hear from you https://www.w3.org/community/webauthn-adoption/

10 more days to register to the @FIDOAlliance Developer Challenge, a good way to dive into #WebAuthn https://twitter.com/FIDOAlliance/status/1404500113213562880

The starting point of #WebNN on the Recommendation Track, by the #MachineLearning Working Group https://twitter.com/w3c/status/1407220398253543425

A reminder of what #WebNN is about https://twitter.com/w3cdevs/status/1367129066340573184

While the API is not shipping in browsers yet, if you want to try it out, there is a helpful polyfill maintained along with the specification https://webmachinelearning.github.io/webnn-getstarted

Head over to the github repository of the specification if you want to bring input https://github.com/webmachinelearning/webnn

That work is based on explorations of the limitations in existing browser primitives, with the goal of allowing web #developers to build rich editing experiences where browsers don't necessarily interfere

This brand new #WorkingGroup has for mission to provide use cases and introduce new #APIs relevant for text editing in the #browser https://twitter.com/w3c/status/1403236233703313410

The group's charter scope includes textual input and text
manipulation, clipboard, selection, undo, virtual keyboard, etc. Some of these draft specifications were presented at last #w3cTPAC breakout sessions: https://twitter.com/w3cdevs/status/1331278157589188608