The HTML5 validator will produce
both errors and warnings. I personally believe that many of the so-called
“errors” are at best shoulds and at worst pose no real
interoperability problems and are so frequently violated that the message
produced only serve to obscure real problems.
To help evaluate this thesis, I’ve analyzed a few sites,
categorized each error and warning, and taken a first pass at sorting these
messages. Those that I have sorted to the top are ones I’ve thought to
be less likely to be intentional and/or more likely to cause interoperation
issues. And, therefore, those that appear later tend to be ones that I either
find likely to be willful violations, or are unlikely to cause any problems at
all.
I want to stress that this ordering was done quickly, and is likely to have
many, many errors. I’m presenting it early in the hopes that others
would comment on this. Such comments may very well influence further
exploration I do in this area.
Tim Bray: The iPhone vision of the mobile Internet’s future omits controversy, sex, and freedom, but includes strict limits on who can know what and who can say what. It’s a sterile Disney-fied walled garden surrounded by sharp-toothed lawyers. The people who create the apps serve at the landlord’s pleasure and fear his anger.
Joseph Scott: Today we’ve turned on PuSH support for the more than 10.5 million blogs on WordPress.com. There’s nothing to configure, it’s working right now behind the scenes to help others keep up to date with your posts.
Tim Bray: Any standard that tries to constrain the way in which data, once received, is processed, is broken.
HTML5 is clearly broken by Tim’s definition. And while it may go too far in places, I can say that there are definitely many areas where that definition is a good thing. I wouldn’t have agreed with that statement a few years ago, but I do now. Enthusiastically. But to explain why, I need to first back up.
At no time did the current, up to the minute, versions — complete with occasional typos and botched commits — of the editor’s drafts become unavailable: HTML5, RDFa, MicroData, 2D Context, Markup, Diffs.
The absolute most that anybody, anywhere, ever proposed was that these very same documents be published with different labels
A few things that you can be sure of. The format of the presentation will be HTML5. And that it will be made available either on the web either concurrent with, or shortly after, the presentation itself.
DeWitt Clinton: The idea is that someday, any host on the web should be able to implement these open protocols and send messages back and forth in real time with users from any network, without any one company in the middle. The web contains the social graph, the protocols are standard web protocols, the messages can contain whatever crazy stuff people think to put in them.
DeWitt posted this within Buzz. If I want to keep up with things DeWitt’s posts via buzz, there’s a feed for that. This particular post generated a lot of comments, and there is a feed for that. I do have someissues I would like to see addressed, but basically what this means that Google just made available a blog to every GMail user.
Simon Phipps: While Matthew’s discussion is good (and the links are very useful), he misses the key point: that communities where one member has significantly more rights than all the rest tend to fail. If you must aggregate copyright, share rather than transfer, and aggregate in the hands of a community-controlled entity.
Tim Bray: the Net is the greatest listening engine ever devised. These days anyone can choose, with its help, to be well-informed
Yehuda Katz: It’s easy to spit out “lmgtfy.com” or RTFM, but in truth, these beginners barely know where to look. All too often, we (open source leaders) assume that if someone couldn’t figure out the right search term on Google, they can never become a viable community member.
I claim that there is a third ingredient that makes this all work. That ingredient is participating.
Anthony Laforge: The Dev channel has been updated to 5.0.317.0 for Google Chrome Frame.
This release addresses the issue I reported in September. Accordingly, I have set these pages to opt-in to the use of Google Chrome Frame if the User Agent header indicates that this is supported.
David Heinemeier Hansson: You thought we were never going to get to this day, didn’t you? Ye of little faith. Because here is the first real, public release of Rails 3.0 in the form of a beta package that we’ve toiled long and hard over. It’s surely not perfect yet, but we were out of blockers on the list, so here we go. Please give it a run around the block, try to update some old applications, try to start some new ones, and report back all the issues you find.
Rails 3.0 requires 1.8.7 or later. Both InstantRails and the (current, released) version of RubyInstaller bundle Ruby 1.8.6. The files on the Ruby site seem to be a scavenger hunt. While the next release of RubyInstaller will address this, we can run today with Cygwin.
