https://purl.dataone.org/odo/MOSAIC_00012000

The "_MOSAiC Specific Term" class is a container to organize and isolate the terms that are most frequently used to describe the various components of the MOSAiC Expedition. Since other established ontologies are imported into this one, a number of extraneous, non-MOSAiC relevant, and unused terms may be present and clutter the presentation. Hopefully, simply presenting this one Class for reference will enable users to enjoy the main advantages of using and exploring this Ontology. Definitions or descriptions of these term as described on the Pangaea website are provided in the Annotation fields associated with each MOSAIC term. The main patterns semantically modeled here are as such: There are 9 Campaigns, which correspond most closely to a "Cruise", or "Leg" although campaigns can involve stationary or aerial platforms. Each Campaign has a Basis, which is typically a Research Vessel (e.g. the Polarstern) or Aircraft (Polar 5 & 6). Each Campaign has one or more Chief Scientists, and a Research Location. The Basis of a Campaign, and its hosted Events, are indicated by the first two initials in the labels of the Campaigns and Events-- e.g. PS122/1 is the first (indicated by the '/1') Campaign (or "Leg") of the 122'nd voyage of the Polarstern (Basis). PS122/2 would be the second Campaign of the 122'nd voyage of the Polarstern, etc. Again-- these "Campaigns" are irregularly referred to elsewhere as "Legs" or "Cruises"-- with their own unique Cruise numbers. Campaigns "host" numerous Events, meaning those Events occurred during that Campaign. Events bear cryptic labels that map to distinct Sensor or Sampling efforts that result in the collection of data. Events extend on the naming scheme for Campaigns, with a numbering system that appears to be temporally sequenced. For example, Event PS122/1_5-10 probably commenced before PS122/1_5-100. (Note that this temporal information is not captured in the Ontology as of version 1.001.) Each Event results in the collection of data by some Sensor or Sampling Device. These "Methods and Devices" are organized under the "Method/Device" hierarchy in the MOSAiC Ontology, that includes the names of each type of Sensor/Sampling device as SubClasses. Each Method/Device SubClass can further have one to several more specifically named devices that perform that type of Measurement. For example, the "Acoustic Doppler Current Profiler Device" SubClass contains 6 specific types of ADCP sensor instruments, modeled as Instances with their "Device Long Name". The MOSAiC team associated each Sensor/Sampling device with a "Short Name" as well. Most "Long Name" Sensor/Samplers have a only single "Short Name" associated with them (sometimes identical to the "Long Name"), but this is not always the case. For example, Device with "Long Name" = "particle size magnifer" has two Device "Short Names" associated with it-- "PSM_UHEL1" and "PSM_UHEL2". Method/Devices are associated with Events via their "Device Long Name", through the predicate "has deployment". Details about inverse and equivalent properties that are represented in the Ontology, providing other potential ways to discover connections, are too detailed to discuss here. Consult the Ontology. Associated with each "Short Name" in the Ontology is a URI on the Alfred Wegener Institue website, pointing to further detailed information about that Sensor, e.g. this one for one of the ADCP devices: https://hdl.handle.net/10013/sensor.3bf53c89-fbed-4486-b5f3-2856fcd76def A Dataset is the outcome/output of an Event. Every dataset contains measurements that can be linked to some Event that used some Device (with most detailed description provided by the URI assocated with its "Short Name"); and is from some Campaign, that was performed on some Basis with some Chief Scientist(s), and some Research Location. (For demonstration purposes, this Ontology contains a single reference to a test dataset instance, findable by searching for "urn" -- where these assocations can be seen. We could link such datasets to specific Events, but since the Events are manifested at level of measurement values in the dataset, these associations are made evident through the Arctic Data Center search portal: http://arcticdata.io, where the PROVO "wasGeneratedBy" predicate is used.) Comments or questions to Mark Schildhauer (schild@nceas.ucsb.edu).

http://orcid.org/0000-0003-0632-7576

2021-07-02T06:57:47Z

_MOSAiC Specific Term

odo:MOSAIC_00012000

_MOSAiC Specific Term

http://www.w3.org/2002/07/owl#Thing