Return-Path: X-Original-To: apmail-commons-dev-archive@www.apache.org Delivered-To: apmail-commons-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id A4D3778C3 for ; Tue, 29 Nov 2011 15:43:39 +0000 (UTC) Received: (qmail 38788 invoked by uid 500); 29 Nov 2011 15:43:39 -0000 Delivered-To: apmail-commons-dev-archive@commons.apache.org Received: (qmail 38701 invoked by uid 500); 29 Nov 2011 15:43:38 -0000 Mailing-List: contact dev-help@commons.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Commons Developers List" Delivered-To: mailing list dev@commons.apache.org Received: (qmail 38692 invoked by uid 99); 29 Nov 2011 15:43:38 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 29 Nov 2011 15:43:38 +0000 X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [209.85.160.171] (HELO mail-gy0-f171.google.com) (209.85.160.171) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 29 Nov 2011 15:43:31 +0000 Received: by ghbz2 with SMTP id z2so10648884ghb.30 for ; Tue, 29 Nov 2011 07:43:10 -0800 (PST) MIME-Version: 1.0 Received: by 10.236.73.166 with SMTP id v26mr71736265yhd.100.1322581390863; Tue, 29 Nov 2011 07:43:10 -0800 (PST) Sender: jcarman@carmanconsulting.com Received: by 10.146.74.14 with HTTP; Tue, 29 Nov 2011 07:43:10 -0800 (PST) Received: by 10.146.74.14 with HTTP; Tue, 29 Nov 2011 07:43:10 -0800 (PST) In-Reply-To: <4ED4EBA5.5070902@apache.org> References: <4EBD6E75.5050101@apache.org> <448080C2-091C-4293-8C48-C89B820E9E15@googlemail.com> <4ED49915.8070404@apache.org> <4ED4EBA5.5070902@apache.org> Date: Tue, 29 Nov 2011 10:43:10 -0500 X-Google-Sender-Auth: bMe2sfZx78J4psN9LR50YqVxzoM Message-ID: Subject: Re: [csv] API design From: James Carman To: Commons Developers List Content-Type: multipart/alternative; boundary=bcaec5396e2efd2cea04b2e179e9 X-Virus-Checked: Checked by ClamAV on apache.org --bcaec5396e2efd2cea04b2e179e9 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable It really sounds like csv should just be a format that's plugged into another library. On Nov 29, 2011 9:29 AM, "Emmanuel Bourg" wrote: > Le 29/11/2011 14:43, Matt Benson a =E9crit : > > Well, assuming "header-free" CSV output you could do any odd thing like: >> >> foo;bar;(2);element1;element2; >> >> giving an open-ended format. Not saying such would be the greatest >> idea, but could be usable under the right circumstances. >> Alternatively, one could embed the collection: >> >> foo;bar;"{element1;element2}" >> > > ... and it starts to get fun when you want to escape the special > characters '"', ';' and '}' in the collection ;) > > It's possible to tailor a CSV like format that supports collections, but > if it doesn't interoperate with other CSV tools it's hardly useful. If > people want a more capable format without caring about interoperability > there are legions of alternative serialization APIs available. > > That's why I think [csv] should focus on the simple format defined by > RFC4180, exotic features are for more ambitious projects (at least for no= w). > > Emmanuel Bourg > > ------------------------------**------------------------------**--------- > To unsubscribe, e-mail: dev-unsubscribe@commons.**apache.org > For additional commands, e-mail: dev-help@commons.apache.org > > --bcaec5396e2efd2cea04b2e179e9--