EUDM dataset

Submitted by simon.cox on Mon, 13/08/2018 - 12:43
Resource Type
Description

The Energy Use Data Model will be cataloguing and publishing energy use datasets to contribute to analysis for Australia's energy supply requirements. A catalogue has been established at https://eudm-catalog.csiro.au/dataset/ but this is likely to transition out of CSIRO's management in due course, so a neutral data.gov.au address will help with data use longevity. 

Ownership expected to transition to Dept of the Environment and Energy.

This request is for a single Dataset URI to point to the EUDM catalogue as a whole which will then contain child datasets. These will have sub-URIs of this requested URU, likely something such as: http://linked.data.gov.au/dataset/eudm/72086586-770c-4d66-a3ce-18827bb496ca ("The Commercial Building Disclosure Downloadable Dataset").

http://infrastructure.data.gov.au/dataset/eudm has been allocated for the EUDM dataset under the previous Guidelines 0.3 regime.

Ownership
Owner
Resource Provided
Approval Status
Date Accepted

Comments

nicholas.car

Mon, 13/08/2018 - 21:48

Remove the trailing slash from the request - you'll get the .../dataset/eudm and then be able to apply the slash at will and this will allow you to have both a single dataset .../dataset/eudm and the register of datasets within it (anonymous register, in terms of URI) at .../dataset/eudm/

william.francis

Thu, 27/09/2018 - 19:12

Some questions regarding future implementation of datasets under this parent item:

Is there a reference for the pattern of a register of datasets and datasets to relate the items within the parent Energy Use Data Model item?

What is the background to having items in the parent dataset identified with uuids? Other datasets are typically referenced with human understandable names and acronyms.

  • Is there a reference for the pattern of a register of datasets and datasets to relate the items within the parent Energy Use Data Model item?
    • No. The Guidelines state, in Section 9 (Second-0Level Registers): "the URI arrangements for the Second-Level Register URIs need to be made by the dataset or Top-Level Register manager, however the AGLDWG can assist with implementing redirects for these subregisters within the patterning assigned to a Dataset or Top-Level Register, if requested"
    • Specifically, the Guidelines then tell us not to know anything about what dataset managers do with their dataset URI's sub parts, including how they implement registers within them.

 

  • What is the background to having items in the parent dataset identified with uuids? Other datasets are typically referenced with human understandable names and acronyms.
    • It's a dataset owner decision - in this case it's an EUDM project decision.
    • As per above, the AGLDWG's not to know how a dataset owner divvies up URIs, including the use of either names or UUIDs.
    • Being on this project I can say that the project expects to issue thousands of dataset IDs over time and didn't want to use a name that coule (likely would) change as datasets move through production so the choice, as the project saw it, was between UUIDs and simpler primary key-style identifiers (sequence numbers). The choise of UUID was made as it seemed most bullet proof.