Skip to content

Commit 278da73

Browse files
csarvenmartinthomsonjyasskinmarcoscaceres
authored
Add Criteria for Design Principles to README (#575)
* Add Criteria section to the Design Principles README Resolves: #572 * Update README.md Co-authored-by: Martin Thomson <[email protected]> * Apply suggestions from code review Co-authored-by: Martin Thomson <[email protected]> * Mention aligned with EWP re value/priority * Apply suggestions from code review * Apply suggestions from code review Co-authored-by: Martin Thomson <[email protected]> Co-authored-by: Martin Thomson <[email protected]> * Apply suggestions from code review Co-authored-by: Jeffrey Yasskin <[email protected]> * Apply suggestions from code review * Can't e.g. and etc. on the same thing * Line breaking hygiene --------- Co-authored-by: Martin Thomson <[email protected]> Co-authored-by: Jeffrey Yasskin <[email protected]> Co-authored-by: Marcos Cáceres <[email protected]>
1 parent 8f1b24f commit 278da73

File tree

1 file changed

+16
-0
lines changed

1 file changed

+16
-0
lines changed

README.md

Lines changed: 16 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,23 @@ With those dependencies, simply invoke `make` to build the document.
1414

1515
Contributions are welcome to anyone who follows [our code of conduct](https://www.w3.org/Consortium/cepc/).
1616

17+
When proposing new principles or updating existing ones, please take the [criteria](#criteria) into consideration.
1718
The editors will merge PRs after they have TAG consensus and will attempt to document that consensus
1819
by linking to the meeting minutes. If you notice a change that seems to have been merged without
1920
consensus, please comment on its PR or file an issue, and we'll either quickly find better evidence
2021
or back out the change until we can discuss it more fully.
22+
23+
24+
## Criteria
25+
26+
These criteria support consistent evaluation of proposed principles.
27+
They are not strict rules and may not all apply in every case.
28+
Principles should be:
29+
30+
* Grounded in patterns from specs, implementations, or real-world web use.
31+
* Evidence-based.
32+
* Generalisable across multiple technologies and use cases, persistent over time.
33+
* Informed by community practices, standards, or observed usage.
34+
* Guided by a clear value or priority, e.g., prefer simplicity, preserve individual/user agency.
35+
* Compatible with established principles and guidelines,
36+
e.g., [Privacy Principles](https://www.w3.org/TR/privacy-principles/) or [Ethical Web Principles](https://www.w3.org/TR/ethical-web-principles/).

0 commit comments

Comments
 (0)