- From: Bart van Leeuwen <bart_van_leeuwen@netage.nl>
- Date: Fri, 27 Mar 2015 15:35:31 +0100
- To: Steven Adler <adler1@us.ibm.com>
- Cc: "DWBP WG" <public-dwbp-wg@w3.org>
- Message-ID: <OFE053DE02.195298E1-ONC1257E15.004FC585-C1257E15.0050290D@netage.nl>
I think we try to assemble a 'best practice' with this working group. I sincerely hope you don't consider data published in a PDF to conform to this best practice. I'm not arguing that it is possible to get usable data from these formats, but they were not intended to carry data in a machine readable way. Bart Steven Adler <adler1@us.ibm.com> wrote on 27-03-2015 15:09:32: > From: Steven Adler <adler1@us.ibm.com> > To: "DWBP WG" <public-dwbp-wg@w3.org> > Date: 27-03-2015 15:10 > Subject: NY Property Tax Explorer > > You may recall I submitted a use case about this example from NYC > last year. The developer, Chris Wong, who works for Socrata, wrote > a Ruby routine to scrape 1000 PDF files for property tax data to > fill out this map app: > > http://www.w3.org/2013/dwbp/track/issues/56 > > Chris is a self-taught developer, by no means a pro. I think this > story well demonstrates that Data on the Web today is quite > innovative and PDF, JPG, AVI, MP3, and MP4 are commonly machine readable. > > Restricting our recommendations to file formats that conform only > those covered by W3C WG's (JSON, CSV, RDF, etc) ignores the reality > of how Open Data is published and used. > > > Best Regards, > > Steve > > Motto: "Do First, Think, Do it Again"
Received on Friday, 27 March 2015 14:36:08 UTC