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
The Presentation API allows rendering any Web content on a second screen: w3.org/TR/presentation-api/
It is available in @googlechrome and in development in @firefox and @webkit chromestatus.com/features/66…
The spec is developed in github.com/w3c/presentation-…
1
1
The Second Screen Working Group develops the Presentation API and the Remote Playback API, both #JS APIs used to render content from one device to a second screen.
Both these APIs have reached Candidate Recommendation status, i.e. #timetoimplement
This tweet is unavailable
1
5
8
The process is maintained by our Advisory Board @w3CAB (yes, they too are on Twitter!) with input from the public via the W3C Process Community Group w3.org/community/w3process/
Congrats to @chaals for shepherding that latest set of updates!
1
Among the notables changes this new process brings:
* a new elected seat on the @w3ctag (with an upcoming election)
* the enforcement of our code of conduct w3.org/Consortium/cepc/
* a non-WG process for maintaining Recommendations
w3.org/2018/Process-20180201…
1
This is for instance where the stages through which a spec needs to go through before becoming a #WebStandard are defined.
1
Today is the day where a new @w3c process comes into action - the well-titled “Feb 1 2018 Process Document” w3.org/2018/Process-20180201…
This document sets the rules and expectations around how W3C develops its standards and interacts with its stakeholders.
1
3
1
2
Self-assessment is rarely sufficient, but at least starting from the analysis of the people who know the technology the best hopefully helps others doing their own assessment.
1
For instance, the #WebRTC Working Group went through that exercise before going to Candidate Recommendation: github.com/w3c/webrtc-pc/iss… - this led to substantial additions to the WebRTC spec github.com/w3c/webrtc-pc/pul… with a detailed set of considerations w3.org/TR/webrtc/#privacy-an…
1
1
e.g. Does the spec create new “fingerprinting” surface (i.e. ways to identify users across Web sites or across devices)?
Does the spec open ways to bypass the same-origin policy (which isolates user data from one site to another)?
1
The @w3ctag has been pushing for all specs it reviews to go through a self-assessment of their impact on security and privacy for Web users. The security & privacy questionnaire documents which questions spec authors need to consider w3.org/TR/security-privacy-q…
We're now debating additions/edits to the Security and Privacy Questionnaire, which should help spec authors/editors think through the implications of adding their new feature to the web platform.
Current draft:
w3.org/TR/security-privacy-q…
@w3ctag
1
Chrome and Firefox now have public client-side implementations of the Web Authentication API (Working Draft version 7) #webauthn w3.org/blog/webauthn/2018/01…
1
If you don't know a script well enough to use the native keyboard, try out these new #unicode character pickers. It works in any #browser! See other avail. pickers: r12a.github.io/pickers
Two new character pickers available:
Cyrillic (most cyrillic characters) r12a.github.io/pickers/cyril…
Russian (specifically) r12a.github.io/pickers/russi…
Both using new picker framework (v22), which has some new features.
1
Every charter that comes up for discussion (either anew or for renewal) gets announced on one of our many mailing lists lists.w3.org/Archives/Public… - subscribe to it if you want to stay up to date (who doesn't want more 📧?)
The chartering and #WebRTC future discussions are happening on the mailing list lists.w3.org/Archives/Public… and in a dedicated github repo github.com/w3c/webrtc-charte…
1
Right now, the draft new charter is setting the group to finish its ongoing work, look at bringing low-level APIs to get rid of the dependency on SDP (if you don't know what that is, DO NOT ASK, DO NOT LOOK IT UP 🙈🙉🙊), and explore new foundations for P2P data channels.
1
1
2
Part of why now is a good time to chime in on the future of #WebRTC is because the Working Group is looking at rechartering soon - a group charter defines its goal and scope for the upcoming couple of years.
1
1
@kennethrohde achievement unlocked 🏆: use of “non-relativistic scalar" in a pull request comment github.com/w3c/sensors/pull/…
1
2
The @w3ctag awakens (for the second day of their meeting) - RT if they should keep fighting the Proprietary Empire, ♥ if they should go back to sleep.
1
1
1
2
A complementary API is under development to bring that control to the Web app directly w3c.github.io/mediacapture-i… developed at github.com/w3c/mediacapture-…
That one is available in @googlechrome and in development in @firefox bugzilla.mozilla.org/show_bu…