Skip to content

Commit

Permalink
Make all citations Camel-Case, and alphabetize them. (#427)
Browse files Browse the repository at this point in the history
  • Loading branch information
@jyasskin
jyasskin authored Jan 8, 2025
1 parent c8a4709 commit dd42bb5
Showing 1 changed file with 43 additions and 49 deletions.
92 changes: 43 additions & 49 deletions index.html
View file
Original file line number Diff line number Diff line change
Expand Up @@ -125,7 +125,7 @@
}
],
localBiblio: {
'ADDING-PERMISSIONS': {
'Adding-Permissions': {
title: 'Adding another permission? A guide',
authors: ['Nick Doty'],
date: '2018',
Expand Down Expand Up @@ -173,7 +173,7 @@
href: 'https://tess.oconnor.cx/2020/10/parties',
authors: ["Tess O'Connor"],
},
'CAT': {
'Content-Aggregation-Technology': {
title: 'Content Aggregation Technology (CAT)',
authors: ['Robin Berjon', 'Justin Heideman'],
href: 'https://nytimes.github.io/std-cat/',
Expand Down Expand Up @@ -434,6 +434,17 @@
href: 'https://github.com/sleevi/psl-problems',
title: 'Public Suffix List Problems'
},
'Records-Computers-Rights': {
title: 'Records, Computers and the Rights of Citizens',
publisher: 'U.S. Department of Health, Education & Welfare',
href: 'https://archive.epic.org/privacy/hew1973report/'
},
'Relational-Governance': {
title: 'A Relational Theory of Data Governance',
authors: ['Salomé Viljoen'],
href: 'https://www.yalelawjournal.org/feature/a-relational-theory-of-data-governance',
publisher: 'Yale Law Journal',
},
'Relational-Turn': {
title: 'A Relational Turn for Data Protection?',
href: 'https://papers.ssrn.com/sol3/papers.cfm?abstract_id=3745973&s=09',
Expand All @@ -444,12 +455,6 @@
href: 'https://bookshop.org/books/seeing-like-a-state-how-certain-schemes-to-improve-the-human-condition-have-failed/9780300246759',
authors: ['James C. Scott'],
},
'SILVERPUSH': {
title: 'How TV ads silently ping commands to phones: Sneaky SilverPush code reverse-engineered',
href: 'https://www.theregister.com/2015/11/20/silverpush_soundwave_ad_tracker/',
publisher: 'The Register',
authors: ['Iain Thomson']
},
'Strava-Debacle': {
title: 'The Latest Data Privacy Debacle',
authors: ['Zeynep Tufekci'],
Expand Down Expand Up @@ -494,29 +499,18 @@
href: 'https://www.hup.harvard.edu/catalog.php?isbn=9780674035072',
publisher: 'Harvard University Press',
},
'Web-Without-3p-Cookies': {
title: 'Improving the web without third-party cookies',
authors: ['Amy Guy'],
href: 'https://www.w3.org/2001/tag/doc/web-without-3p-cookies/',
publisher: 'W3C',
},
'Why-Privacy': {
title: 'Why Privacy Matter',
authors: ['Neil Richards'],
href: 'https://global.oup.com/academic/product/why-privacy-matters-9780190939045?cc=us&lang=en&',
publisher: 'Oxford University Press',
},
'Records-Computers-Rights': {
title: 'Records, Computers and the Rights of Citizens',
publisher: 'U.S. Department of Health, Education & Welfare',
href: 'https://archive.epic.org/privacy/hew1973report/'
},
'Relational-Governance': {
title: 'A Relational Theory of Data Governance',
authors: ['Salomé Viljoen'],
href: 'https://www.yalelawjournal.org/feature/a-relational-theory-of-data-governance',
publisher: 'Yale Law Journal',
},
'web-without-3p-cookies': {
title: 'Improving the web without third-party cookies',
authors: ['Amy Guy'],
href: 'https://www.w3.org/2001/tag/doc/web-without-3p-cookies/',
publisher: 'W3C',
},
},
};
</script>
Expand Down Expand Up @@ -562,7 +556,7 @@
#bp-summary ul:has(#include-api-designers:checked) + ul li:has(.audience-api-designers) { display: list-item; }
</style>
</head>
<body data-cite="html indexedDB service-workers fingerprinting-guidance url infra">
<body data-cite="HTML IndexedDB Service-Workers Fingerprinting-Guidance URL Infra">

<section id="abstract">

Expand Down Expand Up @@ -594,8 +588,8 @@

## How This Document Fits In

This document elaborates on the <a data-cite="ethical-web-principles#privacy">privacy principle</a>
from the [[[ethical-web-principles]]]: "Security and privacy are essential." While it focuses on privacy, this should
This document elaborates on the <a data-cite="Ethical-Web-Principles#privacy">privacy principle</a>
from the [[[Ethical-Web-Principles]]]: "Security and privacy are essential." While it focuses on privacy, this should
not be taken as an indication that privacy is always more important than other ethical web principles, and
this document doesn't address how to balance the different ethical web principles if they come into conflict.

Expand Down Expand Up @@ -674,7 +668,7 @@
information flows.

The web is for everyone ([[?For-Everyone]]). It should be "<i>a platform that helps people and provides a
net positive social benefit</i>" ([[?ethical-web-principles]]). One of the ways in which the
net positive social benefit</i>" ([[?Ethical-Web-Principles]]). One of the ways in which the
web serves people is by seeking to protect them from surveillance and the types of manipulation that data can
enable.

Expand Down Expand Up @@ -715,7 +709,7 @@
There are <em>always</em> privacy principles at work. Some sets of principles may be more
permissive, but that does not make them neutral. All privacy principles have an impact on
[=people=] and we must therefore determine which principles best align with ethical web values in
web [=contexts=] ([[?ethical-web-principles]], [[?Why-Privacy]]).
web [=contexts=] ([[?Ethical-Web-Principles]], [[?Why-Privacy]]).

<dfn>Information flows</dfn> are information exchanged or processed by
[=actors=]. A person's privacy can be harmed both by their information flowing from them to
Expand Down Expand Up @@ -798,7 +792,7 @@
instance, the [=person=] may be objecting to [=processing=] based on legitimate interest,
withdrawing [=consent=] to specific [=purposes=], or requesting that their data not be sold or
shared.) The [=user=] is effectively delegating the expression of their [=opt-out=] to their
[=user agent=], which helps rectify [=automation asymmetry=]. The [[[?gpc-spec]]] is a good
[=user agent=], which helps rectify [=automation asymmetry=]. The [[[?GPC-Spec]]] is a good
example of a [=global opt-out=] mechanism.

