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 permenant chair (Tim),
1 staff contact (Yves)
...for now...
- Tim Berners-LeeÂ
(W3C, Chair) - Daniel AppelquistÂ
(Samsung, co-Chair) - Peter LinssÂ
(Invited Expert, co-Chair) - David Baron (Mozilla)
- Andrew Betts (Fastly)
- Hadley BeemanÂ
(W3C Invited Expert) - Yves LafonÂ
(W3C, staff contact) - Travis LeitheadÂ
(Microsoft) - Sangwhan MoonÂ
(Odd Concepts) - Alex Russell (Google)
Text
Text
Text
Text
Photo Credit: @ThisNatasha
Current work of the TAG
- Pondering deep questions about the web
- Writing stuff: findings and other output
- Design reviews (née “Spec Reviews”)
- Joint work with other groups
- Play a role in cross-organization liaisons
- Developer community engagement
Design Reviews
The TAG's “Heartbeat” 💓
Requesting a TAG Review
Open an issue with us on GitHub
Some closed issues
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
(all minutes linked from agendas)
Finding:
Distribution & Syndicated Content
“[...] content platforms such as Blendle, Facebook's instant articles and Google's AMP [... raise] important issues concerning the primacy of URLs and origins on the web, and the ability for users to make judgments about the trustworthiness and provenance of information they encounter while using it.”
Finding
Polyfills and the evolution of the Web
“Polyfills are a valuable part of Web architecture, because they promote the adoption of new features during the implementation process.”
Client-side API Design Principles
Developer Outreach
14 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
Â
Next event at next F2F: London ~Jan 31
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.
Â
Â
Â
Â
Election! 🗳️
2 seats are up for election
One more elected seat will be opening up soon, pending Process 2018
Diversity
The TAG has a diversity problem
The TAG should reflect the web technical community
We can best address this issue by nominating more diverse candidates
Please consider this when putting forward candidates for our upcoming elections
Â
Breakout on Diversity & Recruitment on Plenary Day
We're on github: https://github.com/w3ctag
Follow @w3ctag on Twitter
TAG Update for W3C AC November 2017 Meeting
By Daniel Appelquist
TAG Update for W3C AC November 2017 Meeting
TAG Update for W3C AC November 2017 Meeting
- 2,896