Get involved in @w3c and give input on all of our specs. See also youtube.com/@W3COfficial and @w3cdevs@w3c.social. By @dontcallmeDOM and @marieforgue
Joined October 2014
- Tweets 4,375
- Following 608
- Followers 11,339
- Likes 2,472
An opp. you can't miss!
Last day to submit your application to the 07th Open Call ⏳
Deadline 06th July - 17:00 (CEST) 📅
Do not miss the opportunity to support your #Research in ICT #Standardisation, apply now!
standict.eu/standicteu-2023-…
1
8 July: At #wac2022 in Cannes 🇫🇷, the @w3c Web Audio #WorkingGroup, via @padenot, will give an update of recent work and what new features to expect wac2022.i3s.univ-cotedazur.f… @WebAudioConf
4
4
5 July: opening a new session of the @thew3cx "#JavaScript Introduction" #MOOC w/ Prof. @micbuffa via @edxOnline
Enroll now! edx.org/course/javascript-in…
1
3
1
🗓️July@w3c: #JavaScript course, Web #audio conference, etc. See more in w3.org/participate/eventscal…
1
4
1
Apply now before 6 July if you are based in 🇪🇺 and looking for #funds to support your work on @w3c
#WebStandards. Do not miss this opp as #w3cTPAC is approaching! Many topics such as #AI, #a11y, #privacy, #media, etc. More in standict.eu/index.php/standi…
You have time until next 06th July⏳to submit applications to the 7th Open Call!
The leading theme is #AI, #Data & #Robotics”, but any other technological area linked to the #ICT Rolling Plan is equally eligible🙌
Do not miss the opportunity, apply now⤵
standict.eu/index.php/standi…
1
4
W3C immersive web strategist @dontcallmeDOM declares: “@w3c is joining the Metaverse Standards Forum to accelerate the coordination in building an interoperable platform for the #metaverse, in which @ImmersiveWebW3C's vision is set to play a critical role.” #WebStandards
This tweet is unavailable
2
1
8
21 June: @dontcallmeDOM presents "Weaving Client, Edge and Cloud computing for the Web" @fraunhoferfokus in #Berlin 🇩🇪 #FOKUSmws fokus.fraunhofer.de/en/fame/…
1
1
5
The latter may use the output of another group under review, the #RDF Dataset Canonicalization and Hash Working Group
This tweet is unavailable
The #VerifiableCredentials Working Group is back under a new charter to work on a new version of the Verifiable Credentials Data Model and how to express and associate proofs of integrity for Verifiable Credentials w3.org/2022/06/verifiable-cr…
This tweet is unavailable
1
1
4
The @W3CAB's priorities in 2022 are listed in w3.org/wiki/AB/2022_Prioriti…
1
These elected participants join the continuing ones: Heejin Chung (@Samsung), Avneesh Singh (@accessibledaisy), Eric Siow (@intel), @LeonieWatson (@TetraLogical), @cwilso (@Google) and Hongru (Judy) Zhu (@AlibabaGroup)
1
1
Congrats to Wei Ding (@Huawei), Tatsuya Igarashi (@Sony), @frivoal (W3C #InvitedExpert), @TzviyaSiegman (@WileyGlobal), @daithesong (@Apple)! 👏👏👏
This tweet is unavailable
1
2
The limit of videoconferencing systems to a single screen share is a choice of these systems vendors (probably because screen content often requires to be close to fullscreen to be readable) - #WebRTC has no such restriction.
How would concurrent screen shares be used?
1
Want to contribute to WebDriver BiDi? Head up to the #github repo! github.com/w3c/webdriver-bid…
Want to know more about WebDriver BiDi? There is an explainer! github.com/w3c/webdriver-bid…
1
2
WebDriver BiDi is a proposed bidirectional protocol for browser automation, building on and extending #WebDriver: w3c.github.io/webdriver-bidi…
Congrats to the @w3c working group and all browser teams involved 🎉 @FirefoxDevTools is the first browser that ships the new automation protocol to their stable release channel 👀 You can test it using @webdriverio today and in v8 it will be build in 😉
1
3
The work is happening in its own #github repo. Check it out! github.com/w3c/mediacapture-…
This can be mitigated by browsers discouraging tab capture (but that goes against the goal of making the Web as widely useful as possible). Viewport Capture proposes an alt approach where a browser tab can only be captured if it respects well-defined cross-origin characteristics
1
... since it potentially weakens the cross-origin protections that prevent a #Website to read the user-customized version of another Web site (think evil.example reading bank.example) w3c.github.io/mediacapture-s…
2