W3C home > Mailing lists > Public > public-rdf-dawg@w3.org > January to March 2012

Re: Comment on SPARQL 1.1 CSV Results

From: Gregory Williams <greg@evilfunhouse.com>
Date: Sun, 5 Feb 2012 20:52:36 -0500
Cc: Lee Feigenbaum <lee@thefigtrees.net>, Andy Seaborne <andy.seaborne@epimorphics.com>, SPARQL Working Group <public-rdf-dawg@w3.org>
Message-Id: <C72BD624-A8B9-4260-9B0B-5C305AA69DD5@evilfunhouse.com>
To: "Eric Prud'hommeaux" <eric@w3.org>
On Feb 5, 2012, at 7:46 PM, Eric Prud'hommeaux wrote:

> On Sun, Feb 5, 2012 at 18:57, Lee Feigenbaum <lee@thefigtrees.net> wrote:
>> I agree with Greg.
>> Given that the CSV format is purposefully simple and lossy, I think that
>> unbound variables and empty strings should both be empty strings in CSV,
>> which can be either ,, or ,"",
> I believe the use of existing libraries argument is more salient for
> parsers than for serializers (i.e. printf loops). What then is the
> harm in specifying the "" distinction, which only some parsers will
> distinguish?

While CSV is a trivial format, I'd suggest that it's not just a matter of "printf loops". There still is escaping to be done, and leaving it to a library is always safer than trying to hack it together in a loop.

Also, I'm worried about us trying to define semantics based on syntactic variations that are specified as being equivalent. It's no longer 'just CSV' if we're ascribing semantics to whether you use ,, or ,"",. The CSV format is inherently lossy, so I'm not sure why this particular case should be any more of an issue than others.

Received on Monday, 6 February 2012 01:53:11 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:01:10 UTC