permalink |
---|
/URI-conventions.html |
Web identifiers (URIs) for Loc-I resources must conform to AGLDWG URI Conventions.
Definitions
http://linked.data.gov.au/def/{scope}(/#){defID}
Datasets
http://linked.data.gov.au/dataset/{datasetID}
Data items
http://linked.data.gov.au/dataset/{datasetID}[/{collectionID}](/#){individualID}
Ontology | {scope} | separator | {defID} |
---|---|---|---|
ASGS | asgs |
# |
MeshBlock StatisticalAreaLevel1 StatisticalAreaLevel2 StatisticalAreaLevel3 StatisticalAreaLevel4 StateOrTerritory Country |
G-NAF | gnaf |
# |
Address StreetLocality Locality |
GeoFabric | geofabric |
# |
ContractedCatchment DrainageDivision RiverRegion |
Loc-I | loci |
# |
DataPublisher Dataset DatasetLinkingStatement Feature Linkset |
Examples of URI patterns for specific datasets:
Dataset | {datasetID} | {collectionID} | separator |
---|---|---|---|
ASGS | asgs2016 |
meshblock statisticalarealevel1 statisticalarealevel2 statisticalarealevel3 statisticalarealevel4 stateorterritory australia |
/ |
G-NAF | gnaf |
address streetLocality locality |
/ |
GeoFabric | geofabric |
contractedcatchment drainagedivision riverregion |
/ |
Meshblock-ControlledCatchment links | mb16cc |
statement |
/ |
Note: in the 2nd-last line, for the SAL6 'Australia' the individual and collection URIs use /australia/ rather than the class name i.e. /country/ . This follows a pattern inherited from the ASGS reference.
Names in the linked.data.gov.au domain must follow the AGLDWG URI Guideline.
The URI pattern for a definition (i.e. a class, concept, controlled-vocabulary or vocabulary item) is:
http://linked.data.gov.au/def/{scope}(/#){defID}
where {scope}
identifies the vocabaulary or ontology, and {defID}
the class, concept, property-type, vocabaulary item, etc.
The URI pattern for a dataset as a whole is:
http://linked.data.gov.au/dataset/{datasetID}
The URI pattern for a collection within a dataset is:
http://linked.data.gov.au/dataset/{datasetID}/{collectionID}
In Loc-I cache all individuals from a class are allocated to a collection for that class with the URI http://linked.data.gov.au/dataset/{datasetID}/{collectionID}
.
This is used for paging in pyLDAPI.
Individual items in a dataset (such as geographic features or entities) are denoted by a URI which is an extension of the dataset URI or collection URI, following the pattern:
http://linked.data.gov.au/dataset/{datasetID}[/{collectionID}](/#){individualID}
N.B. If the optional /{collectionID}
path element is included, and corresponds with a class name, then the classification of each item must be known when the identifier is assigned, and can compromise some lifecycle transitions (e.g. re-classification of an individual feature).
Furthermore, since some individuals are members of more than one class, a single {collectionID}
can make the identifier ambiguous or non-unique.
The recently released OGC API - Features - Part 1: Core specifies a set of URI patterns for accessing features. This is similar to the Loc-I/AGLDWG, but with different keywords and a slightly deeper structure.
- feature = individual item
- collection = dataset
Response structure is defined in a set of YAML patterns
Note that the response must be provided in HTML and JSON, other formats optional.
Resource + spec-link | relative URI pattern | response + example |
---|---|---|
Service | / |
Landing page |
API description | /api |
Swagger with API details |
Conformance | /conformance |
List of conformance classes implemented by this service |
Collections | /collections |
List of collections available from this service |
Specific collection | /collections/{collectionId} |
Description of a collection (but not including the members) |
Features | /collections/{collectionId}/items |
List of members of a collection |
Specific feature | /collections/{collectionId}/items/{featureId} |
Description of a feature |