Return-Path: Delivered-To: apmail-couchdb-user-archive@www.apache.org Received: (qmail 35645 invoked from network); 12 Apr 2011 20:09:48 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 12 Apr 2011 20:09:48 -0000 Received: (qmail 45553 invoked by uid 500); 12 Apr 2011 20:09:46 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 45516 invoked by uid 500); 12 Apr 2011 20:09:46 -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 45508 invoked by uid 99); 12 Apr 2011 20:09:46 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 12 Apr 2011 20:09:46 +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 nebupookins@gmail.com designates 209.85.161.180 as permitted sender) Received: from [209.85.161.180] (HELO mail-gx0-f180.google.com) (209.85.161.180) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 12 Apr 2011 20:09:42 +0000 Received: by gxk10 with SMTP id 10so5219066gxk.11 for ; Tue, 12 Apr 2011 13:09:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to :content-type; bh=M724Lbjp00G330X+EksB8qMApfoVi9q3kvJUAN2Bx5E=; b=Kb8ZaXloVKfJbiIUNxAwFfTjtHQuS/DKufrjJVhWUj8GbfEviHIReNLCmgiq3n3Qeq edaGy+6RW6iyNYxA6EgC6rT3QDCxd3j/nQRFQ2+222ScOmIg141Y64up/2tncxAufYVV wd/BipZpm2e11i0+VWvgYBfMbkHmgKOm8gTE8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=Llh2xjjMqV7zlQ7dyvwgh0dNdR6fba8mTgICdxRz5h3xODfwQTe1BUp7JvcS7ZV8gx NWOZl4ngx96QChly8DO9p9HqCOE7uFvnPdZ+EIk+kvPeH9d9Kd8814ihqJE28qwl08O9 xr/R0jT1vc9+Gl72MqTqYGyxFYUkQk2eZbTd4= MIME-Version: 1.0 Received: by 10.100.226.14 with SMTP id y14mr2318398ang.164.1302638961413; Tue, 12 Apr 2011 13:09:21 -0700 (PDT) Received: by 10.100.107.8 with HTTP; Tue, 12 Apr 2011 13:09:21 -0700 (PDT) Date: Tue, 12 Apr 2011 16:09:21 -0400 Message-ID: Subject: How does one validate CouchDB documents with JSON Schema? From: Nebu Pookins To: user@couchdb.apache.org Content-Type: text/plain; charset=UTF-8 If I have some JSON Schemas (http://tools.ietf.org/html/draft-zyp-json-schema-03), is there a way to pass them onto CouchDB to have CouchDB automatically ensure documents of a given type (i.e. with their "type" property set to a specific string) adhere to a specific schema file? I tried some google searches, but the closest thing I could find to information on the topic was this blog post (http://dev.wavemaker.com/forums/?q=node/2618) which implies (but does not explicitly state) that CouchDB does not support JSON Schemas at all. - Nebu