information modelling moles metadata objects for linking environmental sciences s. ventouras

Information Modelling

MOLESMetadata Objects for Linking Environmental Sciences

S. Ventouras Rutherford Appleton Laboratory

OUTLINE

•Introduction

o What MOLES is abouto MOLES v2

•MOLES v3.4

MOLES

MOLES model refers to B-Browse Type Metadataunderstanding 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

http://dx.doi.org/10.1098/rsta.2008.0237

Key Entities

DataEntity : which consists of aggregations of more Data entities

DataProductionTool: which characterizes the instruments and/or processes available for producing data

Observation Station: which characterizes the location(s) (and observers) of data production 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.

W H A T ?

MOLES – v2

H O W ?

W H E R E ?

W H Y ?

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)

b) 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. EarthObservation, Meteorology, Geochemistry, etc)

MOLES – v3.4

The general structure of the model gives a central place to the concept of observation

ISO 19156An 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: Observation Co...

«FeatureType»OM_Observation

+ 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}

«FeatureType»OM_Process

«FeatureTyp...GFI_Feature

MD_Metadata

«type»Any

{root}

«metaclass»GF_FeatureType

«metaclass»GF_PropertyType

{root}

«DataType»NamedValue

+ name: GenericName+ value: Any

ObservationContext

+ role: GenericName

+propertyValueProvider

0..*

Domain+featureOfInterest

1

0..* +relatedObservation0..*

+generatedObservation 0..*

ProcessUsed

+procedure1

Phenomenon

+observedProperty

1

Metadata

+metadata 0..1

«instanceOf»

+result

Range

+carrierOfCharacteristics

0..*

+theGF_FeatureType 1

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 pkg PackageDependencies:MOL...

«Application Schema»MOLES3.4

(from Model)

«leaf»Project

+ MO_Project+ MO_ProjectPublicationStateValue+ MO_ProjectStatusValue

«leaf»ObservationCollection

+ MO_ObservationCollection+ MO_ObservationCollectionPublicationStateValue

«leaf»ObservableProperty

+ MO_AbsractObservableProperty+ MO_BasePhenomenonValue+ MO_CompositeObservableProperty+ MO_ObservablePropertyConstraint+ MO_SimpleObservableProperty

«leaf»Acquisition

+ CEDA_PlatformTypeValue+ MO_Acquisition+ MO_Instrument+ MO_InstrumentPlatformPair+ MO_InstrumentTypeValue+ MO_Location+ MO_Operation+ MO_OperationStatusValue+ MO_Platform+ MO_PlatformTypeValue

«leaf»Computation

+ MO_Computation+ MO_InputOutput+ MO_Processing

«leaf»Utilities

+ CEDA_PublicationStateValue+ CEDA_RoleValue+ ISO19115_CI_RoleCode+ MO_Citation+ MO_Individual+ MO_Organisation+ MO_Party+ MO_ResponsiblePartyFunctionValue+ MO_ResponsiblePartyInfo

«leaf»Observ ationProcess

+ MO_CompositeProcess+ MO_Process

«Leaf»FeatureOfInterest

+ AGHGP_FeatureOf+ MO_FeatureOfInterest+ MO_FeatureOfInterestTypeValue+ MO_SpecimenProcess

«leaf»Result

+ CEDA_ApplicationProfileValue+ MO_OnlineResource+ MO_Result+ MO_ServiceFunctionValue

«leaf»Observ ation

+ MO_Observation+ MO_ObservationPublicationStateValue+ MO_ObservationStatusValue+ MO_ResultAccumulationValue

«import»

«import»

«import»«import»

«import»

«import»«import»

«import»

«import»

«import»

Observation class Observati...

ISO 19156

«featureType»Project::MO_Project

«featureType»ObservationProcess::MO_Process

«FeatureType»observation::OM_Observation


«FeatureType»General Feature Instance::

GFI_Feature

«FeatureType»observation::OM_Process

«FeatureType»samplingFeature::

SF_SamplingFeature

+ lineage: LI_Lineage [0..1]+ parameter: NamedValue [0..*]

«featureType»MO_Observation

+ 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..*]

constraints{parameter name related with the utilised procedure}

observation::ObservationContext

+ role: GenericName

«DataType»observation::NamedValue

+ name: GenericName+ value: Any

«FeatureType»specimen::SF_Specimen

«FeatureType»specimen::SF_Process

specimen::PreparationStep

+ processOperator: CI_ResponsibleParty [0..1]+ time: TM_Object

«featureType»FeatureOfInterest::

MO_SpecimenProcess

Metadata entity set information::MD_Metadata

«metaclass»General Feature Model::

GF_PropertyType{root}

+ definition: CharacterString+ memberName: LocalName

«type»Records and Class Metadata::Any

{root}

