A major barrier to increased re-use of the growing number of open-source civic tools is the lack of agreement on how to name things. To give a very simple example: if one project's elected officials API calls a person’s name "name" and another calls it "full_name", and you're writing a Q&A platform to ask questions to these elected officials, you'll need to write an adapter for each API. Committing to a standard way of naming things would maximize interoperability, reduce wheel reinvention and make re-use that much easier.
This session is for anyone who can benefit from standards in their work. Depending on who attends, it can begin with a brief presentation of existing efforts, such as http://popoloproject.com/ which unites a number of existing standards to address common open government uses cases. Attendees are encouraged to present their own work on data and API standards/specifications. The session's goal is to get people working together better towards establishing standards, and to prioritize what data requires standardization first.
If you'd like to join the conversation before TCamp, please join the recently created W3C Open Government community group (http://www.w3.org/community/opengov/) and its mailing list (http://lists.w3.org/Archives/Public/public-opengov/).
Posting new ideas has been disabled for this site.