@postmodern_mod3 But what does that mean?
-
In reply to:
This JSON format as two hashes: "rows" and "columns". o_O
http://biom-format.org/documentation/format_versions/biom-1.0.html#minimal-sparse-otu-table
In reply to:@postmodern_mod3 Agreed. You keep giving me reasons to use HTML over JSON (which I already support). I'm looking for good reasons NOT TO. ;)
In reply to:@defiler Not necessarily a great idea.
In reply to:@defiler Agreed. Though, JSON tools that are like "here's your 'API'" are really just JSON views into your objects and tables.
RT @heyaudy: @veganstraightedge scientific data http://biom-format.org
In reply to:@postmodern_mod3 How do you mean? Or an example?
Related:
Other than Activity Streams, what *formats* exist in JSON?
In reply to:@defiler Right?! HTML is kind of amazing. And most of us don't have Unique Scaling Requirements™.
The API/app we're building is HTML only.
In reply to:@defiler Ok. That's fair. HTML does allow ambiguous white-space, like you said.
Cool. Anything else?
In reply to:@defiler I don't understand. Please expand on "the dead-simple whitespace story". Kthx.
In reply to:@leJDen Which is why I'm asking for other people's input. :D
In reply to:@leJDen I tend towards "use HTML for everything even/especially 'APIs'", but I'm trying to be open to a JSON use case.
In reply to:@postmodern_mod3 I tend towards "use HTML for everything even/especially 'APIs'", but I'm trying to be open to a JSON use case.
In reply to:@postmodern_mod3 I'm looking for a case where JSON is a better fit than HTML.