Perhaps the most daunting aspect of openness and transparency is the notion of "comprehensibility".  That is, even if I have access to stuff, and access to the right stuff, can I understand the thing?  In this context, that implies that open government source code should be well documented, designed simply and with support structures like tutorials, examples and possibly even a dev list or the like.

Also, after a quick look, I don't see anything here about the appropriate license?  I guess that's moot for things that the government cannot copyright, but there are cases where the artifact is assigned back to the government and then can be licensed and there are cases where the government forces users to agree to terms for access to stuff (data) that isn't copyrightable.  I would think some comments on this and guidelines for that stuff should be here.

best, Joe Hall (UC Berkeley/Princeton)