What is the TAG?
Special group in W3C chartered to:
- document and build consensus around principles of Web architecture and to interpret and clarify these principles when necessary;
- resolve issues involving general Web architecture brought to the TAG;
- help coordinate cross-technology architecture developments inside and outside W3C.
5 elected, 3 appointed, 1 chair (Tim), 1 staff contact (Yves)
The TAG
Tim Berners-Lee (W3C, Chair)
Daniel Appelquist (W3C Invited Expert, co-Chair)
Peter Linss (HPI, co-Chair)
David Baron (Mozilla)
Andrew Betts (The Financial Times)
Hadley Beeman (W3C Invited Expert)
Yves Lafon (W3C, staff contact)
Travis Leithead (Microsoft)
Mark Nottingham (Akamai)
Alex Russell (Google)
Current work of the TAG
- Pondering deep questions about the web
- Writing stuff: findings and other output
- Spec reviews
- Joint work with other groups
- Play a role in cross-organization liaisons
- Developer community engagement
Spec Reviews
The TAG's “Heartbeat”
Requesting a TAG Review
Open an issue with us on GitHub
(live demo)
What happens during a TAG review?
- One TAG member will own the issue
- We will likely invite someone to a TAG call or to join us at a f2f
- You will get live feedback from us in the github issue
- If appropriate we will issue a more formal feedback document
Where can I find the current work of the TAG?
Visit our page at https://tag.w3.org
Visit our meetings repo:
https://github.com/w3ctag/meetings
(demo)
Finding
Unsanctioned Tracking
“Tracking user activity on the Web using methods other than those defined for the purpose by the Web platform is harmful to the Web.”
WebRTC IP Address Leakage
https://github.com/w3ctag/spec-reviews/issues/14
- WebRTC feature being used for tracking
- TAG took this up at Berlin F2f in July
- Issue taken up by WebRTC group and taken to resolution: https://github.com/w3c/webrtc-pc/issues/179
Finding: Securing the Web
- Moving the Web to https
- Motivations thereof
- Coordinating with the web community
https://www.w3.org/2001/tag/doc/web-https
Great to see w3c move to https
Finding: End-to-End Encryption
- A follow-up to “securing the web”
- Adding our voice to advocates of e2e encryption
- Wading slightly into policy territory – intentionally and (we think) appropriately
Joint Work: Security & Privacy Self-Review
Weighing in on Key Issues
Ensuring a Strong and Secure Web Platform
Developer Outreach
10 Developer Outreach Events since 2013
Mix of panel discussions and unconference-style “summits” (https://extensiblewebsummit.org)
Berlin / Boston / London / Melbourne / San Francisco
~1000 developers
Some have been documented:
http://lanyrd.com/2015/extwebsummit/
Some have been streamed:
https://youtu.be/7BpsUYn6Z2o?t=35m17s
Why?
Take advantage of locations
Talk to and hear from web developers
Raise awareness of emerging web technologies
Be visible: this is your web
Get direct feedback from developers
Help to prioritize
Upcoming:
“Meet the TAG” meetup
London, 29 March 2016
https://ti.to/w3c-tag/meetthetag-london-2016
Next meet-up in Stockholm, probably 28 July
What's next? Developer survey in the works.
We're on github: https://github.com/w3ctag
Follow @w3ctag on Twitter
TAG Update for W3C AC March 2016
By Daniel Appelquist
TAG Update for W3C AC March 2016
TAG Update for W3C AC March 2016 Meeting
