Open Data Model

Henare Degan edited this page Mar 10, 2011 · 1 revision

Table of Contents

Open Data Model

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.

Initial Data Gathering

At the moment I'm trawling the web for all the examples of 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 data APIs you find with the hashtag #datagovau so we can start to build a list similar to

Related Links

Related Systems

As far as I can see the existing systems are;

  • Open Australia
  • myrepresentatives
  • fixmystreet
  • tweetMP

High Level Starting point

  • Federal Government
  • State Governments
  • Local Governments
  • Geographic locations
  • People
  • Groups
  • Issues
  • Messages
I have a bunch of ideas on the key nouns and verbs I think it would be good to start the modelling from and some important concepts that would help make this model tangible, implementable and open ... but I want to throw this open for group discussion first to get general agreement that this is a problem that needs to be solved before we get to that level. I'd also like to clarify how this relates to Open Australia as I don't want to create a tangent that is a distraction from its core goals.

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 [1]
  • Geographic bounds
  • Chamber name
  • Division name
  • Year of addition (This would be the first year from which this data is
valid. A subsequent entry with the same details but a later year of addition would supersede but not replace the entry)

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).

Related Tickets

  • Re: OA Taxonomy and URLs -
You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.
Press h to open a hovercard with more details.