https://wiki.idesg.org/index.php?action=history&feed=atom&title=Meeting_notes_from_September_22%2C_2014Meeting notes from September 22, 2014 - Revision history2026-05-26T16:36:17ZRevision history for this page on the wikiMediaWiki 1.38.4https://wiki.idesg.org/index.php?title=Meeting_notes_from_September_22,_2014&diff=4790&oldid=prevOmaerz: 1 revision imported: Initial Upload of old pages from IDESG Wiki2018-06-28T04:02:18Z<p>1 revision imported: Initial Upload of old pages from IDESG Wiki</p>
<p><b>New page</b></p><div>'''9/22/14 [[Privacy Requirements]] Working Group Meeting Notes'''<br />
<br />
==Attendees==<br />
* Jennifer Behrens<br />
* Jeff Brennan<br />
* Sean Brooks<br />
* David Bruggeman<br />
* Jessica Esparza<br />
* Edmund Jay<br />
* Naomi Lefkovitz<br />
* Meichorn<br />
* Ann Racuya-Robbins<br />
* Stuart Shapiro<br />
* M.A. Signorino<br />
* Steve Stoporoff<br />
* Jim Zok<br />
<br />
==Meeting Notes==<br />
'''FTC – New Requirement Discussion'''<br />
* FTC (represented by Stoporoff) concerned with retroactive application of a new data use. Before material changes happen, consumers should have to opt-in. <br />
* Difference between informed and affirmative consent. Often affirmative consent requires users to opt-in or lose access. What happens if they don’t agree? <br />
* Will continue discussing via email for one more week. Will dedicate 10 min. of next meeting to closing discussion if necessary. <br />
<br />
'''Functional Requirements Development'''<br />
* From now on Sean will send bare bones language Friday before PRWG call.<br />
* Should stick to language that is meaningful to the specific function. Can strike language that states the requirements with reference to that function.<br />
* May add more specific requirement re: data aggregation if this issue comes up in use cases.<br />
* Change text guidance to check marks if function does apply, NA if it doesn’t.<br />
* May wish to clarify boundaries between attributes and personal information at some point. May add a statement to indicate attributes we’re discussing are personal info.<br />
<br />
'''Functional Requirements Edits'''<br />
* Requirement 1: All functions applicable.<br />
* Requirement 2: All functions applicable.<br />
* Requirement 5: Application NA, remaining 3 functions applicable.<br />
* Requirement 6: Further explanation needed (text proposed but undecided) for attribute control, attribute verification, and eligibility decision.<br />
<br />
==Actions==<br />
* All will continue discussing FTC’s language via email<br />
* Will dedicate 10 min of next week’s meeting to conclude.<br />
* Next week will return to discussion of access and correction HL requirement for registration.<br />
* Sean will post meeting notes and updated document to the wiki.</div>Omaerz