The mapping described here are for old CORVEG system and mapping to new CORVEG is available in CORVEG-QBEIS Tables Overview .
This alignment relates the (Queensland) CORVEG logical model to the O&M conceptual model.
CORVEG reports a large set of observations of different properties of a site. The total number of potentially observed properties is large. The description of the site itself is grouped into thematic groups named Geology
, Disturbance
, Situation
etc. The description of the vegetation is organized by strata. The description of the taxa at a site is generally organized by taxon, and also by strata.
Following the standard observation model:
every 'value' is recorded as the hasResult
of an Observation
every Observation
is related to a FeatureOfInterest
in the context of TERN Plot Ontology this is usually a Site, or a Site Strata Table, or a Site Tax Table, or an OrganismOccurrence.
the type of value is recorded as the Observation's observedProperty
. It is taken from a controlled-vocabulary of observable properties
Observations may be grouped in an ObservationCollection which is a set of observations with (usually) a common hasFeatureOfInterest
and phenomenonTime
each individual Observation
is nested as a ssn-ext:hasMember
of the ObservationCollection
The templates on the TERN Plot Ontology description illustrate the application pattern.
Since the observation type is indicated by properties of the observation (i.e. the observedProperty
and hasFeatureOfInterest
), the generic classes Observation
and ObservationCollection
can be used for all observed data. The controlled vocabulary of ObservableProperties
is maintained separately, and can be updated frequently, without having to touch the main data structures.
We could have defined a sub-class of ObservationCollection
for each CORVEG table (i.e. thematic group), but this would tie the ontology directly to CORVEG, which is undesirable because
the CORVEG conceptual model does not match all the data submitted by the various providers, while TERN-plot - which is a lightly extended SSN/SOSA model - is flexible enough to cope
too much specialization/customization compromises compatibility with observation data from other sources or providers, or from other discipline areas
Where an ObservationCollection
does correspond with a row from a CORVEG table, the name of the table can be indicated using the dct:type
property. This may assist discovery and processing by users or applications who are familiar with CORVEG. A list of observation groups is maintained as a TERN-plot 'controlled vocabulary'.
Detailed implementation of CORVEG entities in RDF can be found under Table Mappings.
CORVEG controlled vocabularies can be viewed at the persistent URI http://linked.data.gov.au/def/corveg-cv.
Observation results are encoded using a set of standard data-Datatypes