Skip to content

Commit

Permalink
deploy: 0543b70
Browse files Browse the repository at this point in the history
  • Loading branch information
@rhiaro
rhiaro committed Mar 6, 2024
1 parent 1dfd46f commit 29d204b
Showing 1 changed file with 38 additions and 14 deletions.
52 changes: 38 additions & 14 deletions index.html
View file
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@
<link href="https://www.w3.org/StyleSheets/TR/2021/W3C-ED" rel="stylesheet">
<meta content="Bikeshed version d5d58a306, updated Fri Jan 26 16:12:28 2024 -0800" name="generator">
<link href="https://www.w3.org/TR/design-principles/" rel="canonical">
<meta content="2aa21c40868fc31721c53843df6fd1a3039707b1" name="revision">
<meta content="0543b7035bf5262ab1e23236fb4153b7677c58d3" name="revision">
<style>
table.data {
text-align: left;
Expand Down Expand Up @@ -699,7 +699,7 @@
<div class="head">
<p data-fill-with="logo"><a class="logo" href="https://www.w3.org/"> <img alt="W3C" height="48" src="https://www.w3.org/StyleSheets/TR/2021/logos/W3C" width="72"> </a> </p>
<h1 class="p-name no-ref" id="title">Web Platform Design Principles</h1>
<p id="w3c-state"><a href="https://www.w3.org/standards/types#ED">Editor’s Draft</a>, <time class="dt-updated" datetime="2024-03-05">5 March 2024</time></p>
<p id="w3c-state"><a href="https://www.w3.org/standards/types#ED">Editor’s Draft</a>, <time class="dt-updated" datetime="2024-03-06">6 March 2024</time></p>
<details open>
<summary>More details about this document</summary>
<div data-fill-with="spec-metadata">
Expand Down Expand Up @@ -759,11 +759,12 @@ <h2 class="no-num no-toc no-ref" id="contents">Table of Contents</h2>
<li><a href="#safe-to-browse"><span class="secno">1.2</span> <span class="content">It should be safe to visit a web page</span></a>
<li><a href="#trusted-ui"><span class="secno">1.3</span> <span class="content">Trusted user interface should be trustworthy</span></a>
<li><a href="#consent"><span class="secno">1.4</span> <span class="content">Ask users for meaningful consent</span></a>
<li><a href="#devices-platforms"><span class="secno">1.5</span> <span class="content">Support the full range of devices and platforms (Media Independence)</span></a>
<li><a href="#new-features"><span class="secno">1.6</span> <span class="content">Add new capabilities with care</span></a>
<li><a href="#removing-features"><span class="secno">1.7</span> <span class="content">Remove or change capabilities only once you understand existing usage</span></a>
<li><a href="#leave-the-web-better"><span class="secno">1.8</span> <span class="content">Leave the web better than you found it</span></a>
<li><a href="#data-minimization"><span class="secno">1.9</span> <span class="content">Minimize user data</span></a>
<li><a href="#identity"><span class="secno">1.5</span> <span class="content">Use identity appropriately in context</span></a>
<li><a href="#devices-platforms"><span class="secno">1.6</span> <span class="content">Support the full range of devices and platforms (Media Independence)</span></a>
<li><a href="#new-features"><span class="secno">1.7</span> <span class="content">Add new capabilities with care</span></a>
<li><a href="#removing-features"><span class="secno">1.8</span> <span class="content">Remove or change capabilities only once you understand existing usage</span></a>
<li><a href="#leave-the-web-better"><span class="secno">1.9</span> <span class="content">Leave the web better than you found it</span></a>
<li><a href="#data-minimization"><span class="secno">1.10</span> <span class="content">Minimize user data</span></a>
</ol>
<li>
<a href="#api-across-languages"><span class="secno">2</span> <span class="content">API Design Across Languages</span></a>
Expand Down Expand Up @@ -1052,7 +1053,30 @@ <h3 class="heading settled" data-level="1.4" id="consent"><span class="secno">1.
<li data-md>
<p><a href="https://www.w3.org/2001/tag/doc/ethical-web-principles/#privacy">Security and privacy are essential</a></p>
</ul>
<h3 class="heading settled" data-level="1.5" id="devices-platforms"><span class="secno">1.5. </span><span class="content">Support the full range of devices and platforms (Media Independence)</span><a class="self-link" href="#devices-platforms"></a></h3>
<h3 class="heading settled" data-level="1.5" id="identity"><span class="secno">1.5. </span><span class="content">Use identity appropriately in context</span><a class="self-link" href="#identity"></a></h3>
<p>Give people <a href="https://www.w3.org/TR/ethical-web-principles/#control">control</a> over the identifying information about themselves
they are presenting in different contexts on the web,
and be transparent about it.</p>
<p>"Identity" is a complex concept that can be understood in many different ways.
It can refer to how someone presents or sees themselves, how they relate to other
people, groups, or institutions, and can determine how they behave
or how they are treated by others.
In web architecture, "identity" is often used as a shortcut
to refer to identifiers, and the information attached to them.</p>
<p>Features that use or depend on
identifiers and the attachment of data about a person
to that identifier carry privacy risks which
often reach beyond a single API or system.
This includes data that has been passively generated (for example,
about their behaviour on the web) as well as that which has been
actively collected (for example, they have filled in a form).</p>
<p>For such features, you should <a href="https://www.w3.org/TR/privacy-principles/#identity">understand the context</a> in which it will be used,
including how it will be used alongside other features of the web.
Make sure the user can <a href="#consent">give appropriate consent</a>.
Design APIs to collect <a href="https://www.w3.org/TR/privacy-principles/#data-minimization">the smallest amount of data</a> necessary.
Use short-lived, temporary identifiers
unless a persistent identifier is absolutely necessary.</p>
<h3 class="heading settled" data-level="1.6" id="devices-platforms"><span class="secno">1.6. </span><span class="content">Support the full range of devices and platforms (Media Independence)</span><a class="self-link" href="#devices-platforms"></a></h3>
<p>As much as possible,
ensure that features on the web work across different input and output [devices,
screen sizes, interaction modes, platforms, and media]
Expand Down Expand Up @@ -1085,19 +1109,19 @@ <h3 class="heading settled" data-level="1.5" id="devices-platforms"><span class=
In these cases, features should be designed such that it is possible for
code to gracefully fail or be polyfilled.
See <a href="#feature-detect">§ 2.5 New features should be detectable</a>.</p>
<h3 class="heading settled" data-level="1.6" id="new-features"><span class="secno">1.6. </span><span class="content">Add new capabilities with care</span><a class="self-link" href="#new-features"></a></h3>
<h3 class="heading settled" data-level="1.7" id="new-features"><span class="secno">1.7. </span><span class="content">Add new capabilities with care</span><a class="self-link" href="#new-features"></a></h3>
<p>Add new capabilities to the web with consideration of existing functionality and content.</p>
<p>The Web includes many extension points that allow for additions;
see for example <a href="https://html.spec.whatwg.org/multipage/introduction.html#extensibility"><cite>HTML</cite> § 1.7.3 Extensibility</a>.</p>
<p>Before adding items, consider integration with existing, similar capabilities.
If this leads to a preferred design approach that cannot be implemented by only adding items,
it might still be possible; see <a href="#removing-features">§ 1.7 Remove or change capabilities only once you understand existing usage</a>.</p>
it might still be possible; see <a href="#removing-features">§ 1.8 Remove or change capabilities only once you understand existing usage</a>.</p>
<p>Do not assume that a change or removal is impossible without first checking.
Before adding items, consider integration with existing, similar capabilities.
If this leads to a preferred design approach that cannot be implemented by only adding items,
it might still be possible; see <a href="#removing-features">§ 1.7 Remove or change capabilities only once you understand existing usage</a>.
it might still be possible; see <a href="#removing-features">§ 1.8 Remove or change capabilities only once you understand existing usage</a>.
Do not assume that a change or removal is impossible without first checking.</p>
<h3 class="heading settled" data-level="1.7" id="removing-features"><span class="secno">1.7. </span><span class="content">Remove or change capabilities only once you understand existing usage</span><a class="self-link" href="#removing-features"></a></h3>
<h3 class="heading settled" data-level="1.8" id="removing-features"><span class="secno">1.8. </span><span class="content">Remove or change capabilities only once you understand existing usage</span><a class="self-link" href="#removing-features"></a></h3>
<p>Prioritize compatibility with existing content when removing or changing functionality.</p>
<p>Once a significant amount of content has come to depend on a particular behavior,
removing or changing that behavior is discouraged.
Expand All @@ -1110,7 +1134,7 @@ <h3 class="heading settled" data-level="1.7" id="removing-features"><span class=
behavior that might be considered implementation bugs.
Web features are not solely defined in specifications;
they are also defined by how content uses those features.</p>
<h3 class="heading settled" data-level="1.8" id="leave-the-web-better"><span class="secno">1.8. </span><span class="content">Leave the web better than you found it</span><a class="self-link" href="#leave-the-web-better"></a></h3>
<h3 class="heading settled" data-level="1.9" id="leave-the-web-better"><span class="secno">1.9. </span><span class="content">Leave the web better than you found it</span><a class="self-link" href="#leave-the-web-better"></a></h3>
<p>As you add new capabilities to the web platform, do so in a way that improves
the overall platform, for example its security or privacy vulnerabilities, or accessibility characteristics.
The existence of a defect in one part of the platform must not be used as a license
Expand All @@ -1121,7 +1145,7 @@ <h3 class="heading settled" data-level="1.8" id="leave-the-web-better"><span cla
Issues that are present with a certain web technology now may be fixed in a subsequent iteration.
Duplicating these issues makes fixing them more difficult.
By adhering to this principle we can make sure overall platform quality improves over time.</p>
<h3 class="heading settled" data-level="1.9" id="data-minimization"><span class="secno">1.9. </span><span class="content">Minimize user data</span><a class="self-link" href="#data-minimization"></a></h3>
<h3 class="heading settled" data-level="1.10" id="data-minimization"><span class="secno">1.10. </span><span class="content">Minimize user data</span><a class="self-link" href="#data-minimization"></a></h3>
<p>Design features to work with the minimum amount of data necessary to carry out their
users' goals.</p>
<p><a href="https://www.w3.org/TR/privacy-principles/#data-minimization">Data minimization</a> limits the risks of data being inappropriately disclosed or misused.</p>
Expand Down

0 comments on commit 29d204b

Please sign in to comment.