Return-Path: X-Original-To: apmail-couchdb-user-archive@www.apache.org Delivered-To: apmail-couchdb-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 910AD99BA for ; Mon, 9 Apr 2012 14:42:18 +0000 (UTC) Received: (qmail 39277 invoked by uid 500); 9 Apr 2012 14:42:17 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 39227 invoked by uid 500); 9 Apr 2012 14:42:17 -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 39217 invoked by uid 99); 9 Apr 2012 14:42:16 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 09 Apr 2012 14:42:16 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of jeroen.janssen@gmail.com designates 209.85.160.180 as permitted sender) Received: from [209.85.160.180] (HELO mail-gy0-f180.google.com) (209.85.160.180) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 09 Apr 2012 14:42:12 +0000 Received: by ghbz12 with SMTP id z12so2210390ghb.11 for ; Mon, 09 Apr 2012 07:41:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; bh=Mq5RyROftmEQdU8+nFbWOC1gQWv3qG8aS58hj+Mpu3o=; b=MeHeVbTN4trzye+1wkN1A9sKOAwS9F1r6PSDFemM2NB7M1Hdj810JxN6ozpy7Huilj SlsYqLy+t/pHfgOioRYSdx+SLjutt251aVEV7pOrosrqJWS5DFubHn6j9aTURPLZQh/l Qg9/9lUEnGsWRN8BY9TMwP6VuqjNrYgRzV+/EPQR4QGzmnUnp9F6zkFQX9XIfC7XWGHb uD93xUeD2v9tjDrSf90/dgMPTvvXezIKGsS5AFizi0ZIGzpstfsGzLFfDDwX/BoMkzc8 aAq9CrfzyqsA/2YH2hCRJFnHfw/JWSnfSHZKxHcHJQ39xWgNcyqwRMIoKIwh8OZld1CE kXdA== MIME-Version: 1.0 Received: by 10.236.147.19 with SMTP id s19mr6131453yhj.36.1333982511746; Mon, 09 Apr 2012 07:41:51 -0700 (PDT) Received: by 10.101.207.31 with HTTP; Mon, 9 Apr 2012 07:41:51 -0700 (PDT) In-Reply-To: <4F82F378.1040709@gmail.com> References: <4F82F378.1040709@gmail.com> Date: Mon, 9 Apr 2012 16:41:51 +0200 Message-ID: Subject: Re: formal database schema? From: Jeroen Janssen To: user@couchdb.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org Hi, Not sure if this is what you are looking for, but there is a draft JSON schema specification at http://json-schema.org/ which is "a JSON based format for defining the structure of JSON data". Best regards, Jeroen On Mon, Apr 9, 2012 at 4:34 PM, Kevin R. Coombes wrote: > Hi, > > We just had a manuscript that describes three applications of CouchDB in > bioinformatics =A0accepted with minor revisions. =A0(I think this will be= the > first paper describing a CouchDB application in the area of bioinformatic= s.) > > One of the requested minor changes is for "schematics, data models, etc". > =A0I'm sure that the reviewer is thinking about the kinds of schema diagr= ams > that can easily be supplied for a relational database. =A0Other than a ta= ble > or a screenshot showing the reviewer what a typical document looks like i= n > these databases, does anyone know of equivalent tools or diagrams to > describe a document-oriented database? Are there any (formal) design or > document conventions that have evolved or are evolving for describing > databases built using Couch? > > =A0 =A0Kevin > > In case anyone wants to take a look at the applications, here are the URL= s: > > geneSmash > > =A0http://app1.bioinformatics.mdanderson.org/genesmash/_design/basic/inde= x.html > drugBase > > =A0http://app1.bioinformatics.mdanderson.org/drugbase/_design/basic/index= .html > HapMap-CN > =A0 =A0http://app1.bioinformatics.mdanderson.org/hapmap/_design/basic/ind= ex.html >