News for hackers. Stuff that matters.

Ask YC: Retaining the Authenticity of Government Data

The government is currently considering a major overhaul of its public data services, making a wide assortment of APIs available for developer use.

It's all being held up by a concern that there will be no way for end-users to be able to discern the real data from manipulated or made-up data.

Are you aware of any best-practices for avoiding this problem, but also allowing the data to be freely available?

( 4 comments | 3 points | on HN )
Re:Ask YC: Retaining the Authenticity of Government Data by bayareaguy on Wednesday June 18, 2008 @04:55AM (#220635)
They could just publish a few public keys and use them to digitally sign the data.

http://en.wikipedia.org/wiki/Digital_Signature

Re:Ask YC: Retaining the Authenticity of Government Data by DenisM on Wednesday June 18, 2008 @01:10PM (#220901)
To help you in your quest, the problem space is called "data provenance" - information about origination, history and trustworthiness of the data. There's been plenty of research about this topic recently.
Re:Ask YC: Retaining the Authenticity of Government Data by jamslevy on Wednesday June 18, 2008 @04:43AM (#220629)
Re:Ask YC: Retaining the Authenticity of Government Data by babyshake on Wednesday June 18, 2008 @06:40AM (#220658)
But digital signatures would require some baked-in solution that would be problematic in some respects, like limiting access from unsupported platforms.

As far as I know, there's no clear way of maintaining the integrity of the data without keeping it in some sort of walled garden. Am i wrong?