The ICO is the UK regulator and was one of the first websites to comply with their own rules. They display a white box at the top of every page, and it never goes away unless you check the box and click the button to consent to cookies:

It's fair to assume this solution is considered compliant, if only because it was written by the regulator. However the text that they use assumes a clear familiarity with the term "cookies" - if you don't know what cookies are, it's meaningless to you. We thought the spirit of the law was to protect precisely the kind of people who don't know what a cookie is, and their text doesn't help those people at all. They also don't say what their cookies do, which is track their visitors in Google Analytics.

As the ICO themselves state in their guidelines:

"Any attempt to gain consent that relies on users' ignorance about what they are agreeing to is unlikely to be compliant."

Oh sweet irony.

Nice comment on the stupidity of the ICO's own handling of the forthcoming, and stupid, cookie directive (the ICO are the regulator in this case).

BTW, did I mention that I think it's a stupid directive?

Nice overview of the standards landscape around web apps by Scott Wilson of CETIS.

The web’s “small pieces loosely joined” architecture echoes what in another era we called the Unix philosophy. Web thinkers design reusable parts, and also reuse such parts where possible, because they know that the web both embodies and rewards this strategy.

Great article, outlining 7 principles that apply when working on/with/thru the web.

I really like this closing statement, not least because, as someone who has grown professionally with both, I have always felt that UNIX and the web stem from the same architectural mindset.