Process Metadata Group Change Requests | OGC

S e n s o r M o d e l L a n g u a g e O G C 0 7 - 0 0 0

8.11 Process Metadata Group

All processes and process method descriptions in SensorML provide five optional groups of metadata through the metadataGroup.. As previously discussed, these metadata are primarily to support discovery of resources, qualification of process results, and assistance to humans. These metadata include identifiers, classifiers, constraints, capabilities, properties, contacts, documentation sources, and history. Each of these groups will be discussed in detail below. Figure 9.7. Conceptual model for the metadata group in SensorML 8.11.1 General Information Identifier and Classifier The generalInfo group includes three properties, identifier, classifier, and description.

8.11.1.1 identifier

The identifier property take a Term as its value. The Term has a definition attribute that specifies in this case the type of identifier, while the codeSpace attribute specifies that the value of the identifier is according to the rules or enumerations of a particular authority. For example, an identifier with a definition of “urn:ogc:def:identication:tailNumber” might take “N291PV” as its value based on the codespace of a US Air Force rules dictionary. Other possible definitions for identifiers might include, for example, shortName, longName, acronym, serialNumber, manufacturerID, or partNumber. The identification properties should be considered as information suitable for the discovery process. Figure 9.8. Conceptual model for Term used in identifier and classifier properties. Copyright © 2007 Open Geospatial Consortium, Inc. All Rights Reserved. 61 S e n s o r M o d e l L a n g u a g e O G C 0 7 - 0 0 0

8.11.1.2 classification

The classification property provides a list of possible classifiers that might aid in the rapid discovery of processes, sensors, or sensor systems. Definitions for a classifier Term might include, for instance, sensorType, observableType, processType, intendedApplication, or missionID. The classification properties should be considered as information suitable for the discovery process.

8.11.2 Constraints

A SensorML resource description can be constrained by three properties: national and international securityConstraints, validTime, and legalConstraints. These constraints may or may not be considered as information suitable for the discovery process.

8.11.2.1 securityConstraints

The model for specification of security constraints may be based on such security definitions as the Security Banner Marking model of the Intelligence Community Information Security Marking IC ISM Standard.

8.11.2.2 validTime

The validTime property indicates the time instance or time range over which this process description is valid. Time constraints are important for processes in which parameter values or operation modes may change with time.

8.11.2.3 legalConstraints

The legalConstraints property is based on ISO 19115 and specifies whether Privacy Act, Intellectual Property Rights, or copyrights apply to the content of the process description or its use. In addition to the Boolean attributes, privacyAct, intellectualPropertyRights, and copyrights, legalConstraints take documentation as its value, thereby providing for more explicit description of the legal constraints. Figure 9.9. Model for Rights definitions used in legalConstraints. 8.11.3 Properties Capabilities and Characteristics Any SensorML resource e.g., a process, sensor, sensor system may possess various characteristics or capabilities that are useful for its discovery. The characteristics and capabilities properties take a RecordType as their value, which allows for the grouping of various properties using SWE Common DataRecord, for example. Copyright © 2007 Open Geospatial Consortium, Inc. All Rights Reserved. 62 S e n s o r M o d e l L a n g u a g e O G C 0 7 - 0 0 0

8.11.3.1 capabilities

The capabilities property is intended for the definition of parameters that further qualify the output of the process, component, or system for the purpose of discovery. For example, a particular remote sensor on a satellite might measure radiation between a certain spectral range e.g. 700 to 900 nanometers at a particular ground resolution e.g. 5 meter, and with a typical spatial repeat period e.g. 3.25 – 4.3 days. Alternatively, a particular process might have certain quality constraints. Any process may have certain limits e.g., operational and survivable limits, based on physical or mathematical conditions. Once a user has identified candidate sensors based on the classifiers described above, the capabilities parameters might prove useful for further filtering of processes or sensor system during this discovery process. The capabilities properties should be considered as information suitable for the discovery process.

8.11.3.2 characteristics

A physical or non-physical process may have characteristics that may not directly qualify the output. For example, a component may have certain physical measurements such as dimensions and weight, and be constructed of a particular material. A component may have particular power demands, or anticipated lifetime. The characteristics properties may or may not be considered as information suitable for the discovery process.

8.11.4 References Contacts and Documentation

The references group provides contact and documentation properties that are useful for human consideration. The contact property takes two possible values for contact information: Person, which is based on the IC Department of Defense Discovery Metadata Specification DDMS, and ResponsibleParty, which is based on ISO 19115. The documentation property provides a reference description and URI to an online resource e.g., specification documentation, peer-reviewed algorithm literature, etc..

8.11.5 History

Within SensorML, the history of a resource can be provided through a collection of Event objects. These are provided within an EventList that serves as the value of the history property. Events might for instance, specify calibration or maintenance history of a sensor, or changes to an algorithm within a process. Figure 9.10. Conceptual model for Event. Copyright © 2007 Open Geospatial Consortium, Inc. All Rights Reserved. 63 S e n s o r M o d e l L a n g u a g e O G C 0 7 - 0 0 0

8.12 SensorML as Applied to Sensors