Transparent Calendars

Posted on May 6th, 2009 - 12:30 PM

About the author: Jeffrey Levy joined EPA in 1993 to help protect the ozone layer. He is now the Director of Web Communications.

A couple of weeks ago, EPA Administrator Jackson issued a memo calling for maximum transparency in everything we do. The memo put into EPA terms the ideas first espoused in the memo President Obama issued on his first full day in office, saying that government must be transparent, participatory, and collaborative.  The overarching theme is that you, the public, are entitled to know what we’re up to.

Those of us in EPA’s Web community really took notice, because our site and various social media tools (Facebook, Twitter, etc.) offer so many ways to serve those goals.  We have several projects underway.

image of a calendar pageOne of the first is that the Administrator publishes her daily working calendar showing meetings with the public.  Next, she directed her senior management team to do the same.

We’re now setting up the process, and you’ll soon be able to see who’s meeting with top EPA leaders.

It occurs to us, though, that we could do better than simply giving you a calendar in table form. What if you could download multiple calendars across EPA and other agencies, and then create mashups as you saw fit?

So we want to publish machine-readable formats, too. And that’s where you can help us. Please let us know what works best: comma delimited, something else?

Also, please help us understand how you’d use the info; that’ll help us figure out how to make it easier.

We’ll be coming back to you to ask for your help on other questions, too, so here’s to a long, collaborative discussion!

Tags: ,

| Permalink | TrackBack

7 Responses to “Transparent Calendars”

  1. Amanda Says:

    I think CSV are the best way to go for a mass calendar. For me, I use Outlook at work, Google for personal, and my iPhone to merge the two. I’d probably pull a google calendar into my site to pass on the information.

    [Reply]

  2. Jeremy Carbaugh Says:

    At a bare minimum, you should provide schedule data using the iCalendar format.

    http://www.ietf.org/rfc/rfc2445.txt
    http://en.wikipedia.org/wiki/ICalendar

    iCalendar is widely supported by applications such as Microsoft Exchange, Apple’s iCal, Google Calendar, and others. There are also libraries for many programming languages that make it easy to work with the data in the format.

    In addition to iCalendar, other formats to consider include:

    - XML using xCal (http://xml.coverpages.org/iCal.html)
    - hCalendar to markup the HTML page (http://microformats.org/wiki/hcalendar)

    I would actually avoid releasing generic comma delimited data since there are plenty of great formats meant specifically for schedules and calendars.

    Great work, and thanks much for asking the community for suggestions!

    [Reply]

  3. Joshua Tauberer Says:

    Besides the choice of data format, one needs to also consider what information there is to be made available and how the public might use it. If there is a calendar of meetings, the public might want to be able to (reliably) categorize meetings by type or topic. In that case you would need to include in the calendar data some normalized values for topics that machines can search and sort, rather than merely having it be obvious to a human reading the free text description of the event, and that may not be possible in all calendar formats. I’m not familiar with how the EPA works so I can’t give good examples. Also depending on how many calendar feeds you create, you may need to also think about aggregating them or listing them in a way that makes it easy for users or web developers to choose the right ones. That is, calendars may also need *metadata* reliably describing what the particular calendar feed is for.

    [Reply]

  4. Jeffrey Levy Says:

    Thanks very much to the three folks who’ve left comments so far. I’ll discuss your thoughts with our folks here. Regardless of what the first version looks like, though, please continue to help us improve.

    And to everyone, please keep sharing your ideas.

    Jeffrey Levy

    [Reply]

  5. Michael Hessling Says:

    What Jeremy Carbaugh said, seriously. It’s harder if you don’t yet have a backend powering everything (so you can output into multiple formats), but it’ll be the most machine-readable that way.

    I can see, at a minimum, people pairing the calendar with Dopplr or Mapme.at (or maybe you’ll do that).

    [Reply]

  6. Adriel Hampton Says:

    Jeffrey - It is great to see the EPA leading in this initiative! I am going to look at iCalendar, and will be eager to see where you go with this. Wide-scale adoption of public calendars will go a long way to building a better government.

    [Reply]

  7. David Bush Says:

    Jeffrey Levy, You post a perfect article on American government. They are always perfect in time. So their calender also transparent.

    [Reply]

Leave a Reply