- From: Adam Harvey <harvey@thedesignstate.com>
- Date: Thu, 21 May 2009 07:57:14 -0400
- To: eGov IG <public-egov-ig@w3.org>
Hello, More input below: >> ... >>> + a set of small docs with guidance? >>> (could be recs or not) >> >> I am not sure what these "small docs" would do that would not be >> included in BP and the rewritten Note, but am open to suggestion. >> Are you thinking of technical documents that would be more of a how- >> to? a series of case studies of particularly effective practices? > > I was thinking of small how-to like things, e.g. techniques to > identify and expose OGD, but also identification of scenarios to do > so. More how-to than case studies. This path reminds me of Mark Pilgrim's 30 day guide to a more accessible website, called Dive Into Accessibility: http://www.diveintoaccessibility.org/ which provides some scenarios that make it easier to understand how to implement BPs. I see this as a great opportunity to move forward, mainly because I see the most room for improvement in this area. For example, the Board of Elections in my county makes all of the past election data available on their website. This is good, except that the presentation format is just a .txt file. I've received requests from people who would like to be able to compare turnout rates for specific precincts from election to election. Without an easily manipulated file format or a presentation layer (like Google Analytics offers) they have no way of doing so, apart from manually sifting through the mounds of data. Okay, off to work. Have a good day/afternoon everyone! Adam
Received on Thursday, 21 May 2009 12:06:39 UTC