Data, Apps, APIs...

Design for Interoperability and Re-Use

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 »

Submitted by

Voting

13 votes
Active

Data, Apps, APIs...

Push .govs to consume each others APIs

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 »

Submitted by (@graybrooks)

Voting

11 votes
Active

Beyond Websites (Mobile, Broadband...)

Publishing .govs via APIs will allow innovation yet to come

By changing the expectations for government websites to be that they make all of their content and data available via web services will change the game. Not only are there benefits for the webmasters when they eat their own dogfood, the public can also access, consume, republish, and further disseminate the information in ways that the originating agency hasn't considered and in ways which are more convenient for audiences ...more »

Submitted by (@graybrooks)

Voting

9 votes
Active

Services and Transactions

Wrap Complaint Forms in an API

So, we have this site called "Recalls.gov" and it's a great cross-agency aggregator for information on product recalls. But what we haven't done is set up a one-stop shop for consumers to SUBMIT complaints for agencies to investigate. Citizens still need to figure out what agency has jurisdiction over the product they want to complain about. What citizen is going to know that they should complain about their child safety ...more »

Submitted by

Voting

8 votes
Active

Beyond Websites (Mobile, Broadband...)

Consume their own APIs when building products

In the model of 'eating their own dog food', government agencies should not just offer the public APIs of all their front-facing content and data, but consume those APIs for their own products. This is not only more efficient but will reinforce the use of APIs as well as promote a better feedback loop whereby agencies will find and correct errors and improve the format of their public offerings. The FCC has opensourced ...more »

Submitted by (@graybrooks)

Voting

8 votes
Active

Policies and Principles

Require .govs to provide all content and data via web services

In the short and medium term, one of the best efforts that government websites can effect in order to better serve the public would be to offer webservices (e.g. RESTful APIs) of all website content and data. This way, any information the website is offering, including not just public data, but also the textual content of the site, can be consumed by the public in a much more powerful and efficient manner. Interested ...more »

Submitted by (@graybrooks)

Voting

7 votes
Active

Data, Apps, APIs...

Make better use of Federal Register 2.0

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 »

Submitted by

Voting

6 votes
Active