Update ethical-web-principles links and bibrefs (#601)

Author: csarven

index.bs

@@ -14,7 +14,7 @@ Former Editor: Lea Verou, Invited Expert, https://lea.verou.me, w3cid 52258
 Former Editor: Sangwhan Moon, w3cid 42399, Google https://www.google.com/, https://sangwhan.com
 Former Editor: Domenic Denicola, Google https://www.google.com/, https://domenic.me/, [email protected]
 Former Editor: Travis Leithead, Microsoft, [email protected]
-Abstract: This document contains a set of design principles to be used when designing web platform technologies. These principles have been collected during the Technical Architecture Group's discussions in <a href="https://github.com/w3ctag/design-reviews/">reviewing</a> developing specifications, and build upon the Ethical Web Principles [[ETHICAL-WEB]]. We encourage specification designers to read this document and use it as a resource when making design decisions.
+Abstract: This document contains a set of design principles to be used when designing web platform technologies. These principles have been collected during the Technical Architecture Group's discussions in <a href="https://github.com/w3ctag/design-reviews/">reviewing</a> developing specifications, and build upon the Ethical Web Principles [[ethical-web-principles]]. We encourage specification designers to read this document and use it as a resource when making design decisions.
 Default Biblio Status: current
 Markup Shorthands: markdown on
 Boilerplate: feedback-header off
@@ -53,7 +53,7 @@ urlPrefix: https://www.rfc-editor.org/rfc/rfc9110.html; spec: rfc9110
 <h2 id="basic-principles">Principles behind design of Web APIs</h2>
 
 The Design Principles are directly informed by the ethical framework
-set out in the Ethical Web Principles [[ETHICAL-WEB]].
+set out in the Ethical Web Principles [[ethical-web-principles]].
 These principles provide concrete practical advice
 in response to the higher level ethical responsibilities
 that come with developing the web platform.
@@ -68,7 +68,7 @@ be sure to understand and document the user need that the API aims to address.
 
 [The internet is for end users](https://tools.ietf.org/html/rfc8890):
 any change made to the web platform has the potential to
-[affect vast numbers of people](https://www.w3.org/2001/tag/doc/ethical-web-principles/#allpeople),
+[affect vast numbers of people](https://www.w3.org/TR/ethical-web-principles/#allpeople),
 and may have a profound impact on any person's life. [[RFC8890]]
 
 User needs come before the needs of web page authors,
@@ -86,8 +86,8 @@ and theoretical concerns reflect underlying needs of all of these groups.
 
 See also:
 
-* [The web should not cause harm to society](https://www.w3.org/2001/tag/doc/ethical-web-principles/#noharm)
-* [The web must enhance individuals' control and power](https://www.w3.org/2001/tag/doc/ethical-web-principles/#control)
+* [The web should not cause harm to society](https://www.w3.org/TR/ethical-web-principles/#noharm)
+* [The web must enhance individuals' control and power](https://www.w3.org/TR/ethical-web-principles/#control)
 * [[RFC8890]]
 
 <h3 id="safe-to-browse">It should be safe to visit a web page</h3>
@@ -100,7 +100,7 @@ The Web is named for its hyperlinked structure.
 In order for the web to remain vibrant,
 users need to be able to expect that merely visiting any given link
 won't have implications for the security of their computer,
-or for any essential aspects of their [privacy](https://www.w3.org/2001/tag/doc/ethical-web-principles/#privacy).
+or for any essential aspects of their [privacy](https://www.w3.org/TR/ethical-web-principles/#privacy).
 
 For example, an API that allows any website to
 [detect the use of assistive technologies](#do-not-expose-use-of-assistive-tech)
@@ -143,7 +143,7 @@ Users depend on trusted user interfaces
 such as the address bar, security indicators and permission prompts,
 to understand who they are interacting with and how.
 These trusted user interfaces must be able to be designed in a way
-that enables users to trust [and verify](https://www.w3.org/2001/tag/doc/ethical-web-principles/#verify)
+that enables users to trust [and verify](https://www.w3.org/TR/ethical-web-principles/#verify)
 that the information they provide is genuine,
 and hasn't been spoofed or hijacked by the website.
 
@@ -163,7 +163,7 @@ In the context of fulfilling a user need,
 a web page may want to make use of a feature
 that has the potential to cause harm.
 Features that have this potential for harm should be designed such that people can give
-[meaningful consent](https://www.w3.org/2001/tag/doc/ethical-web-principles/#control) for that feature to be used,
+[meaningful consent](https://www.w3.org/TR/ethical-web-principles/#control) for that feature to be used,
 and that they can refuse consent effectively.
 
 In order to give *meaningful consent*, the user must:
@@ -210,7 +210,7 @@ no location information is available to the Web page.
 
 See also:
 
-* [The web is secure, and respects people's privacy](https://www.w3.org/2001/tag/doc/ethical-web-principles/#privacy)
+* [The web is secure, and respects people's privacy](https://www.w3.org/TR/ethical-web-principles/#privacy)
 * [Consent Principles](https://www.w3.org/TR/privacy-principles/#consent-principles)
 * [Permissions](https://www.w3.org/TR/permissions/)
 
@@ -258,7 +258,7 @@ a Web page may be viewed on virtually any consumer computing device
 at a very wide range of screen sizes,
 may be used to generate printed media,
 and may be interacted with in a large number of different ways.
-New features should match the [existing flexibility](https://www.w3.org/2001/tag/doc/ethical-web-principles/#render)
+New features should match the [existing flexibility](https://www.w3.org/TR/ethical-web-principles/#render)
 of the web platform.
 
 <div class="note">
@@ -719,10 +719,10 @@ Some people use [private browsing mode](https://www.w3.org/2001/tag/doc/private-
 to protect their own personal safety.
 Because of this, the fact that someone is using private browsing mode
 may be [sensitive information](https://www.w3.org/TR/security-privacy-questionnaire/#sensitive-data) about them.
-This information may [harm](https://www.w3.org/2001/tag/doc/ethical-web-principles/#noharm) people
+This information may [harm](https://www.w3.org/TR/ethical-web-principles/#noharm) people
 if it is revealed to a web site controlled by others who have power over them
 (such as employers, parents, partners,
-or [state actors](https://www.w3.org/2001/tag/doc/ethical-web-principles/#expression)).
+or [state actors](https://www.w3.org/TR/ethical-web-principles/#expression)).
 
 Given such dangers,
 websites should not be able to detect that private browsing mode is engaged.
@@ -750,7 +750,7 @@ without revealing that private browsing mode is engaged.
 
 See also:
 
-* [Security and privacy are essential](https://www.w3.org/2001/tag/doc/ethical-web-principles/#privacy)
+* [Security and privacy are essential](https://www.w3.org/TR/ethical-web-principles/#privacy)
 * [What data does this specification expose to an origin?](https://www.w3.org/TR/security-privacy-questionnaire/#underlying-platform-data)
 * [[#private-browsing-mode]]
 
@@ -803,16 +803,16 @@ See also:
 Make sure that your API doesn't provide a way
 for authors to detect that a user is using assistive technology.
 
-[The web platform must be accessible to people with disabilities.](https://www.w3.org/2001/tag/doc/ethical-web-principles/#allpeople)
+[The web platform must be accessible to people with disabilities.](https://www.w3.org/TR/ethical-web-principles/#allpeople)
 If a site can detect that a user is using an assistive technology,
 that site can deny or restrict the user's access to the services it provides.
 
 People who make use of assistive technologies
-are often [vulnerable members of society](https://www.w3.org/2001/tag/doc/ethical-web-principles/#noharm);
+are often [vulnerable members of society](https://www.w3.org/TR/ethical-web-principles/#noharm);
 their use of assistive technologies is [sensitive information](https://www.w3.org/TR/security-privacy-questionnaire/#sensitive-data) about them.
 If an API provides access to this information,
 this sensitive information may be revealed to others
-(including [state actors](https://www.w3.org/2001/tag/doc/ethical-web-principles/#expression))
+(including [state actors](https://www.w3.org/TR/ethical-web-principles/#expression))
 who may wish them harm.
 
 Sometimes people propose features which aim to improve the user experience
@@ -837,7 +837,7 @@ which don't reveal the use of assistive technology.
 See also:
 
 * [Web Technology Accessibility Guidelines](https://w3c.github.io/apa/fast/)
-* [Security and privacy are essential](https://www.w3.org/2001/tag/doc/ethical-web-principles/#privacy)
+* [Security and privacy are essential](https://www.w3.org/TR/ethical-web-principles/#privacy)
 * [What data does this specification expose to an origin?](https://www.w3.org/TR/security-privacy-questionnaire/#underlying-platform-data)
 
 <h3 id="require-user-activation">Require user activation for powerful APIs</h3>
@@ -3206,7 +3206,7 @@ the user experience will suffer.
 (This problem is even more pronounced on low-powered devices,
 which are more likely to be used by disadvantaged or marginalized users.
 Remember,
-[the web is for all people](https://www.w3.org/2001/tag/doc/ethical-web-principles/#allpeople).)
+[the web is for all people](https://www.w3.org/TR/ethical-web-principles/#allpeople).)
 
 Therefore,
 APIs which would often block the main thread if used as intended