Merge branch 'master' into alice-tess-149

index.bs

@@ -4,9 +4,9 @@ Group: W3C TAG
 Shortname: design-principles
 Repository: w3ctag/design-principles
 Status: DREAM
-Editor: Travis Leithead, Microsoft, travil@microsoft.com
 Editor: Sangwhan Moon, Invited Expert, https://sangwhan.com
 Former Editor: Domenic Denicola, Google https://www.google.com/, https://domenic.me/, d@domenic.me
+Former Editor: Travis Leithead, Microsoft, travil@microsoft.com
 Abstract: This document contains a small-but-growing set of design principles collected by the W3C TAG while <a href="https://github.com/w3ctag/spec-reviews/">reviewing</a> specifications.
 Default Biblio Status: current
 Markup Shorthands: markdown on
@@ -171,6 +171,13 @@ Names take meaning from:
 * use (how people come to understand the name over time)
 * context (the object on the left-hand side, for example)
 
+API naming *must* be done in easily readable US English. For example `horizontalAlignment` 
+is a more English-readable name than `alignmentHorizontal`. Whenever possible consider 
+readability over brevity.
+
+Names should adhere to the local language restrictions, for example CSS ident rules etc. 
+and *should* be in the [ASCII range](https://infra.spec.whatwg.org/#ascii-code-point).
+
 <h4 id="naming-consistency" class="no-num no-toc">Consistency</h4>
 Naming schemes should aim for consistency, to avoid confusion.