Queries take data form different areas and are more user friendly than using endpoints. Output is usable without further manipulation.
...
The query parameter in the request body allows the data requested from any endpoint to be filtered according to the parameters specified. For example:
From the * endpoint, it is possible to retrieve only sites which contain a feature of interest (FOI) = “plant occurrence”
From the * endpoint, it is possible to retrieve observations which contain a parameter = “basal area”
...
"http://linked.data.gov.au/dataset/ausplots"is the identifier of 1 ausplots in TERN Surveillance Monitoring (a single instance of the class Dataset, in the example, TERN Surveillance Monitoring.Dataset class)
"http://linked.data.gov.au/def/tern-cv/b311c0d3-4a1a-4932-a39c-f5cdc1afa611"is the identifier of “plant occurrence” (a * within the class Concept, in the example, the Concept “plant occurrence” Concept class that belongs to the Concept Scheme “Feature types”).
This design offers multiple benefits (e. g., Because a URI is a unique and immutable identifier for a specific concept, we can easily modify the vocabulary by changing the label, the description or any other property of the concept without having to update the data). The only drawback to using URIs is that URIs they are usually not human readable.
...