W3C home > Mailing lists > Public > public-script-coord@w3.org > October to December 2013

Re: Conventions for composed words in enum

From: Anne van Kesteren <annevk@annevk.nl>
Date: Tue, 22 Oct 2013 11:13:11 +0100
Message-ID: <CADnb78gKPEpzkUcp4rj-Nxhitr=efjEFHkik7+uxdANHhGEUcA@mail.gmail.com>
To: Harald Alvestrand <harald@alvestrand.no>
Cc: Dominique Hazael-Massieux <dom@w3.org>, "public-script-coord@w3.org" <public-script-coord@w3.org>, Stefan HÃ¥kansson LK <stefan.lk.hakansson@ericsson.com>
On Tue, Oct 22, 2013 at 8:29 AM, Harald Alvestrand <harald@alvestrand.no> 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.

Received on Tuesday, 22 October 2013 10:13:39 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:14:18 UTC