published february 18, the Initial Implementing Guidance for the American Recovery and Reinvestment Act
guidelines created an impressive echo on the web, because they were an exciting sign that government openness and transparency make one significant further step, setting up a feed-based infrastructure for information dissemination. these guidelines are only an initial version (the document itself claims that more detailed guidelines will be published in 30-60 days), and our first reaction as well as some more detailed feedback was still not sufficient to explain what we thought was required to make this really work in a reliable and robust way.
together with my colleagues eric kansa and raymond yee, we have now finished a technical report about next steps for the recovery act guidelines, making specific recommendations for technical guidelines and best practices around them. this is the abstract:
the most exciting part about writing this report was not so much writing the report itself, but creating a sample dataset for demonstration purposes. the sample dataset homepage has links to the underlying XML, schemas for the three feed types (for communications, formula block grant allocations, and weekly reports), fake agency web pages, fake agency feeds, and even visualizations of our fake data in Google Maps, Timemap, even featuring a KML version to load into Google Earth. all of this is currently generated from the initial XML with a simple XSLT transformation (the goal would of course be for all of this data to be made available in a distributed fashion).
for something as significant as the recovery act and as heavy as $787 billion, it is of course impossible to create complete and final guidelines in just two weeks. thus, our mail goal was to demonstrate that the guidelines don't need to require anything complicated to make exciting things possible; all that is required are guidelines specific enough so that data can be found reliably and in a machine-readable way. recovery.gov and its lists of agency sites and agency reports are a promising starting point, and with our report we hope to make some contributions to how to improve the transparency and openness of stimulus feeds.
I disagree with the use of the "simple" GeoRSS profile, which is a gateway to bad practices like multiple locations, but otherwise this is great work.
Posted by: Sean Gillies | Monday, March 16, 2009 at 13:30
@sean: thanks for your comment, and you're absolutely right that the guidelines should say that agencies should not use more than one location, if they decide to use GeoRSS. or if agencies were allowed to put in more than one location (maybe one for a point, and one for a polygon for more advanced spatial representations), then these would have to be qualified (but that is currently not allowed by GeoRSS, i am afraid).
which brings me back to the reply i still owe you (and i hope to get back to that thread soon): GeoRSS as it currently exists is not all that great and guidelines like the ones you proposed would be a very useful first step. but overall, i think GeoRSS needs a major revision, cleaning up the location model, producing a well-defined spec, and making the format extensible in a well-defined way. and then we can also start calling it GeoAtom.
Posted by: dret | Monday, March 16, 2009 at 14:36