Under this model, a [=global opt-out=] signal should not be understood as a decision that a
Expand Down Expand Up @@ -843,7 +837,7 @@
businesses operating in a competitive environment. They also do not consider cases in
which one [=actor=] may coerce other [=actors=] into facilitating its [=inappropriate=]
practices, as is often the case with dominant players in advertising or in content aggregation
([[?Consent-Lackeys]], [[?CAT]]).
([[?Consent-Lackeys]], [[?Content-Aggregation-Technology]]).

Reference to the [=FIPs=] survives to this day. They are often referenced as "<i>transparency
and choice</i>", which, in today's digital environment, is often an indication that
Expand Down Expand Up @@ -1114,10 +1108,10 @@
Once one is choosing between different designs at the Pareto frontier, the choice of which
privacy principles to prefer is complex and depends heavily on the details of each
particular situation. Note that people's privacy can also be in tension
with non-privacy concerns. As discussed in the [[[ethical-web-principles]]], "it is important to
with non-privacy concerns. As discussed in the [[[Ethical-Web-Principles]]], "it is important to
consider the context in which a particular technology is being applied, the expected
audience(s) for the technology, who the technology benefits and who it may disadvantage,
and any power dynamics involved" ([[ethical-web-principles]]). Despite this complexity, there is a basic ground
and any power dynamics involved" ([[Ethical-Web-Principles]]). Despite this complexity, there is a basic ground
rule to follow:

<div class="practice" data-audiences="websites user-agents">
Expand Down Expand Up @@ -1315,27 +1309,27 @@
<dt><dfn>Non-ancillary APIs</dfn></dt>
<dd>
Web APIs that were designed to support users' immediate goals, like <a
data-cite="dom#interface-event">DOM events</a> and <a
data-cite="cssom-view-1#extension-to-the-element-interface">element position
data-cite="DOM#interface-event">DOM events</a> and <a
data-cite="CSSOM-View-1#extension-to-the-element-interface">element position
observers</a>.
</dd>

