Re: Conventions for composed words in enum

> On Tue, Oct 22, 2013 at 8:29 AM, Harald Alvestrand < <>> wrote:
> > On 10/21/2013 02:57 PM, Anne van Kesteren wrote:
> >> Yeah, lowercase, no separators.
> >>
> > not to be a pain, but why is the answer here "lowercase" and not "camelCase"
> > or "CamelCase"?
> >
> > trying to understand why this case (identifiers represented as strings) is
> > different from other identifiers.
> Just ended up being the convention we use. This is also the convention
> we use for HTML element and attribute names, for what it's worth. It's
> not completely unique.
> Is "lowercasewords" still the preferred style? Would it be possible to add
naming guidelines to Absent any
other guidance, the current note implies use of dashes. says nothing about naming.

FYI, here are a couple counterexamples in active specs:

   - Fetch is using a mix of concatenation and dashes:
   - Screen Orientation is using dashes:

Received on Wednesday, 12 November 2014 18:31:05 UTC