One W3C concept which I didn’t fully wrap my head around till recently is the idea of a test suite. It is a set of files that each test a certain property or aspect of a specification (… being things like HTML, CSS, or SVG).
For example, there could be a test which makes sure that a browser can render bold text correctly. That’s all it’d do. You’d view the file in the browser and you can quickly tell that whether the browser passed or failed.
There are a bunch of test suites…
Test suites are important so that you can test that the specification was implemented properly. What good is a spec unless it’s been implemented somewhere and implemented consistently?
At the World Wide Web Consortium (W3C) Technical Plenary and Advisory Council week last week, there was concern that not enough people knew about the W3C blogs.
Well here is a list of some of the ones that I read…
There are probably more that I just don’t know about. Hopefully someone will send me those links
These blogs are a great opportunity to interact and have a conversation with those who have an influential role on the future of the Web.
Well this week I’m not writing you from my home base in Washington DC. I’m up in Boston, MA for the W3C’s Technical Plenary / Advisory Committee Meetings Week… that’s a mouthful.
It’s a week where the individual working groups get together and meet. We also pick one day (Wednesday) and get everyone in one BIG room and meet, folks give presentations, and discuss issues. It’s a good time.
In the past at these events, I’ve had the opportunity of getting to chat with some of the smartest people in the Web. I always learn a ton.
Over the course of the week, I’m going to be posting my thoughts, photos, notes, and I’m sure much much more. Cheers!