<dt><dfn>Ancillary APIs computed from existing information</dfn></dt>
<dd>
APIs that filter, summarize, or time-shift information available from
[=non-ancillary APIs=], like the [[[event-timing]]] and <a
data-cite="intersection-observer#introduction">IntersectionObserver</a>. See
[=non-ancillary APIs=], like the [[[Event-Timing]]] and <a
data-cite="Intersection-Observer#introduction">IntersectionObserver</a>. See
[[[#information]]] for restrictions on how existing non-ancillary APIs can
be used to justify new ancillary APIs.
</dd>

<dt><dfn>Ancillary APIs that provide new information</dfn></dt>
<dd>
APIs that provide new information that's primarily useful to support the
ancillary uses, like <a data-cite="element-timing#sec-intro">element paint
timing</a>, <a data-cite="performance-measure-memory#intro">memory usage
ancillary uses, like <a data-cite="Element-Timing#sec-intro">element paint
timing</a>, <a data-cite="Performance-Measure-Memory#intro">memory usage
measurements</a>, and <a
data-cite="deprecation-reporting#deprecation-report">deprecation
data-cite="Deprecation-Reporting#deprecation-report">deprecation
reports</a>.
</dd>
</dl>
Expand Down Expand Up @@ -1519,11 +1513,11 @@

<aside class="example">
Usually, these APIs will be designed to expose data that enables some
[=appropriate=] information discovery, as recommended by [[[web-without-3p-cookies]]]:
[=appropriate=] information discovery, as recommended by [[[Web-Without-3p-Cookies]]]:

> It is better to approach [these use cases] with replacement technologies
that are designed-for-purpose and built to respect user privacy.
[[?web-without-3p-cookies]]
[[?Web-Without-3p-Cookies]]

For example, they might reveal a performance metric for a website directly
instead of requiring it to be computed from the timing of
Expand Down Expand Up @@ -1797,7 +1791,7 @@
1. [=User agent=] developers need to consider whether requests from [=device owners=] and
[=administrators=] are reasonable, and refuse to implement unreasonable requests, even if that
means fewer sales. Owner/administrator needs do not supersede user needs in the <a
data-cite="design-principles#priority-of-constituencies">priority of constituencies</a>.
data-cite="Design-Principles#priority-of-constituencies">priority of constituencies</a>.
1. Even when information disclosure is reasonable, the [=person=] whose data is being disclosed
needs to know about it so that they can avoid doing things that would lead to unwanted
consequences.
Expand Down Expand Up @@ -1907,7 +1901,7 @@
Features that are designed-for-purpose facilitate these principles by providing functionality that is only or primarily
useful for a particular purpose. Designed-for-purpose features make it easier to explain the purpose to people, and may
also limit the feasible secondary uses of data. When building a designed-for-purpose feature,
<a data-cite="design-principles#high-level-low-level">consider tradeoffs between high and low-level
<a data-cite="Design-Principles#high-level-low-level">consider tradeoffs between high and low-level
APIs</a>.

[=Controlled de-identified data=] may be used for additional purposes in ways that are compatible with the specified
Expand All @@ -1930,7 +1924,7 @@

<div class="note">
In designing new web features that may involve permissions, consider whether a permission is
needed and how to make that permission meaningful [[?ADDING-PERMISSIONS]].
needed and how to make that permission meaningful [[?Adding-Permissions]].

Past workshops have explored the needs for better permissions on the web:
<ul>
Expand Down Expand Up @@ -1970,7 +1964,7 @@
</div>

Non-transparent methods of [=recognition=] are harmful in part because they are not visible to the
user, which undermines user control [[?UNSANCTIONED-TRACKING]]. Designing features that minimize
user, which undermines user control [[?Unsanctioned-Tracking]]. Designing features that minimize
data and make requests for data explicit can enable detectability, a kind of transparency that is an
important mitigation for <a>browser fingerprinting</a>.

Expand Down Expand Up @@ -2386,7 +2380,7 @@

If a [=user agent=] can tell that its user is using a particular identity on a
website, it should make that active identity clear to the user (e.g. if the
user logged into the site via an API like [[[credential-management-1]]]).
user logged into the site via an API like [[[Credential-Management-1]]]).

</section>

Expand All @@ -2409,7 +2403,7 @@
# Acknowledgements {#acknowledgements}

Some of the definitions in this document build on top of the work in
[[[tracking-dnt]]].
[[[Tracking-DNT]]].

The following people, in alphabetical order of their first name, were instrumental
in producing this document and made invaluable contributions:
Expand Down

0 comments on commit dd42bb5

Please sign in to comment.