Return-Path: X-Original-To: apmail-hadoop-general-archive@minotaur.apache.org Delivered-To: apmail-hadoop-general-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 49C754B66 for ; Fri, 13 May 2011 04:49:17 +0000 (UTC) Received: (qmail 12157 invoked by uid 500); 13 May 2011 04:49:15 -0000 Delivered-To: apmail-hadoop-general-archive@hadoop.apache.org Received: (qmail 12119 invoked by uid 500); 13 May 2011 04:49:14 -0000 Mailing-List: contact general-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: general@hadoop.apache.org Delivered-To: mailing list general@hadoop.apache.org Received: (qmail 12111 invoked by uid 99); 13 May 2011 04:49:14 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 13 May 2011 04:49:14 +0000 X-ASF-Spam-Status: No, hits=-2.3 required=5.0 tests=RCVD_IN_DNSWL_MED,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of mbhandarkar@linkedin.com designates 69.28.149.25 as permitted sender) Received: from [69.28.149.25] (HELO esv4-mav03.corp.linkedin.com) (69.28.149.25) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 13 May 2011 04:49:08 +0000 DomainKey-Signature: s=prod; d=linkedin.com; c=nofws; q=dns; h=X-IronPort-AV:Received:From:To:Subject:Thread-Topic: Thread-Index:Date:Message-ID:In-Reply-To:Accept-Language: Content-Language:X-MS-Has-Attach:X-MS-TNEF-Correlator: x-originating-ip:Content-Type:Content-ID: Content-Transfer-Encoding:MIME-Version; b=rnqw7eRXfyLdHXj2sS72eelL381jlBsnXXC1WtCbGxHAJjzx8bYQhAU9 c7+R7a7J58O2Ksw5A344f1JeWg3+Y+iWONQ0b3M7GKxW1vx2lI3ndte+B 3/kCzDFCrgcwkfh; DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linkedin.com; i=mbhandarkar@linkedin.com; q=dns/txt; s=proddkim; t=1305262148; x=1336798148; h=from:to:subject:date:message-id:in-reply-to:content-id: content-transfer-encoding:mime-version; bh=eVXy9Lbp5iPjpwGm3KJsReLQUTzq4lGb2zGVGBN6gyM=; b=hfym8Eb/8AYWSoW4MXQbdkFM48ZFaaJML9KmXc8k/UgelUeylcghUvkh xhzmMOzTgDPA5ilRrXr49jlY9U4GYAHRwY7H1RjnswMWD/gyOXOneKWqb ILoGas8uqekwTR2; X-IronPort-AV: E=Sophos;i="4.64,362,1301900400"; d="scan'208";a="23148751" Received: from ESV4-EXC02.linkedin.biz ([fe80::4d74:48bd:e0bd:13ee]) by esv4-cas02.linkedin.biz ([172.18.46.142]) with mapi id 14.01.0251.000; Thu, 12 May 2011 21:52:23 -0700 From: Milind Bhandarkar To: "general@hadoop.apache.org" Subject: Re: Defining Hadoop Compatibility -revisiting- Thread-Topic: Defining Hadoop Compatibility -revisiting- Thread-Index: AQHMEPOnIB+Y40jJf0ahsOjyQf2X+pSKG1eAgAB+JQD//5axgA== Date: Fri, 13 May 2011 04:52:23 +0000 Message-ID: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [172.18.46.247] Content-Type: text/plain; charset="us-ascii" Content-ID: <9C7DFA44E173F1489918182DF0B03FD3@linkedin.com> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Virus-Checked: Checked by ClamAV on apache.org Ok, my mistake. They have only asked for documented specifications. I may have been influenced by all the specifications I have read. All of them were in English, which is characterized as a natural language. But then, if you are proposing a specification in a non-natural-language, isn't that called a test suite ? Or is there a middle ground ? - milind --=20 Milind Bhandarkar mbhandarkar@linkedin.com +1-650-776-3167 On 5/12/11 9:05 PM, "Ted Dunning" wrote: >Did anybody propose natural language only specifications? > >On Thu, May 12, 2011 at 8:37 PM, Milind Bhandarkar >> wrote: > >> The problem with (only) specs is that they are written in natural >> language, and subject to human interpretation, >>