- From: Doug Schepers <schepers@w3.org>
- Date: Wed, 24 Jun 2015 03:25:55 -0400
- To: Ivan Herman <ivan@w3.org>
- CC: Robert Sanderson <azaroth42@gmail.com>, Jacob Jett <jjett2@illinois.edu>, Frederick Hirsch <w3c@fjhirsch.com>, W3C Public Annotation List <public-annotation@w3.org>
Hi, Ivan– On 6/23/15 3:12 AM, Ivan Herman wrote: >> On 23 Jun 2015, at 05:04 , Doug Schepers <schepers@w3.org> wrote: >> On 6/22/15 6:24 PM, Robert Sanderson wrote: >>> >>> Unless case insensitivity is a goal, >> >> I think we should try for case insensitivity as a goal. Case >> sensitivity proved to be one of the most frustrating, hard-to-debug >> aspects of XML; I know it's bitten many people coding SVG, for >> example. > > Doesn't JSON have case sensitivity? If so, we should decide once and > for all for the style we use? > > Alternatively, we can include, in the @context, mapping of several > formats to the same term (ie, @context can be many-to-one, afaik). > But I am not sure I like that… Sorry, I wasn't clear (I was sleepy when I wrote that email)… Yes, JSON is case-sensitive. What I meant to say is that we shouldn't use mixed-case, because it's hard for people to remember which case to use for any given key or value. Thus, I think we should all lower-case for these names. Further, I agree with Randall's suggestion [1] that we use snake_case [2] (and specifically, spinal_case, which is the all-lower-case variant of snake_case). I think Randall makes excellent points regarding its benefits and widespread adoption (which will make it more familiar to developers). [1] https://github.com/w3c/web-annotation/issues/12#issuecomment-59282459 [2] https://en.wikipedia.org/wiki/Snake_case Regards– –Doug
Received on Wednesday, 24 June 2015 07:26:01 UTC