Developing open data standards is all the rage. In fact, chances are that you're drawing one up right now (I am). In that case, here's a list of things you may believe about your data standard, but that are probably not true.
I've had the chance to contribute to two influence mapping projects in South Africa and Mozambique. While both projects focus on finding possible conflicts of interest within a small group of politically exposed persons, their approach has been very different.
When we discuss data journalism, we often tend to think of nicely formatted spreadsheets full of financial data or crime stats. Yet most journalistic source material does not take the form of tables, but it comes in messy collections of documents, whether on paper, or scraped off a web site.
Building Grano started with a desire to map political and economic influences. Developing it further has made us re-examine our motivations: why would journalists want software to help map out the connections between people in politics and industry?
When software developers write code, they often use tools called IDEs, integrated development environments, that provide contextual information needed to manage the complexity of modern software. What would such a workspace look like, if it were designed for journalism?
I've worked with OpenOil in an effort to find oil contracts which have been been published as part of filings to the US stock exchange regulator, the SEC. While these contracts are not usually public, companies are required to file full contract documents as part of their annual reports under certain conditions.