Join GitHub today
Open Data Model
Table of Contents
We've got a number of very promising different systems in play at the moment, but if we try to start connecting them together things are going to get slow and painful pretty fast if we aren't speaking a common language. Adam Kennedy (via email "Re: Identifying things" - Wed, 17 Jun 2009 20:09:53 +1000)
I think this point is spot on and was also highlighted during the Open Data discussions at #publicsphere 2 in Canberra on Monday 22nd June.
At the moment I'm trawling the web for all the examples of gov.au based data models starting from AGIMO and working my way outwards. I'll add the links here and hopefully this will provide a useful resource for building a more generic and useful Open Data Model.
It would also be great if you could tweet any examples of gov.au data APIs you find with the hashtag #datagovau so we can start to build a list similar to http://data.gov.
- US Gov Org Chart : http://blog.dataunbound.com/2009/06/18/a-first-pass-at-an-org-chart-for-the-us-federal-government/
- Election Markup Language & related standards : http://www.oasis-open.org/specs/#eml5.0
As far as I can see the existing systems are;
- Open Australia
- Federal Government
- State Governments
- Local Governments
- Geographic locations
However, without agreement on this Open Data Model I think there will be a lot more overlaps, wasted development and discussion.
Also - here's the link to my initial email to the OA dev list.
Further thoughts: There is a range on information that needs to be expressed. This includes
- Level of govt
- Jurisdiction 
- Geographic bounds
- Chamber name
- Division name
- Year of addition (This would be the first year from which this data is
We would also like to recognise the different objects - chamber, division, ward, etc.
Right now we are leaning towards using URIs. So, for the Federal House Of Representatives after the last general Federal election we would have something like:
And the Federal electoral division of Lowe would be:
In this way the Senate would be:
and the NSW block in the Senate:
At a state level you could have
Please note - the names used here are mostly placeholders. They may not be ideal for the final specification (if the spec wants to easily support things like having the paths be filesystem-friendly or what not).
- Re: OA Taxonomy and URLs - http://tickets.openaustralia.org/browse/OA-226