create a 'google' style search engine. Streamline the govt form data concepts all the way down to forms, all into preceptive categories that allow users to search using any term they can conceive of while trying to look for an agency, form or data.... from the data at CDC to the latest on the oil spill int he Gulf to how to fill out your govt job app and apply for benefits. google.gov!
1) Allowing people to comment on any given comments for a certain idea.
2) Analyze the ideas to show interdepencies and relationships between them.including comments.
3)Just counting number of votes for an idea is not usefull, and may be interpreted differently by different realities.
4)provide a structural meaningful for all inputs received and initiate dialogues to discuss.
Sort datasets and tools by rating and number of ratings not just ratings.
We need to have all of the IT leaders in the country trained and cognizant of the information security challenges that face our businesses, our intellectual property and our infrastucture. As technology continues to evolve over the coming months and years, portions of the IT infrastructure are falling behind. Let's create a strategic training program and bundle a toolset to make infosec an issue that gets the attention ...more »
As additional datasets become exposed through RDF, and described through RDFS/OWL-based ontological definitions, I would like to see the ability to mashup DATA.GOV datasets with the rest of the Linked Open Data cloud, using SPARQL.
Government/Public Sector Practice
Rather than organizing the data according to organizational silo's (eg. USDA, HHS, etc) recommend developing an interface that allows for multiple "views" of the same data. Taking Apple's iPhoto software as an example - the single photo dataset can be viewed according to events, photos, faces, or places. This allows the same dataset to be sliced and diced in multiple ways - unearthing interesting connections along the ...more »
This entry is a consensus recommendation of seven organizations that work on government transparency of which OpenTheGovernment.org is one. Require agencies to indicate whether a high value dataset was previously unavailable, available only with a FOIA request, available only for purchase, or available, but in a less user-friendly format. Going forward, this will make it easier to track how agencies are complying with ...more »
This entry is a consensus recommendation of seven organizations that work on government transparency of which OpenTheGovernment.org is one. Require agencies to explain why the data is high value by having them designate which of the “high value criteria” the data meets: information that can be used to increase agency accountability and responsiveness; improve public knowledge of the agency and its operations; further ...more »
Using some of the recommendations here, including documenting solid applications of the data, and a 'social network of users' will help to establish and document the 'value' of data by the importance and diversity of data use. Documenting requests for data as has been suggested by others can help with this and some agency agency perceptions(with all due respect) that "numbers" of data sets proffered satisfies the criteria ...more »
In light of the excellent work other governments are doing in this area, the US should spearhead an international group (maybe in conjunction with the UN) to share best practices, cross-fertilize experience and maybe even share common code or data formats.
This relates to data.gov in a tangential fashion - however perhaps either the data or the dashboard could reside within Data.gov: The idea here, toward government transparency, is to develop a simple, common format for reporting FOIA requests, with a historic and status context, e.g. number of new requests opened in a given month, number of existing closed in a given month, number of requests outstanding broken out by ...more »
The approach to making information available should be simple, but not simplistic. Common things should be simple to achieve, more complex things should be possible. What I mean by this can be seen by contrasting a spreadsheet to a relational database. In my view spreadsheets are "simplistic". Relational databases are really not that much more difficult to use, I would even say they are simple to use. A relational ...more »
The OMB Open Government Directive published on December 8, 2009 includes what are (in my opinion) some undefined terms and very unrealistic expectations and deadlines for federal agency compliance with the directive. It also did not include any method for assessing progress towards the spirit and intent of the stated objectives. I would like to offer a simple framework that the Data.gov effort can use to work (collaboratively) ...more »
On Page 9 of the CONOP, the example of Forbes' use of Federal data to develop the list of "America's Safest Cities" brings to light a significant risk associated with providing 'raw data' for public consumption. As you are aware, much of the crime data used for that survey is drawn from the Uniformed Crime Reporting effort of the FBI. As self-reported on the "Crime in the United States" website, "Figures used in this ...more »
As currently written, the CONOP only addresses internal activities (means) and doesn't identify the outcomes (ends) that would result from successful implementation of Data.gov. In paragraph 1 the CONOP states "Data.gov is a flagship Administration initiative intended to allow the public to easily find, access, understand, and use data that are generated by the Federal government.", yet there is no discussion about "what ...more »