3. Gov. Data Publishing Today Good news Significant amount of data is already being published Mostly federal e.g. Census Bureau, HUD, DOE, CDC, USDA, OMB, FBI Increasingly state and local e.g. CT, DC, IN, MA, MD, PA Challenges Data is spread across a slew of government and commercial sites Data is in a variety of formats e.g. ASCII, SAS, ESRI Using data requires patience, resources, and programming skills Data publishing is not a trivial task both politically and technically www.data.gov addresses data discoverability problem
4. Why OGDI? Help government organizations to Accelerate data publishing plans Publish data more efficiently Promote use of cloud computing by the government Tap into the cloud today (Windows Azure) Learn by doing Drive policy based on experience Promote use of government data by citizens and businesses Motivate government to publish more data and improve data quality
5. What is OGDI? Set of free open source software assets facilitating data publishing on the Web using open standards Set of software components .NET or PHP (coming this summer) Deployable in the cloud Provide interactive and API access to the data Makes data instantly browsable and queryable by people and applications Section 508 compliant Data can be saved in DAISY format Exposes data in a set of standard formats e.g. AtomPub (OData), JSON, KML Comes with a comprehensive set of samples demonstrating data access from most popular Web platforms and languages e.g. PHP, Python, Ruby, Flash
6. OGDI High Level Architecture Storage Data Loader Data Service (ogdi.cloudapp.net) Interactive SDK (ogdisdk.cloudapp.net) HTTP/REST Source Data Sets Client and Web apps (AJAX, Flash, Silverlight, Ruby, PHP, etc.)
7. OGDI vs. data.gov OGDI is a solution, not a destination on the Web OGDI instances can be referenced by data.gov OGDI makes data instantlyqueryable and browsable by people and software OGDI renders data in a small set of Web friendly formats OGDI complements data.gov