Right - I would guess, (with credit and your permission), that Attrition & PogoWasRight.org would switch to your data set or at least import the data you've collected into their database.<br><br><div><span class="gmail_quote">
On 10/16/06, <b class="gmail_sendername">Allan Friedman</b> <<a href="mailto:allan_friedman@ksgphd.harvard.edu">allan_friedman@ksgphd.harvard.edu</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
> It would be cool if we could begin distinguishing whether it was employee<br>> data that was lost or client data, (or both).<br><br>There's a field for data subject my data. I also note the presence of<br>a principle-agent relationship for data protection, for when a third
<br>party is safeguarding the data on behalf of the {employer/merchant}.<br>Finally, the data subject could have no direct or transitive<br>relationship with the data subject (i.e. Choicepoint). I only have it<br>for publicly traded companies, though.
<br><br>I hate to keep this stuff as a shadow dataset, but since exact date<br>and sequence of info is critical to our project, it's taken longer<br>than expected to make sure it's good. We really look forward to<br>sharing it soon.
<br><br>allan<br>_______________________________________________<br>Dataloss Mailing List (<a href="mailto:dataloss@attrition.org">dataloss@attrition.org</a>)<br><a href="http://attrition.org/dataloss">http://attrition.org/dataloss
</a><br>Tracking more than 137 million compromised records in 430 incidents over 6 years.<br><br><br><br></blockquote></div><br>