DataFormats.CSV History

Hide minor edits - Show changes to output

August 14, 2006, at 12:07 PM by MatthewVernon - Another problem with CSV
Changed lines 11-12 from:

*If you do use CSV you will almost certainly require  multiple files (one for the nodes, one for the groups, one for the links, one for the other links, one to explain each file's format etc), but that is easily worked around by archiving them all together in .tar or .zip files. I think, for networks, this might even be a better option
to:
*If you do use CSV you will almost certainly require  multiple files (one for the nodes, one for the groups, one for the links, one for the other links, one to explain each file's format etc), but that is easily worked around by archiving them all together in .tar or .zip files. I think, for networks, this might even be a better option
* Many programs simply get CSV wrong, particularly if you start wanting commas, newlines, or the like in your records.
Deleted line 0:
Changed lines 9-11 from:
to:
*CSV focuses on table (row/column) format. This is just as difficult as [[XML]] to map to social network data without forcing it to do unnatural things
*CSV columns SHOULD NOT change meaning mid-file

Added lines 1-11:

data formated into columns using comma or tab delimeters

!!Pros:
*Dead simple to parse.
*Work well for any situation with records of any sort (i.e.
"case by variables" situations) or for sociomatricies.

!!Cons/ Considerations:

*If you do use CSV you will almost certainly require  multiple files (one for the nodes, one for the groups, one for the links, one for the other links, one to explain each file's format etc), but that is easily worked around by archiving them all together in .tar or .zip files. I think, for networks, this might even be a better option