National Dialogue on Improving Federal Websites Data, Apps, APIs...

Use a dialogue like this to gather user input and feedback on the design, usability, and data made available via the Performance.gov site.

I am recommending that the OTIS, ECHO, and Envirofacts web services are moved to the RCRAInfo server to directly access RCRAInfo data that displays in these services, with a tie into any other servers (e.g. ICIS, NPDES). This would save time and errors due to extraction of data from one server and uploading to another. Also, the data will be real time data, as opposed to older data that is currently shown. The ...more »

Experts have called for the government to make its data available in its original form to better serve power users who provide added value by analyzing the data or developing apps based on the complete data. Database data can be delivered directly to web visitors' database systems using a database sharing service that maintains db structure and complex types, does not convert to intermediate formats (e.g. CSV, XML..) ...more »

Federal Register publishing drives the production of so many agency materials. The new Federal Register offers improved search functionality and an API. Individual articles have a clean, friendly look and feel. Individual paragraphs and headings have their own ID for building links and citations. Rules include links for comments; FR, CFR, USC, and Federal Law references are hyperlinked (this still needs more work); contents ...more »

Given the ever-evolving nature of the web, the importance of flexibility towards new technologies should be a regularly reviewed/updated list of acceptable APIs. Having this list available would allow designers/developers to keep updated on approved options as they appear.

The Electronic Code of Regulations published by NARA and GPO is a great resource and stays amazingly current (http://ecfr.gpoaccess.gov/). However, the links to items appear to be based dynamically on the node position of the item with the larger Title and Part document. When preceding items are deleted or added, the link to a given item changes. So, for example, a link to 17 CFR 240.15c2-12, will change when new 17 ...more »

Many government agencies have overlapping and important data. NOAA, Federal Register, HHS, FCC, and others are beginning to offer more of it as APIs. As more agencies do the same, there are strong benefits and efficiences that can come from agencies making a point to consume each others APIs when creating new products for the public. They can create mashups of their own data with that of other agencies to create products ...more »

Agencies should design their websites and online tools to facilitate interoperability and re-use by other agencies and external developers. Improving the interoperability of online datasets with other information and tools from inside and outside the government multiplies the value of agency websites by enabling mashups and innovative applications. Agencies should also facilitate re-use by publishing in open machine-readable ...more »

JQuery-style coding (or scripting) libraries should be created for government use - allowing for greater standardization, cross-compatibility, and compliance across government websites. These libraries could also then be regularly updated and maintained by government staff (who have the government's best interest in mind). This concept would be similar to a open-source development platform - but limited to government ...more »