The core elements of an abstract process from which all major elements of SensorML are derived. SensorML is an OGC Standard. Copyright (c) 2019 Open Geospatial Consortium. To obtain additional rights of use, visit http://www.opengeospatial.org/legal/ . A feature with generic metadata which further clarifies the object and supports object discovery. A property that allows one to extend a document using a schema in a different namespace from the current schema. Short keywords describing the context of this document to aid in discovery. Identifiers useful for discovery of the process (e.g. short name, mission id, wing id, serial number, etc.) Classifiers useful for discovery of the process (e.g. process type, sensor type, intended application, etc.) The time instance or time range during which this instance description is valid. Overall security tagging of process description; individual tagging of properties can be done using extension element. Legal constraints applied to this description (e.g. copyrights, legal use, etc.) Useful properties of this process that do not further qualify the output values (e.g. component dimensions, battery life, operational limits, etc). Properties that further clarify or quantify the output of the process (e.g. dynamic range, sensitivity, threshold, etc.). These can assist in the discovery of processes that meet particular requirements. Persons or responsible parties that are relevant to this process (e.g. designer, manufacturer, expert, etc.) Additional external online documentation of relevance to this process (e.g. user's guides, product manuals, specification sheets, images, technical papers, etc.) A collection of time-tagged events relevant to this process. A tag that identifies the language (e.g. english, french, etc.) for the overall document using a two-letters code as defined by ISO 639-1. The general base model for any process. sml:AbstractProcess A reference to a base process from which this process inherits properties and constraints (e.g. original equipment manufacturer's model description, generic equation, etc.). The uniqueID of the referenced process must be provided using the xlink:title attribute while the URL to the process description must be provided by the xlink:href attribute. Value settings that further constrain the properties of the base process. A collection of features relevant to a process (e.g. the Gulf of Mexico, the White House, the set of all Fibonacci Numbers, etc.); can also support a sampling feature. The primary purpose of the Features of Interest is to support discovery. The list of data components (and their properties and semantics) that the process will accept as input; In the standard linear equation y=mx+b; x is the input, m and b are the parameters, and y is the output. The list of data components (and their properties and semantics) that the process will accept as output; In the standard linear equation y=mx+b; x is the input, m and b are the parameters, and y is the output. The list of data components (and their properties and semantics) that the process will accept as parameters; In the standard linear equation y=mx+b; x is the input, m and b are the parameters, and y is the output. A collection of parameters that can be set at once through the selection of a particular predefined mode. An optional property that allows one to reference the process instance in an online ontology or dictionary. The value of the property must be a resolvable URI. A time tagged Event with description and relevant property values. keywords useful for discovery of the event Identifiers relevant to the event Type of event (useful for discovery) Persons or parties relevant to this event Additional documentation relevant to this event DateTime of the event Properties of interest to the event (e.g. calibration values, condition category, error codes, etc) Configuration settings adjusted during event online dictionary or ontology which defines a collection of possible keywords a short word or phrase that will aid in discovery of this object The DataInterface description provides information sufficient for "plug-and-play" access to and parsing of the data stream or file at the particular IO port. The definition of the digital data components and encoding accessed through the data interface. A set of property values that define the type and configuration of a data interface (e.g. the port settings of an RS232 interface). A physical property that can be observed and possibly measured (e.g. temperature, color, position). An ObservableProperty has unambiguous definition, but does not have units of measure. Either a Time Instant or Time Period A single digital number (DN) or aggregate of DNs that represent the value of some property. Single data components can be of type Quantity, Count, Category, Boolean, Text, or Time; these can be aggregated in records, arrays, vector, and matrices. A physical property of the environment that can be observed by an appropriate detector (e.g. temperature, pressure, etc.); Typically,an ObservableProperty serves as the input of a detector and the output of an actuator. A data interface serves as an intermediary between the pure digital domain and the physical domain where DN are encoded into a format and perhaps transmitted through physical connections using some well-defined protocol. The DataInterface element allows one to define the components, semantics, encoding, connections, and protocol at an input, output, or parameter port.