Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
Received-SPF: pass (nike.apache.org: domain of julian.goacher@gmail.com
 designates 72.14.220.158 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:date:message-id:subject:from:to:content-type;
        b=GoBz2cYEaGWJXiw5r+t7KMI+cKyHnCsFHm/UaaB1gvCOrgbVynIRm9JclbNXri5cas
         zubVEVA68eq1aviYOiOEIk+9wUmTUkcyj248mk4yCfsPEvipXwtJxFzvFAlJz4h8ZnIL
         WV39+NFpzGlXzm18uL9cMuHLtNmHwYRRcrskI=
MIME-Version: 1.0
Date: Thu, 29 Oct 2009 22:47:20 +0000
Message-ID: <3f1568830910291547ldc358e3s30bf07c6c9ad954c@mail.gmail.com>
Subject: Proposal regarding reserved names
From: Julian Goacher <julian.goacher@gmail.com>
To: user@couchdb.apache.org
Content-Type: multipart/alternative; boundary=001485ede4ffb17f0904771ab168

--001485ede4ffb17f0904771ab168
Content-Type: text/plain; charset=ISO-8859-1

Hello,

With respect to http://wiki.apache.org/couchdb/Reserved_words: I'm a
developer currently writing an application framework layered over couchdb.
The framework needs to annotate  user documents with additional state
information. Prior to recent releases, my framework used property names
beginning with an underscore to store these annotations (following the
convention that such names are separate from the user data). As things
stand, this is no longer possible, but I was wondering if the couchdb dev
team would consider allocating a specific property name - e.g. something
like _meta - specifically for this use case. The idea would be that the
property could then be used by third party developers to house any values
considered orthogonal to the document data.

Example:

{
    "_meta":{
        "plink_framework_property_a": 23,
        "plink_framework_property_b": "2009-10-29T00:00:00Z"
    }
}


Regards,

/julian

--001485ede4ffb17f0904771ab168--