Re: sparql11-results-csv-tsv

On Jun 14, 2011, at 1:20 PM, Andy Seaborne wrote:

> Because CSV allows it, I think we should aim for maximum interoperability - We are not registering text/sparql-results+csv.

I would consider *requiring* the header line the best path for interoperability in that it's the path of consistency. Otherwise I have to jump through hoops to figure out if the first line is variable names or values. And requiring me to have access to the http headers that come along with the response to figure that out seems contrary to the simplicity argument for having such a serialization (and easily avoidable).

.greg

Received on Tuesday, 14 June 2011 19:05:19 UTC