«codeList»Utilities::

CEDA_PublicationStateValue

+ citable+ old+ published+ working

«dataType»Result::MO_Result

«featureType»FeatureOfInterest::

MO_FeatureOfInterest

«CodeList»Maintenance information::

MD_MaintenanceFrequencyCode

+ annually+ asNeeded+ biannually+ continual+ daily+ fortnightly+ irregular+ monthly+ notPlanned+ quarterly+ unknown+ weekly

«CodeList»Identification information::

MD_ProgressCode

+ completed+ historicalArchive+ obsolete+ onGoing+ planned+ required+ underDevelopment

«CodeList»MO_ObservationPublicationStateValue

«CodeList»MO_ResultAccumulationValue

«CodeList»MO_ObservationStatusValue

+result

+sampledFeature«voidable» 0..1

+segment0..*

+result

Range

+propertyTypeMetadata

0..*

+propertyType

0..*

+component0..*

+processingDetails 0..*

+inSupportOf«voidable»

+subProject0..*

Intention

+sampledFeature1..*

«informative»

0..* +relatedSamplingFeature0..*

Design

+relatedObservation0..*

Metadata

+metadata0..1

Phenomenon

+observedProperty 1

+generatedObservation0..*

ProcessUsed

+procedure 1

0..*



0..*

Domain

+featureOfInterest1

Result class Result

«dataType»MO_Result

+ source: MO_OnlineResource [0..*]

«voidable»+ sample: MO_OnlineResource [0..*]

«featureType»Observation::MO_Observation

+ 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..*]



«type»Records and Class Metadata::Any

{root}

«dataType»MO_OnlineResource

+ serviceFunction: MO_ServiceFunctionValue [0..1]

constraints{applicationProfile values from codelist CEDA_ApplicationProfileValue}

«codeList»CEDA_ApplicationProfileValue

+ cerif+ csml+ csv+ geosciml+ netCDF+ vivo

«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]

«CodeList»Citation and responsible party

information::CI_OnLineFunctionCode

+ download+ information+ offlineAccess+ order+ search

«CodeList»MO_ServiceFunctionValue

+segment0..*

+result

0..*


+resultRange

Feature Of Interest class FeatureOfInterest


«FeatureType»samplingFeature::SF_SamplingFeature

+ l ineage: LI_Lineage [0..1]+ parameter: NamedValue [0..*]


«featureType»MO_FeatureOfInterest

+ description: CharacterString [0..1]

«voidable»+ identifier: MD_Identifier [0..*]+ type: MO_FeatureOfInterestTypeValue [0..1]

«featureType»Observ ation::MO_Observation

«FeatureType»General Feature

Instance::GFI_Feature

«CodeList»MO_FeatureOfInterestTypeValue

Design

+relatedObservation

0..*

0..*

+relatedSamplingFeature 0..*

«informative»

Intention

+sampledFeature 1..*


0..*Domain

+featureOfInterest

1

0..*+relatedObservation 0..*

+sampledFeature«voidable» 0..1

Feature Of Interest: Specimen class SpecimenProcess


+ currentLocation: Location [0..1]+ materialClass: GenericName+ samplingMethod: SF_Process [0..1]+ samplingTime: TM_Object+ specimenType: GenericName [0..1]

«estimatedProperty»+ samplingLocation: GM_Object [0..1]+ size: Measure [0..1]

GFI_Feature

«FeatureType»samplingFeature::

SF_SamplingFeature

+ lineage: LI_Lineage [0..1]+ parameter: NamedValue [0..*]

«FeatureType»specimen::

SF_Process

specimen::PreparationStep

+ processOperator: CI_ResponsibleParty [0..1]+ time: TM_Object

«featureType»MO_SpecimenProcess


«voidable»+ documentation: MO_Citation [0..*]+ identifier: MD_Identifier [0..*]+ relatedParty: MO_ResponsiblePartyInfo [1..*]

«Union»specimen::Location

+ geometryLocation: GM_Object+ nameLocation: EX_GeographicDescription

+processingDetails

0..*

0..*+relatedSampl ingFeature0..*

+component0..*

Observed Property class Observ ablePrope...

«dataType»MO_AbsractObservableProperty

+ description: CharacterString [0..1]+ label: CharacterString [0..*]

«dataType»MO_SimpleObserv ableProperty

+ basePhenomenon: MO_BasePhenomenonValue+ constraint: MO_ObservablePropertyConstraint [0..1]

«dataType»MO_Observ ablePropertyConstraint

+ description: CharacterString [0..1]+ label: CharacterString

«dataType»MO_CompositeObserv ableProperty

«metaclass»General Feature Model::

GF_PropertyType{root}

+ definition: CharacterString+ memberName: LocalName

«CodeList»MO_BasePhenomenonValue

instanceOf

