First, the Problem: Apples and Oranges
This undermines the value of the clusters' work on semantic standards.
And makes it much more diffciult to repurpose data into . . .
When we consider the cost of semantic and syntactic differences throughout a humanitarian response, the impact to coordination becomes very, very large.
Good luck with that.
Instead, HXL focuses on interoperability among existing information systems in the form of an open data exchange format.
Humanitarian eXchange Language
Publish once, use everywhere
How do we leverage the standardization work done by the clusters and IASC task forces to streamline humanitarian information flows?
Build a big database and make everybody use it?
Common Export
Format
May '12
Mar '12
Feb ' 12
Aor '12
Jun '12
Dec '11
Nov '11
Jan '12
Identify existing standards
Syntactic Framework (the 'tags')
Cluster semantic content (indicators, etc)
Inter-cluster semantic content (HP, geolocation, etc)
Develop and deploy support tools
Different internal tools are ok
Different data formats are ok
Do we put individuals at risk?
How do we integrate this information?
Streamlining Humanitarian
Information Flows
Syntactic differences: different formats
Syntactic differences: two excel files but organized differently
Time is lost trying to clean and massage the data into a standard format.
Even worse for humanitarian organizations, they may have to report in different formats to their donors as well.
Dashboards
Analytical Products
Reporting Products
Post-response academic research
Semantic differences are being addressed by the clusters through the development of standard methods of measureing humanitarian needs and humanitarian response.
Semantic differences: some count apples, some count oranges, some count bananas. Everyone stores and reports them differently.
Semantic differences have a cost:
Difficult or impossible to aggregate to emergency-wide analysis
Significant resource time lost in trying to reconcile apples to oranges