Transcript Information Modelling MOLES Metadata Objects for Linking Environmental Sciences S. Ventouras Rutherford Appleton Laboratory.

Information Modelling
MOLES
Metadata Objects for Linking Environmental Sciences
S. Ventouras
Rutherford Appleton Laboratory
OUTLINE
•Introduction
oWhat MOLES is about
oMOLES v2
•MOLES v3.4
MOLES
MOLES model refers to B-Browse Type Metadata
understanding the context of data and choosing
between similar data sets
MOLES model was originally developed within the
Natural Environment Research Council DataGrid (NDG)
project to fill a missing part of the ‘metadata
spectrum’
[Lawrence et al. . doi:10.1098/rsta.2008.0237]
Currently MOLES v2.0 is deployed in CEDA
MOLES – v2
Key Entities
WHAT ?
DataEntity : which consists of aggregations of more Data entities
HOW ?
DataProductionTool: which characterizes the instruments and/or processes
available for producing data
WHERE ?
Observation Station: which characterizes the location(s) (and observers) of data
production
WHY
?
Activity: which characterizes the projects and campaigns etc., associated with data
production
These four key entities are related by the Deployment, which binds a production tool
deployed at an observation station on behalf of an activity to produce data.
Conceptual Modelling
Conceptual modelling is one of the important components in the development of any
information system.
Owing to the lack of structured approaches to system design
• the time or resources required for a system development are typically underestimated
• the system is inefficient to meet the demands of the intended end-users
•documentation is limited
• maintenance is difficult.
MOLES – v3.4
MOLES 3.4 is rooted in the ISO 19100 series of standards from the ISO/TC 211
“Harmonised Model”. In particular, it has been created:
a) following the guidance provided by ISO/TC 211 (i.e. ISO 19101, 19106 and 19109)
concept of feature ( type and instance)
a) has been formalised in the Unified Modelling Language (UML) ISO/IEC 19501, following
the guidance of ISO/TS 19103.
c) by integrating reusable modules of conceptual schemas defined within ISO 19100 series
e.g. temporal schema , metadata , Observations&Measurements etc.
User Requirements
MOLES v3.4 has been influenced by a range of environmental sciences (e.g. Earth
Observation, Meteorology, Geochemistry, etc)
MOLES – v3.4
The general structure of the model gives a central place to the concept of observation
ISO 19156
An observation is an act that results in the estimation of the value of a feature property,
and involves application of a specified procedure, such as a sensor, instrument, algorithm
or process chain.
An observation is an act associated with a discrete time instant or period through which
a number, term or other symbol is assigned to a phenomenon . The result of an observation
is an estimate of the value of a property of some feature, so the details of the observation
are metadata concerning the value of the feature property.
MOLES – v3.4
Base Standard: ISO 19156 Observations & Measurements
class Figure 2: Observ ation Co...
«FeatureType»
OM_Process
«metaclass»
GF_FeatureType
1
+theGF_FeatureType
«FeatureTyp...
GFI_Feature
+generatedObservation
1
+featureOfInterest
0..*
+carrierOfCharacteristics
1
«metaclass»
GF_PropertyType
Phenomenon
+observedProperty
{root}
+metadata
Metadata
0..*
+
+
+
+
+
parameter: NamedValue [0..*]
phenomenonTime: TM_Object
resultQuality: DQ_Element [0..*]
resultTime: TM_Instant
validTime: TM_Period [0..1]
constraints
{observedProperty shall be a phenomenon associated
with the feature of interest}
{procedure shall be suitable for observedProperty}
{result type shall be suitable for observedProperty}
{a parameter.name shall not appear more than once}
0..*
Range
«DataType»
NamedValue
+
+
name: GenericName
value: Any
0..1
«FeatureType»
OM_Observ ation
Domain
+propertyValueProvider
0..*
+procedure
ProcessUsed
«instanceOf»
1
MD_Metadata
+relatedObservation
0..*
+result
«type»
Any
{root}
Observ ationContext
+
role: GenericName
MOLES – v3.4
Key components of MOLES v3.4 include:
•Project descriptions
•The observation event itself (ISO 19156), and
•The processes used to acquire or generate the observation (ISO 19156, 19115 and 19115-2)
MOLES – V3.4 Structure
Observation
Feature Of Interest (Subject of the Observation)
-Specimen
Observed Property
Result
Process
Observation Process
-Acquisition
-Computation
Specimen Process
-Specimen Acquisition
Project
Observation Collection
Leaf packages of the MOLES3.4 schema
Observation
ass Observ ati...
«featureType»
Proj ect::MO_Proj ect
«featureType»
FeatureOfInterest::
MO_FeatureOfInterest
+subProject
0..*
ISO 19156
+propertyTypeMetadata
Metadata entity set information:
«metaclass»
:MD_Metadata
General Feature Model::
0..*
0..*
GF_PropertyType
1
{root} +propertyType
+featureOfInterest
0..1
+metadata
+ definition: CharacterString
+ memberName: LocalName
+inSupportOf
«voidable»
«featureType»
MO_Observ ation
+
+
description: CharacterString [0..1]
publicationState: MO_ObservationPublicationStateValue [0..1]
«voidable»
+ documentation: MO_Citation [0..*]
+ geographicExtent: EX_GeographicExtent [0..*]
+ identifier: MD_Identifier [0..*]
+ permission: MD_Constraints [0..1]
+ relatedParty: MO_ResponsiblePartyInfo [1..*]
+ resolution: CharacterString [0..1]
+ resultAccumulation: MO_ResultAccumulationValue [0..1]
+ status: MO_ObservationStatusValue
+ verticalExtent: EX_VerticalExtent [0..*]
+observedProperty
Domain
+
+
+
+
+
Design
+
+
+relatedObservation
0..*
«CodeList»
MO_Observ ationStatusValue
«CodeList»
Identification
information::
MD_ProgressCode
+
+
+
+
+
+
+
completed
historicalArchive
obsolete
onGoing
planned
required
underDevelopment
+relatedSamplingFeature
0..*
+
role: GenericName
specimen::PreparationStep
+
+
processOperator: CI_ResponsibleParty [0..1]
time: TM_Object
+result
1
«FeatureType»
observation::
OM_Process
«CodeList»
Maintenance information::
MD_MaintenanceFrequencyCode
lineage: LI_Lineage [0..1]
parameter: NamedValue [0..*]
observ ation::
Observ ationContext
+segment
0..*
+procedure
«CodeList»
MO_ResultAccumulationValue
0..*
0..*
ProcessUsed
annually
asNeeded
biannually
continual
daily
fortnightly
irregular
monthly
notPlanned
quarterly
unknown
weekly
«FeatureType»
specimen::SF_Specimen
«FeatureType»
samplingFeature::
SF_SamplingFeature
0..*
+relatedObservation
parameter: NamedValue [0..*]
phenomenonTime: TM_Object
resultQuality: DQ_Element [0..*]
resultTime: TM_Instant
validTime: TM_Period [0..1]
Range
«dataType»
Result::MO_Result
+
+
+
+
+
+
+
+
+
+
+
+
Intention
«informative»
+propertyValueProvider
«FeatureType»
observ ation::OM_Observ ation
+generatedObservation
citable
old
published
working
+sampledFeature
0..*
+result
+
+
+
+
1..*
Metadata
1
0..*
«codeList»
Utilities::
CEDA_PublicationStateValue
«FeatureType»
General Feature Instance::
GFI_Feature
Phenomenon
constraints
{parameter name related with the utilised procedure}
«CodeList»
MO_Observ ationPublicationStateValue
+sampledFeature
«voidable» 0..1
«type»
Records and Class Metadata::Any
{root}
«featureType»
ObservationProcess::MO_Process
«DataType»
observ ation::NamedValue
+
+
name: GenericName
value: Any
+processingDetails
0..*
«FeatureType»
specimen::
SF_Process
«featureType»
FeatureOfInterest::
MO_SpecimenProcess
+component
0..*
Result
class Result
+
+
+
+
+
«FeatureType»
observ ation::OM_Observ ation
0..*
parameter: NamedValue [0..*]
phenomenonTime: TM_Object
resultQuality: DQ_Element [0..*]
resultTime: TM_Instant
validTime: TM_Period [0..1]
+relatedObservation
0..*
+result
Range
«type»
Records and Class Metadata::Any
{root}
«featureType»
Observ ation::MO_Observ ation
+
+
description: CharacterString [0..1]
publicationState: MO_ObservationPublicationStateValue [0..1]
«dataType»
MO_Result
«voidable»
+ documentation: MO_Citation [0..*]
+ geographicExtent: EX_GeographicExtent [0..*]
+ identifier: MD_Identifier [0..*]
+ permission: MD_Constraints [0..1]
+ relatedParty: MO_ResponsiblePartyInfo [1..*]
+ resolution: CharacterString [0..1]
+ resultAccumulation: MO_ResultAccumulationValue [0..1]
+ status: MO_ObservationStatusValue
+ verticalExtent: EX_VerticalExtent [0..*]
«datatype»
Citation and responsible party information::
CI_OnlineResource
+
+
+
+
+
+
applicationProfile: CharacterString [0..1]
description: CharacterString [0..1]
function: CI_OnLineFunctionCode [0..1]
linkage: URL
name: CharacterString [0..1]
protocol: CharacterString [0..1]
+result
+
+segment
0..*
«CodeList»
Citation and responsible party
information::
CI_OnLineFunctionCode
+
+
+
+
+
download
information
offlineAccess
order
search
«dataType»
MO_OnlineResource
+
source: MO_OnlineResource [0..*]
«voidable»
+ sample: MO_OnlineResource [0..*]
serviceFunction: MO_ServiceFunctionValue [0..1]
constraints
{applicationProfile values from codelist CEDA_ApplicationProfileValue}
«codeList»
CEDA_ApplicationProfileValue
+
+
+
+
+
+
cerif
csml
csv
geosciml
netCDF
vivo
«CodeList»
MO_Serv iceFunctionValue
Feature Of Interest
class FeatureOfInterest
+relatedObservation 0..*
0..*
+propertyValueProvider
«FeatureType»
observ ation::OM_Observ ation
+featureOfInterest
0..*
«FeatureType»
General Feature
Instance::GFI_Feature
+relatedObservation
0..*
+
description: CharacterString [0..1]
«voidable»
+ identifier: MD_Identifier [0..*]
+ type: MO_FeatureOfInterestTypeValue [0..1]
1
Domain
+sampledFeature
«featureType»
MO_FeatureOfInterest
1..*
Intention
+sampledFeature
«voidable» 0..1
«informative»
Design
«FeatureType»
samplingFeature::SF_SamplingFeature
«featureType»
Observ ation::MO_Observ ation
+
+
lineage: LI_Lineage [0..1]
parameter: NamedValue [0..*]
«FeatureType»
specimen::SF_Specimen
+relatedSamplingFeature 0..*
0..*
«CodeList»
MO_FeatureOfInterestTypeValue
Feature Of Interest: Specimen
class SpecimenProcess
GFI_Feature
«FeatureType»
samplingFeature::
SF_SamplingFeature
+
+
0..*
+relatedSamplingFeature
0..*
lineage: LI_Lineage [0..1]
parameter: NamedValue [0..*]
specimen::PreparationStep
«FeatureType»
specimen::SF_Specimen
+
+
+
+
+
+
+
processOperator: CI_ResponsibleParty [0..1]
time: TM_Object
currentLocation: Location [0..1]
materialClass: GenericName
samplingMethod: SF_Process [0..1]
samplingTime: TM_Object
specimenType: GenericName [0..1]
+processingDetails
0..*
«FeatureType»
specimen::
SF_Process
«estimatedProperty»
+ samplingLocation: GM_Object [0..1]
+ size: Measure [0..1]
«featureType»
MO_SpecimenProcess
+
«Union»
specimen::Location
+
+
geometryLocation: GM_Object
nameLocation: EX_GeographicDescription
description: CharacterString [0..1]
«voidable»
+ documentation: MO_Citation [0..*]
+ identifier: MD_Identifier [0..*]
+ relatedParty: MO_ResponsiblePartyInfo [1..*]
+component
0..*
Observed Property
class Observ ablePrope...
«metaclass»
General Feature Model::
GF_PropertyType
{root}
+
+
definition: CharacterString
memberName: LocalName
«dataType»
MO_Observ ablePropertyConstraint
instanceOf
+subConstraint
0..*
+
+
description: CharacterString [0..1]
label: CharacterString
«dataType»
MO_AbsractObservableProperty
+
+
description: CharacterString [0..1]
label: CharacterString [0..*]
«dataType»
MO_CompositeObserv ableProperty
«CodeList»
MO_BasePhenomenonValue
«dataType»
MO_SimpleObserv ableProperty
+component
+
2..* +
basePhenomenon: MO_BasePhenomenonValue
constraint: MO_ObservablePropertyConstraint [0..1]
+procedure
1
«FeatureType»
observation::
OM_Process
Observation Process
‘Acquisition’ and ‘Computation’
can serve as a basis for describing
any observation chain process.
Computation
An
observation
process
«featureType»
MO_Process
Acquisition
«featureType»
Acquisition::MO_Acquisition
+
«featureType»
Computation::MO_Computation
description: CharacterString [0..1]
«voidable»
+ documentation: MO_Citation [0..*]
+ identifier: MD_Identifier [0..*]
+ instrumentPlatformPair: MO_InstrumentPlatformPair [0..*]
+ outputDescription: MO_InputOutput [0..1]
+ relatedParty: MO_ResponsiblePartyInfo [1..*]
«featureType»
MO_CompositeProcess
+ description: CharacterString [0..1]
+computationComponent
«voidable»
+ documentation: MO_Citation [0..*]
0..*
+ identifier: MD_Identifier [0..*]
+ relatedParty: MO_ResponsiblePartyInfo [1..*]
constraints
{Presence of acquisition and computation components}
+acquisitionComponent
0..*
Acquisition
A process step which interacts with the
feature of interest (e.g. an atmospheric
column, a specimen etc)
to provide a result
Computation
A process step which involves only
numerical computation
Process Acquisition
s Acquisition(MOLE...
MO_Process
«dataType»
MO_InstrumentPlatformPair
«featureType»
MO_Acquisition
+
+
+
description: CharacterString [0..1]
instrument: MO_Instrument
platform: MO_Platform
«voidable»
+ documentation: MO_Citation [0..*]
+ identifier: MD_Identifier [0..*]
+ instrumentPlatformPair: MO_InstrumentPlatformPair [0..*]
+ outputDescription: MO_InputOutput [0..1]
+ relatedParty: MO_ResponsiblePartyInfo [1..*]
UsedInstrument
UsedOperation
UsedPlatform
+operation
«voidable»
0..*
+platform
«voidable»
«featureType»
MO_Operation
+
description: CharacterString [0..1]
0..*
+instrument
«featureType»
MO_Platform
+platform
«voidable»
+
description: CharacterString [0..1]
«voidable»
«voidable»
+ documentation: MO_Citation [0..*]
+ documentation: MO_Citation [0..*]
1..* + identifier: MD_Identifier [0..*]
+ identifier: MD_Identifier [0..*]
+ location: MO_Location
+ location: MO_Location [0..1]
+ operationTime: TM_Object
+ relatedParty: MO_ResponsiblePartyInfo [1..*]
+ relatedParty: MO_ResponsiblePartyInfo [1..*]
+ type: MO_PlatformTypeValue
+ status: MO_OperationStatusValue
Aircraft
Flight
+childOperation 0..*
+childPlatform
0..*
1..*
«featureType»
MO_Instrument
+
description: CharacterString [0..1]
«voidable»
+ documentation: MO_Citation [0..*]
+ identifier: MD_Identifier [0..*]
+ realatedParty: MO_ResponsiblePartyInfo [1..*]
+ type: MO_InstrumentTypeValue
+memb
«voidab
0..*
Process Computation
class Computation
«featureType»
ObservationProcess::MO_Process
Data quality information::LI_Source
+
+
+
+
+
«dataType»
MO_InputOutput
description: CharacterString [0..1]
scaleDenominator: MD_RepresentativeFraction [0..1]
sourceCitation: CI_Citation [0..1]
sourceExtent: EX_Extent [0..*]
sourceReferenceSystem: MD_ReferenceSystem [0..1]
+
+
description: LE_Source
name: CharacterString [0..1]
«featureType»
MO_Computation
Data quality information - Imagery::LE_Source
+
+
+algorithm
processedLevel: MD_Identifier [0..1]
resolution: LE_NominalResolution [0..1]
«featureType»
MO_Processing
+
description: CharacterString [0..1]
«voidable»
+ documentation: MO_Citation [0..*]
+ identifier: MD_Identifier [0..*]
+ processingInput: MO_InputOutput [0..*]
+ processingOutput: MO_InputOutput
+ relatedParty: MO_ResponsiblePartyInfo [1..*]
+ softwareReference: MO_Citation [0..*]
Data quality information - Imagery::
LE_Algorithm
0..*
+
+
citation: CI_Citation
description: CharacterString
Project
Definition
An identifiable activity designed to accomplish a set of objectives.
Description
A typical sequence of data capturing involves one or more projects under which a number of
further activities are undertaken, using appropriate tools and methods to produce the datasets.
EXAMPLE 1 The UK Surface Ocean /Lower Atmosphere Study (UK SOLAS) was a Directed
Mode programme of the Natural Environment Research Council (NERC) . The overall aim of UK
SOLAS was to advance understanding of environmentally significant interactions between the
atmosphere and ocean, focusing on material exchanges that involve ocean productivity,
atmospheric composition and climate.
NOTE A project may be a member of a complex of parent- and sub-projects.
Observation Collection
Definition
A collection of existing observations which has a title and a reason for existence.
Description
NOTE The observation results can be appeared in collections which are
organised with significantly more flexibility than would be done if one used the
original project alone.
Project – Observation - Observation Collection
MOLES v3.4 - Overview
Observation Collection
(DataEntity)
Project
(Activity)
Observation Process
(DataProductionTool)
Observation
(Deployment)
Specimen Process
Implementation
 From UML diagrams to XMI (From Enterprise Architect) then
XML/GML
- FullMoon (CSIRO) , NewMoon ( CEDA)
DB
- CEDA activity ,ongoing
 OWL-DL
- ISO 19152?