I recently learned through reading Alex Russell’s blog that Google had nominated him as a candidate on the upcoming W3C Technical Architecture Group elections. I thought this was great, as I more often then not find myself in violent agreement with Alex on how browsers should expose their guts to developers (amongst other things). As Alex put it:
I’m running to try to turn the TAG into an organization that has something to say about the important problems facing devs building apps today; particularly how new specs either address or exacerbate those challenges.
I thought it would be great to finally have someone who cares about the challenges that Web developers face represented on the TAG. So it then came to me as a bit of a humbling surprise that I had also been nominated (by Nokia) and asked to run by Robin Berjon. Admittedly, I was hesitant (and I still am) as I don’t know much about the TAG.
To us humble outsiders, the TAG has always been the Ivory Tower of the old guard of the Web: you know, where the guys that started it all pontificate about the nuances of URIs, HTTP Range 14 (don’t worry, I have no idea what the hell that is either!), and the mythical semantic web.
Because of the somewhat obscure range of topics, the TAG’s discussions have been the butt of many jokes on the Web (e.g., the fake tag) and humorous pictures on W3C Memes. It has also become synonymous with architecture astronautism. This is a shame, because, as Alex points out, it could be a force for the greater good, but the interactions with other working groups is generally been limited (and certainly does not appear to be focused on pursuing the issues relevant to Web developers who end up using the stuff coming out of the W3C).
Given the negative perception of the TAG, I basically share Alex’s “goal of turning the TAG into an advocacy organization for the interests of webdevs.” If elected, I want to work with other “reformist-minded candidates” (namely, Anne van Kesteren and Yehuda Katz) towards making that happen.
What and how?
Some proactive things that could be done by the TAG to meet the goal above include:
- Take the discussion to where developers are (Google+, Twitter, GitHub, etc.) – ask them what the TAG should focus on (or make the case to developers to show that there is value in the TAG).
- Talk to developers and find out what their pressing issues are. Do this by attending actual developer conferences and similar forums. See if we can make the TAG something cool and respected again!
- Instead of publishing findings at the W3C, publish findings in the popular developer press (e.g., A List Apart, Smashing magazine, .Net magazine, HTML5 Rocks, or similar) – i.e., where developers can actually read the findings, and in a common voice. Make TAG members available for interviews to media.
- Make time available to talk to developers on a regular (e.g., bi-monthly Q&A sessions on Google+)
- Help developer-based Community Groups (e.g., the RICG and the Extensible Web CG) with navigating the process of adding things to the Web platform.
- Work more closely with WebApps WG, System Apps, HTMLWG/WHATWG to make sure their API designs stay in sync and don’t cause developers unnecessary pain.
- Advocate to W3C Working Groups for more clear specs that meet the needs to developers as well as implementers.
If you have more/better ideas of what could be done to make the TAG more relevant to developers, please let me know in the comments.
How to vote
Unfortunately, voting is W3C member only. But otherwise, you need your AC rep to nominate a candidate (instructions).
What’s my pitch
This is what I submitted to the W3C as my pitch to get votes:
Over the last 6 years, Marcos’ background in interaction design has brought a unique perspective to Web standards. Long before there was the “Native Apps vs Web Apps” debate, Marcos was leading the charge to standardise installable web applications at the W3C through the Widgets family of specifications. Until recently, Marcos worked as a software architect at Opera Software, where he led the team that created Opera Widgets and Extensions platforms. Aside from his work on installable web applications, Marcos has been involved in numerous efforts to bring device APIs to the Web. To the TAG, Marcos can bring hands-on experience dealing with the architectural challenges that come from designing, deploying, and running installable web apps – and how those apps can safely interact with device APIs. For more information about Marcos’ qualifications, please see Marcos at LinkedIn.
The W3C has also published the list of other candidates.
9 thoughts on “W3C TAG elections”
Good luck 😉
I’m 100% behind you, and I know from years of experience working with you that you deserve a place within the TAG. As we were colleagues at Opera Software, you know how useful effective technical documentation is to external developers worldwide. I think I still hold the #1 search engine page return results for “web specifications” I built while working with you. If I can be of any help, please let me know.
You, alex, yehuda and anne would be my dream team… Good luck, we’ll do what we can to get you all some buzz 🙂
The TAG could do with some fresh thinking and input from Web Developers.
However I think a successful TAG will look at the short and long term, and think about the needs of all players on the web, hence comments like “into an advocacy organization for the interests of webdevs” worry me – why just webdevs
Secondly, the TAG needs to be able to decide what issues are important to the future web. HTTP Range 14 may have become a joke, but I’d rather someone who read up and understood what it was and why people are discussing, and *then* decide it is not important, rather than just say “don’t worry, I don’t know what it is”.
We need a group capable of both thinking about how to fix the problems of today and look at the long term roadmap of the web. Of course, the issues and technologies of today would seem obscure and academic to a develop in 2000. My understanding of Linked Data, RDF and the mysterious semantic web is that it could open opportunities for building apps that are unthinkable today; and lower the barrier to development, what today takes AJAX, APIs, jquery, etc would need nothing more complex that the equivalent of a img tag.
All I’m trying to say is that why there’s no question TAG at the moment could be better, it’s important not to dismiss ideas just because they don’t affect web developers today 🙂
Comments are closed.