RE: TAG on privacy by design for web applications

Thomas:

The TAG does post plain text versions of its minutes before review and approval, but I wish you wouldn't repost unapproved minutes, as you did:
http://lists.w3.org/Archives/Public/public-privacy/2012AprJun/0056.html

The original email containing unapproved minutes http://lists.w3.org/Archives/Public/www-tag/2012Apr/0127.html at least contains a pointer to the location of the location to be updated: http://www.w3.org/2001/tag/2012/04/02-agenda, with a great URL for the (updated, formatted) minutes on the topic you quoted:
                       http://www.w3.org/2001/tag/2012/04/02-minutes#item06

TAG:

In future, I suggest when sending out Draft minutes in email to www-tag@w3.org that we explicitly add a disclaimer DRAFT, UNREVIEWED, DO NOT FORWARD OR CITE header or other disclaimer.

Given that the TAG occasionally discusses issue that are contentious and highly political nature, I'd like to more strongly discourage this practice.


Public-Privacy discussion & TAG:

I think this is a "privacy" use case: 
I have an expectation of audience and distribution. I know the meeting isn't recorded, and that while minutes are taken, I expect to have an opportunity to review the minutes after a draft is published and before they are approved. My expectation wasn't met. 

My fault?  I should have known that if I am concerned about being misquoted I have to watch the irc log in real time and correct errors BEFORE the draft minutes get published, and trust that the person cleaning up the notes doesn't inadvertently change the meaning of what I said.
Thomas' fault? The TAG's fault for posting draft minutes publicly?

If there were APIs for any of this information flow -- if we somehow automated the processes by which minutes are taken, edited, drafts published, reviewed, approved -- would "API minimization" help ? How?

Larry
--
http://larry.masinter.net

Received on Sunday, 29 April 2012 15:47:42 UTC