Return-Path: Delivered-To: apmail-couchdb-user-archive@www.apache.org Received: (qmail 64843 invoked from network); 25 Mar 2011 12:28:18 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 25 Mar 2011 12:28:18 -0000 Received: (qmail 79051 invoked by uid 500); 25 Mar 2011 12:28:16 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 79010 invoked by uid 500); 25 Mar 2011 12:28:16 -0000 Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@couchdb.apache.org Delivered-To: mailing list user@couchdb.apache.org Received: (qmail 79002 invoked by uid 99); 25 Mar 2011 12:28:16 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 25 Mar 2011 12:28:16 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of n.teofilov@gmail.com designates 209.85.214.52 as permitted sender) Received: from [209.85.214.52] (HELO mail-bw0-f52.google.com) (209.85.214.52) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 25 Mar 2011 12:28:09 +0000 Received: by bwj24 with SMTP id 24so1365286bwj.11 for ; Fri, 25 Mar 2011 05:27:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:content-type:mime-version:subject:from :in-reply-to:date:content-transfer-encoding:message-id:references:to :x-mailer; bh=P2WSzQhr81gN/YPkiW8eBrCeG/t4/LKK9JEEe/5KyKY=; b=cGIT/PLy1N+NjVdrOTv6u4IWA/AEWKwodKEBJYda71sTbL5gxjEUDNX9Bc53md2jr6 nKK5erKLf5CP9J97TxYE/Cz1eepWZSGYjF4T61u5YEWUIX4eNSBs+HkeIy4MWORvHVIh xQx/XgPyovMAGbNpl/jPry6ViYbCe15VOMuPU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=content-type:mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to:x-mailer; b=pJK7yBGQE4HdPCkGKcdemKzScDNBqMSvhnyZkmZj7Tr0eYCfNmuWeJP79lzzT07YD+ 1F5hqGKA8KPSgCo/TKZMyvWxU3cJIvvwEwPeYAlM2HIUsMI2xWYuPGee7Y+vWoSpOS3f qhYMCCwiunJu0H6Bx2RfEJv6ZRi6aUL3ldilY= Received: by 10.204.188.65 with SMTP id cz1mr721745bkb.108.1301056067836; Fri, 25 Mar 2011 05:27:47 -0700 (PDT) Received: from [192.168.178.109] (p5DDAAC74.dip.t-dialin.net [93.218.172.116]) by mx.google.com with ESMTPS id y9sm135001faj.0.2011.03.25.05.27.46 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 25 Mar 2011 05:27:47 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Apple Message framework v1084) Subject: Re: JSON style question From: Nikolai Teofilov In-Reply-To: Date: Fri, 25 Mar 2011 13:27:45 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: <023D3FB2-E891-4336-901C-11CE9A2D6EF8@gmail.com> References: To: user@couchdb.apache.org X-Mailer: Apple Mail (2.1084) This is only example field name in a JSON structure with two words. I = wanted to know if there is a kind of common style for such long fields = in a document? On 25.03.2011, at 13:09, Benoit Chesneau wrote: > On Fri, Mar 25, 2011 at 12:15 PM, Nikolai Teofilov = wrote: >> What is the best or common style for field names in the JSON = documents? >>=20 >> For example Quantum Efficiency: >>=20 >> 1. QuantumEfficiency >> 2. quantumEfficiency >> 3. quantum_efficiency >> 4. quantumefficiency >>=20 >>=20 >>=20 >>=20 >=20 > quantum/efficiency ?