The advantage in using the CC infrastructure, is that it is globally recognised and all the processes / committees are established to implement in each country.

Interesting – I hadn’t thought of the ‘vote’ system. Ideally, what I’m imagining would perhaps be:

(1) visual, on-site, representation of the privacy position, denoted by icons;
(2) coded instructions that ‘tell’ the browser about the site’s privacy position – this would be used by browsers and plugins to mashup data/display it in different formats/enable ‘privacy settings’, where an individual might not go to sites with particular privacy positions or at least be warned;
(3) where a site lacks information, have the option of somehow notifying the site about the commons, and invite them to join

Adding (4) a way of reflecting public concerns is interesting, but I get a little worried about it because it could project the perceptions of privacy on top of companies who may actually have decent privacy provisions or vice versa. Example: Nokia-Siemens is falsely accused to selling DPI equipment to Iran for censorship, and so in reaction hosts of people ‘vote down’ N-S’ privacy position on the basis of that false information. Alternately, people ‘vote up’ Google’s privacy position, even though they’re well known to have poor protections in place (e.g. masking the last octet of search results).

Would you say that your critique of the commons would also extend to the creative commons?