-
Website
http://eaves.ca/ -
Original page
http://eaves.ca/2009/09/30/three-law-of-open-government-data/ -
Subscribe
All Comments -
Community
-
Top Commenters
-
Devin Johnston
4 comments · 4 points
-
Harley Young
26 comments · 1 points
-
Stephen Taylor
6 comments · 54 points
-
Facebook User
4 comments · 1 points
-
nickcharney
5 comments · 1 points
-
-
Popular Threads
-
A Sad Day for Canadian Democracy
1 week ago · 19 comments
-
Eaves.ca Blogging Moment #7 (2009 Edition): Explaining the New to the Old
3 days ago · 3 comments
-
The Supreme Court of Canada: There are no journalists, only citizens
2 weeks ago · 11 comments
-
MuniForge: Creating municipalities that work like the web
1 month ago · 9 comments
-
Why David Suzuki Matters
3 weeks ago · 7 comments
-
A Sad Day for Canadian Democracy
You might also be interested in:
* http://www.w3.org/TR/2009/WD-gov-data-20090908/
* http://blip.tv/file/2664587
* http://www.acq.osd.mil/ats/opensyst.htm
* http://www.opengovdata.org/ (more on the 8 principles)
"That is what we need and that is what is needed."
A wee ad-like but goes beyond the like.
'Use' works, or what about 'build'?
Find, build, share.
Or, 'add value'.
That said, may I suggest you modify your message a bit if you truly want to sell it to government? If you believe that the public service is behind the techno-curve, then it would follow that you shouldn't be speaking to public servants in techno-jargon and buzzwords. The language you use in your "Three Rules" is, I'm sure, second nature to the tech-savvy. However, to an audience that is (or that you believe to be) less knowledgeable, it would make sense to explain your terms at what to you probably seems like an absurdly basic level. What do "spidering" and "indexing" mean in the online context? What do you mean by "open and machine readable format"? (Your example of the Vancouver city government's open data helped make that part more understandable, although I would still be careful assuming everyone knows what an ".xml" does. A lot of people in that room only know "indexing" in the context of library shelves.)
This may seem ridiculous to you, but not everyone with a computer has to know how to program, just as not everyone with a car needs to be a mechanic, and not everyone who flies needs to be a pilot. I'm your age and I'm a techno-peasant by that standard. Now consider the age of the average public servant, especially the ones whose knowledge and experience you're most hoping to capture before they retire...I'm not saying you don't have good ideas, but you need to put them in really plain language with a lot of explanation if you want to convince government generally of how good they are.
There's a good discussion of this issue here: http://spaghettitesting.ca/2008/11/06/gcpedia-w...
One other tip for presenting to government people: be very careful about using the word "literally". If information can't be found, then yes, it *might as well* not exist, it *is as good as if* it does not exist...but unless the failure of, say, a hard copy book to register in a Google search causes that book to spontaneously dematerialize from a library shelf, it does not "literally* cease to exist. This may seem nit-picky, and I'll confess that to some extent it is, but I guarantee you I'm not the only person in the room who noticed. There were a lot of bright, educated people there, and if you're misusing words they do understand, they're more likely to write off your great claims about new technology that they don't.
As someone who *wants* to see our institutional memory captured and preserved, and our government as open and responsive as possible, I wish you luck!
Lots of interesting things brewing on the open data front, thank you for the luck and I hope to have more to share soon.
@Jon Stahl: I agree that "use" is better than "play".
@David Eaves: "...or analyze in Excel". Surely this excludes those that do not use Microsoft products.
There are open standards and then there are defacto standards - I'm not such a ideologue that I believe things should only be available in open standards (e.g. ODF or Ogg) but that they should be available in both (so am in complete agreement with you). That said, I know this line might make some more ardent open standard folks unhappy but the fact is, a huge number of people have no idea what an ODF is and wouldn't know how to open it, so we've got to give them open standards and standards they use.
Las Tres Leyes de Información de Gobierno Abierto:
1. Si no es accesible para las arañas de web, no existe.
2. Si no es disponible en un formato que puede ser leído y procesado con éxito por una computadora, no puede motivar.
3. Si un framework legal no permitir alguien para hacer obras derivadas, no da poder.
http://www.cpsrenewal.ca/2009/10/column-three-l...
Again, your #righttoknow talk was very empowering. Cheers my friend.
1. If it can’t be spidered or indexed, it doesn’t exist
I take this to mean we want to capture these data in a search engine. Now, pointers to data, I would agree. But the data itself - can we categorically say that all data must be able to be captured in a search engine? That's might be google's view on the world, but I suspect that there are some things with DO exist but which are not suitable for catpure in a search engine..
http://gisnap.com/
The place where fun never ends
http://gisnap.com/
The place where fun never ends