+subConstraint0..*

+component

2..*

Observation Process

Acquisition

Computation An observation

process

‘Acquisition’ and ‘Computation’ can serve as a basis for describing any observation chain process.

AcquisitionA process step which interacts with the feature of interest (e.g. an atmospheric column, a specimen etc) to provide a result

ComputationA process step which involves only numerical computation

class Observ ationProce...

observ ation::OM_Observ ation

+ + + + +

observation::OM_Process

«featureType»MO_Process

«featureType»Acquisition::MO_Acquisition


«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


«voidable»+ documentation: MO_Citation [0..*]+ identifier: MD_Identifier [0..*]+ relatedParty: MO_ResponsiblePartyInfo [1..*]

constraints{Presence of acquisition and computation components}

«featureType»Computation::MO_Computation

0..*+relatedObservation0..*

+generatedObservation 0..*

ProcessUsed

+procedure 1

+computationComponent

0..*

+acquisitionComponent 0..*

class Acquisition(MOLE...

«featureType»MO_Operation


«voidable»+ documentation: MO_Citation [0..*]+ identifier: MD_Identifier [0..*]+ location: MO_Location+ operationTime: TM_Object+ relatedParty: MO_ResponsiblePartyInfo [1..*]+ status: MO_OperationStatusValue

«featureType»MO_Instrument


«voidable»+ documentation: MO_Citation [0..*]+ identifier: MD_Identifier [0..*]+ realatedParty: MO_ResponsiblePartyInfo [1..*]+ type: MO_InstrumentTypeValue

«featureType»MO_Platform


«voidable»+ documentation: MO_Citation [0..*]+ identifier: MD_Identifier [0..*]+ location: MO_Location [0..1]+ relatedParty: MO_ResponsiblePartyInfo [1..*]+ type: MO_PlatformTypeValue

Identification information::MD_ProgressCode

+ completed+ historicalArchive+ obsolete+ onGoing+ planned+ required+ underDevelopment

CEDA_PlatformTypeValue

+ aircraft+ balloon+ geostationaySatell ite+ groundStation+ orbitalSatell ite+ spaceStation+ vehicle+ watercraft

MO_Location

+ geometryLocation: GM_Object [0..1]+ nameLocation: EX_GeographicDescription [0..1]

MO_Process

«featureType»MO_Acquisition


«voidable»+ documentation: MO_Citation [0..*]+ identifier: MD_Identifier [0..*]+ instrumentPlatformPair: MO_InstrumentPlatformPair [0..*]+ outputDescription: MO_InputOutput [0..1]+ relatedParty: MO_ResponsiblePartyInfo [1..*]

«dataType»MO_InstrumentPlatformPair

+ instrument: MO_Instrument+ platform: MO_Platform

MO_InstrumentTypeValue+platform«voidable»

1..*

+childOperation 0..*

+member«voidable»0..*

+childPlatform0..*

UsedPlatform

+platform«voidable» 0..*

UsedOperation

+operation«voidable» 0..*

UsedInstrument

+instrument 1..*

Process Acquisition

Flight Aircraft

Process Computation class Computation

Data quality information - Imagery::LE_Algorithm

+ citation: CI_Citation+ description: CharacterString

Data quality information - Imagery::LE_Source

+ processedLevel: MD_Identifier [0..1]+ resolution: LE_NominalResolution [0..1]

Data quality information::LI_Source

+ description: CharacterString [0..1]+ scaleDenominator: MD_RepresentativeFraction [0..1]+ sourceCitation: CI_Citation [0..1]+ sourceExtent: EX_Extent [0..*]+ sourceReferenceSystem: MD_ReferenceSystem [0..1]

«featureType»MO_Computation

«featureType»ObservationProcess::MO_Process

«featureType»MO_Processing


«voidable»+ documentation: MO_Citation [0..*]+ identifier: MD_Identifier [0..*]+ processingInput: MO_InputOutput [0..*]+ processingOutput: MO_InputOutput+ relatedParty: MO_ResponsiblePartyInfo [1..*]+ softwareReference: MO_Citation [0..*]

«dataType»MO_InputOutput

+ description: LE_Source+ name: CharacterString [0..1]

+algorithm

0..*

Project

DefinitionAn 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

DefinitionA collection of existing observations which has a title and a reason for existence.

DescriptionNOTE 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 Project(Activity)

Observation(Deployment)

Observation Process(DataProductionTool)

Specimen Process

Observation Collection(DataEntity)

Implementation

From UML diagrams to XMI (From Enterprise Architect) then

XML/GML

- FullMoon (CSIRO) , NewMoon ( CEDA)

DB - CEDA activity ,ongoing

OWL-DL

- ISO 19152?

information modelling moles metadata objects for linking environmental sciences s. ventouras

Documents