- From: Frederick Hirsch via cvs-syncmail <cvsmail@w3.org>
- Date: Tue, 20 Apr 2010 20:23:04 +0000
- To: public-dap-commits@w3.org
Update of /sources/public/2009/dap/privacy-rulesets
In directory hutz:/tmp/cvs-serv8840
Modified Files:
Overview.html
Log Message:
fix additional validation issues, reversed tag order, missing tags etc
Index: Overview.html
===================================================================
RCS file: /sources/public/2009/dap/privacy-rulesets/Overview.html,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -d -r1.3 -r1.4
--- Overview.html 20 Apr 2010 20:17:20 -0000 1.3
+++ Overview.html 20 Apr 2010 20:23:02 -0000 1.4
@@ -118,7 +118,10 @@
</p>
<section>
<h2>Sharing</h2>
- <p><b><code>internal</code></b>: The data can be shared internally within the <a>data collector</a>'s organization and with other organizations that help the <a>data collector</a> provide the service requested in the current interaction.
+ <p><b><code>internal</code></b>: The data can be shared
+ internally within the <a>data collector</a>'s organization and
+ with other organizations that help the <a>data collector</a>
+ provide the service requested in the current interaction. </p>
<ul>
<li>Example: A user uses an application that invokes the media capture API to provide a voice search service. The voice capture gets shared only with the organization that provides the app and its partner company that provides the search results, but not with any other company.</li></ul>
@@ -128,27 +131,57 @@
<p><code><b>unrelated-companies</b></code>: The data can be shared outside of the <a>data collector</a>'s organization with other organizations that it does not control and is not controlled by.</p>
<ul>
- <li>Example: A user provides contact details obtained through the contacts API to an application provider and that application provider shares them with other unaffiliated companies, like direct marketers or credit reporting agencies.</ul></li>
+ <li>Example: A user provides contact details obtained
+ through the contacts API to an application provider and that
+ application provider shares them with other unaffiliated
+ companies, like direct marketers or credit reporting
+ agencies.</li>
+ </ul>
<p><code><b>public</b></code>: The data can be made public.</p>
<ul>
- <li>Example: A user uses an application employing the calendar API to post an event on a public web site.</ul></li>
+ <li>Example: A user uses an application employing the calendar API to post an event on a public web site.</li></ul>
- <p>It is important to note that none of the <code>sharing</code> attributes are mutually exclusive -- any of them may be combined to form more permissive grants of sharing abilities than any single one of them on its own.</p>
+ <p>It is important to note that none of the <code>sharing</code>
+ attributes are mutually exclusive -- any of them may be combined
+ to form more permissive grants of sharing abilities than any
+ single one of them on its own.</p>
</section>
<section>
<h2>Secondary Use</h2>
- <p>It can sometimes be difficult to distinguish between "primary" uses of user data and "secondary" uses. What users believe to be <a title='primary use'>primary uses</a> and what applications providers believe to be <a title='primary use'>primary uses</a> are not always the same, because all of the functionality that contributes to being able to provide a particular application or service is not always evident to users. The attributes below are crafted with the user's conception of <a>secondary use</a> in mind, and therefore attempt to cover all uses of user data that users might want to express a preference about (without making the attributes overly granular).</p>
+ <p>It can sometimes be difficult to distinguish between
+ "primary" uses of user data and "secondary" uses. What users
+ believe to be <a title='primary use'>primary uses</a> and what
+ applications providers believe to be <a title='primary
+ use'>primary uses</a> are not always the same, because all of
+ the functionality that contributes to being able to provide a
+ particular application or service is not always evident to
+ users. The attributes below are crafted with the user's
+ conception of <a>secondary use</a> in mind, and therefore
+ attempt to cover all uses of user data that users might want to
+ express a preference about (without making the attributes overly
+ granular).</p>
- <p><code><b>contextual</b></code>: The data may only be used for the purpose of completing the current interaction. Contextual uses may include securing, troubleshooting or improving the service being provided or providing advertising in the context of the current interaction.</p>
+ <p><code><b>contextual</b></code>: The data may only be used for
+ the purpose of completing the current interaction. Contextual
+ uses may include securing, troubleshooting or improving the
+ service being provided or providing advertising in the context
+ of the current interaction.</p>
<ul
- ><li>Example: A user sets reminders for upcoming events using an application that uses the calendar API. The application uses the events data to deliver the reminders and to serve a contextual ad when the user sets a reminder.</ul></li>
+ ><li>Example: A user sets reminders for upcoming events
+ using an application that uses the calendar API. The application
+ uses the events data to deliver the reminders and to serve a
+ contextual ad when the user sets a reminder.</li></ul>
<p><code><b>customization</b></code>: The data may be used to customize, personalize, or otherwise tailor the current interaction for the user.</p>
<ul>
- <li>Example: A user records songs that he or she hears using an application that employs the media capture API. The application identifies and uses the recorded songs to suggest new music that the user may be interested in.</ul></li>
+ <li>Example: A user records songs that he or she hears using
+ an application that employs the media capture API. The
+ application identifies and uses the recorded songs to
+ suggest new music that the user may be interested
+ in.</li></ul>
<p><code><b>marketing-or-profiling</b></code>: The data may be used for marketing and/or profiling purposes. Marketing may occur over time and via any channel (web, email, telemarketing, etc.). Profiling involves the creation of a collection of information about an individual and applies to <a title='profile'>profiles</a> created for any purpose other than customization (e.g., for research, to sell to other organizations, etc.).</p>
<ul>
@@ -162,17 +195,17 @@
<p>The fact that most web servers automatically record logs of user activity -- and that many of these logs are never deleted -- can complicate the task of having applications abide by user-defined retention policies. The retention attributes defined below assume that as a general matter, all <a title='data collector'>data collectors</a> may retain user data for a baseline period of 35 days for the purposes of maintenance, security, and troubleshooting. The attributes express user preferences that apply to retention practices that go beyond this baseline period.</p>
- <p><code><b>no</b></code>: The data may only be retained for the baseline period.</p></li>
+ <p><code><b>no</b></code>: The data may only be retained for the baseline period.</p>
<ul>
- <li>Example: A user uses a webcam service that employs the media capture API. The video data is not retained after 35 days.</ul></li>
+ <li>Example: A user uses a webcam service that employs the media capture API. The video data is not retained after 35 days.</li></ul>
- <p><code><b>short</b></code>: The data may be retained beyond the baseline period, but only for a limited time.</p></li>
+ <p><code><b>short</b></code>: The data may be retained beyond the baseline period, but only for a limited time.</p>
<ul>
- <li>Example: A user uses an application that invokes the media capture API to provide a voice search service. The voice searches are retained for 90 days to optimize search results.</ul></li>
+ <li>Example: A user uses an application that invokes the media capture API to provide a voice search service. The voice searches are retained for 90 days to optimize search results.</li></ul>
- <p><code><b>long</b></code>: The data may be retained beyond the baseline period for an unspecified or indefinite amount of time.</p></li>
+ <p><code><b>long</b></code>: The data may be retained beyond the baseline period for an unspecified or indefinite amount of time.</p>
<ul>
- <li>Example: A user drafts SMS messages using an application that invokes the messaging API. Those draft SMS messages are retained indefinitely until the user deletes them.</ul></li>
+ <li>Example: A user drafts SMS messages using an application that invokes the messaging API. Those draft SMS messages are retained indefinitely until the user deletes them.</li></ul>
<p>The <code>retention</code> attributes are mutually exclusive.</p>
</section>
@@ -187,44 +220,47 @@
<dl>
<dt><p><b>Least permissive:
- <br><code>sharing=internal</code>
- <br><code>secondary-use=contextual</code>
- <br><code>retention=no</code>
- </b></dt>
- <dd>The least permissive <a title='privacy ruleset'>ruleset</a> says that the user wants her data shared only internally by the <a>data collector</a> and organizations that help the <a>data collector</a> deliver the service, only used for contextual purposes (which includes contextual advertising), and not retained beyond the baseline period.</p></dd>
+ <br /><code>sharing=internal</code>
+ <br /><code>secondary-use=contextual</code>
+ <br /><code>retention=no</code>
+ </b></p></dt>
+ <dd><p>The least permissive <a title='privacy ruleset'>ruleset</a> says that the user wants her data shared only internally by the <a>data collector</a> and organizations that help the <a>data collector</a> deliver the service, only used for contextual purposes (which includes contextual advertising), and not retained beyond the baseline period.</p></dd>
<dt><p><b>Internal customization/personalization:
- <br><code>sharing=internal</code>
- <br><code>secondary-use=customization</code>
- <br><code>retention=short</code>
- </b></dt>
- <dd>Some users may want to permit their data to be used internally by the <a>data collector</a> to do individualized analytics or provide some personalization based on recent activity, but not for marketing purposes. This <a title='privacy ruleset'>ruleset</a>, which allows data to be retained for a limited period and used for customization but not shared, corresponds to that set of preferences.</p></dd>
+ <br /><code>sharing=internal</code>
+ <br /><code>secondary-use=customization</code>
+ <br /><code>retention=short</code>
+ </b></p></dt>
+ <dd><p>Some users may want to permit their data to be used
+ internally by the <a>data collector</a> to do
+ individualized analytics or provide some personalization
+ based on recent activity, but not for marketing
+ purposes. This <a title='privacy ruleset'>ruleset</a>,
+ which allows data to be retained for a limited period and
+ used for customization but not shared, corresponds to that
+ set of preferences.</p></dd>
<dt><p><b>Profile-based advertising:
- <br><code>sharing=internal</code>
- <br><code>secondary-use=marketing-or-profiling</code>
- <br><code>retention=long</code></b></dt>
- <dd>If users want to allow the <a>data collector</a> to use their data in <a title='profile'>profiles</a> that are later used to target ads back to them, this <a title='privacy ruleset'>ruleset</a> would allow for that, with sharing still limited for internal use but with marketing, profiling, and retention allowed.</p></dd>
+ <br /><code>sharing=internal</code>
+ <br /><code>secondary-use=marketing-or-profiling</code>
+ <br /><code>retention=long</code></b></p></dt>
+ <dd><p>If users want to allow the <a>data collector</a> to use their data in <a title='profile'>profiles</a> that are later used to target ads back to them, this <a title='privacy ruleset'>ruleset</a> would allow for that, with sharing still limited for internal use but with marketing, profiling, and retention allowed.</p></dd>
<dt><p><b>Public:
- <br><code>sharing=public</code>
- <br><code>secondary-use=contextual</code>
- <br><code>retention=long</code>
- </b></dt>
- <dd>This <a title='privacy ruleset'>ruleset</a> lets users express their permission to have their data shared publicly, but not used by the <a>data collector</a> for non-contextual purposes.</p></dd>
+ <br /><code>sharing=public</code>
+ <br /><code>secondary-use=contextual</code>
+ <br /><code>retention=long</code>
+ </b></p></dt>
+ <dd><p>This <a title='privacy ruleset'>ruleset</a> lets users express their permission to have their data shared publicly, but not used by the <a>data collector</a> for non-contextual purposes.</p></dd>
<dt><p><b>Most permissive:
- <br><code>sharing=internal</code>
- <br><code>sharing=affiliates</code>
- <br><code>sharing=unrelated-companies</code>
- <br><code>secondary-use=contextual</code>
- <br><code>secondary-use=customization</code>
- <br><code>secondary-use=marketing-or-profiling</code>
- <br><code>retention=long</code>
- <br><code></b></dt>
- <dd>The most permissive <a title='privacy ruleset'>ruleset</a> allows all three kinds of sharing, all three kinds of <a>secondary use</a>, and indefinite retention.</p></dd>
+ <br /><code>sharing=internal</code>
+ <br /><code>sharing=affiliates</code>
+ <br /><code>sharing=unrelated-companies</code>
+ <br /><code>secondary-use=contextual</code>
+ <br /><code>secondary-use=customization</code>
+ <br /><code>secondary-use=marketing-or-profiling</code>
+ <br /><code>retention=long</code>
+ <br /></b></p></dt>
+ <dd><p>The most permissive <a title='privacy ruleset'>ruleset</a> allows all three kinds of sharing, all three kinds of <a>secondary use</a>, and indefinite retention.</p></dd>
</dl>
</section>
-
-
-
-
<section class='appendix'>
<h2>Glossary</h2>
<p>
@@ -249,8 +285,5 @@
</p>
</section>
-
-</section>
-
</body>
</html>
Received on Tuesday, 20 April 2010 20:23:06 UTC