Re:Congress votes to make open government data the default i...
by wilde on Sunday December 23, 2018 @10:51AM
(#18746694)
I’ll defend this practice. It’s the only way of knowing for sure that you’re transmitting exactly the information you intend to send. Even copy/paste often picks up other stuff you don’t intend.
[ Parent
| on HN ]
Re:Congress votes to make open government data the default i...
by TheCoelacanth on Sunday December 23, 2018 @02:14PM
(#18747772)
It's more of a way to prevent transmitting any easily accessible data at all. Using a human-auditable but still machine-readable format like CSV is what should be done.
Re:Congress votes to make open government data the default i...
by prepend on Sunday December 23, 2018 @11:09AM
(#18746819)
It the only, but maybe the easiest.
Having a data review process with automated integrity, confidentiality, and quality checks is not terribly difficult.
But having a prototocol to export the pdf to csv is also dead easy for confirming only the data relevant is included. ASCII is just as “easy” as scan, but it requires training clerks to be data-oriented rather than document.
Re:Congress votes to make open government data the default i...
by paulryanrogers on Sunday December 23, 2018 @02:11PM
(#18747753)
_ugh_ if only CSVs were standardized sooner and more completely. There are many encoding, delimiter, escaping and truncation conventions to deal with in real world data.
Re:Congress votes to make open government data the default i...
by prepend on Sunday December 23, 2018 @06:38PM
(#18749179)
Definitely. They are better than PDFs, but still have lots of room for improvement.
Re:Congress votes to make open government data the default i...
by akudha on Sunday December 23, 2018 @07:45PM
(#18749467)
There are other ways to ensure this. Even with your own logic, it would make sense then to send both the Excel sheets and scanned PDFs of the Excel sheets, isn't it? It would be super comical though