About LongSpine

This interface to the models and data assembled by the Longitudinal Spine of Government Functions project (LongSpine) which ran in the 2018/2019 Financial Year as part of CSIRO's Data61's Platforms for Open Data (PfOD) series of projects has been created to keep all of its outputs in one place and to demonstrate some of the capabilities that the project facilitated.

§ Project Aim

The aim of LongSpine was to make information about government functions and structure more available and better the better integration of other sources of information on topics such as staffing, budgets and reporting. A key part of the aim was to allow changes in structure and function to be tracked over time.

The project did not seeking to replace any function classification used in the Australian Government, rather it sought to create linkages between functions from different function classification systems and other datasets, building them into a spine.

While the project aimed to demonstrate improved capabilities by implementing a spine, the demonstration of which is in this website, it had to create or enhance harmonised models of its component datasets and vocabularies (see the Models & Data pages) to make them work together and they may be used independently of the spine.

§ Future of LongSpine

There are several small projects in the 2019/2020 Financial Year which are extending on this work. Also, it is possible a LongSpine 2 may be initiated within a year of this project ending (June 2019).

This spine demonstration will be maintained for an un-specified amount of time, likely the 2019/2020 Financial Year. The component models are published already (see the Models page) via the Australian Government Linked Data Working group with CSIRO providing interim technical maintenance. CSIRO is seeking to hand model maintenance over to the agencies that own the systems modelled (National Archives of Australia, the Department of Finance and the Australian Bureau of Statistics)

The datasets built (original data interpreted as RDF via use of the dataset's models) are one-time builds so they are published and available on-going but they are static and will not change are the underlying data does. It is hoped that live interpretations of the underlying datasets may produce continually up-to-date RDF versions of them in the future.

§ Team

The LongSpine project team in 2018/2019 and their project roles was: