- Open Web Foundation Agreement
The GPL, Creative Commons and open source have proven that boiler plate license can be intensely useful to enable and support open collaboration. The use of something similar seems like a good idea as a lot of specification development has been happening well outside of the W3C so could benefit from patent rights agreements and clear rules on re-use of such specs.
- Canonical provide engineering for Chrome OS under contract
The Register has the details, the most interesting to me was the pains Canonical took to clarify that Google’s OS won’t invade Ubuntu’s turf. I think that has to say something about Google’s plans, that Chrome OS simply isn’t meant as a replacement for full desktop operating systems and everything they can do. That does increase the mystery, though, of why you’d use Chrome OS and web services at all, though, if that’s the case.
- More details on Digital Economy Bill
Glyn Moody pulls together more information, including some of the legislative machinations being used to try to get this pushed through and the discredited report still being used to justify this draconian bit of law and policy making.
- An indie creator’s personal perspective on the Digital Economy Bill
Charlie Stross does his level based, in his usual idiom, to clarify just how badly this bit of legal wrangling will affect individual creators as opposed to the large, consolidated media how no doubt were the major lobbying forces responsible. Warning, Charlie uses strong language so be advised if you follow the link at work.
- MPAA calls concerns over lack of transparency into ACTA a distraction
Sherwin Siy of Public Knowledge deflates this tortured bit of rhetoric from the unsurprising supporter of ACTA. I think Sherwin is being conservative, I am convinced the MPAA is one of the major driving forces in the negotiations and the direct authoring of this horrible act of policy laundering.
- Protocol based mechanism for versioned access to the web
This is actually pretty clever, this subtle use described by RWW of the date and time mechanism already in the HTTP protocol. RWW is skeptical about older versions of dynamic sites but that may be possible, as well, since those applications usually are strongly versioned to begin with. The database backing them are probably the sticking point as those often change in ways that historical versions of the server application code couldn’t manage.