Editing Example 5: Using the Reference Model to explain the technology details of common services (WP4 practices)

Jump to: navigation, search

Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision Your text
Line 64: Line 64:
 
=== <span style="color: #BBCE00">Information Viewpoint</span> ===
 
=== <span style="color: #BBCE00">Information Viewpoint</span> ===
  
Analysing the environmental data schema results in identifying the common structural concepts, the ENVRI vocabulary, which include the terms such as “metadata attributes”, “observation”, “dataset”.  Data retrieved from the different sources are firstly mapped to this uniform semantic model. Figure 3 gives two examples, and shows how datasets of ICOS and EuroArgo can be mapped to the ENVRI vocabulary, respectively.
 
 
{| class="wikitable" style="background-color:#ffffff; margin: auto;"
 
|-
 
| [[File:CO2.png|600px]]
 
|-
 
| [[File:Temp.png|600px]]
 
|}
 
<center>'''Figure 3''': Datasets as provided by ICOS (above) with CO2 concentrations and by EURO-Argo (below) with ocean temperature measurements</center>
 
 
 
Semantic mappings are based on observation statements. For example, the following observation statement declares the measurements about “'''air'''”:
 
 
<center>''“Observation of the CO2 concentration in samples of air at the Mace Head atmospheric station which is located at (53_20'N, 9_54'W): CO2 concentration of the air 25m above the sea level on Jan 1st, 2010 at 00:00 was 391.318 parts per million"''.</center>
 
 
“'''Air'''” is represented as the concept of air in GEneral Multi-lingual Environmental Thesaurus (GEMET) by assigning the URI to it (entity naming). The GEMET concept of air is then defined as an instance of envri:FeatureOfInterest (entity typing).
 
 
The mapping rules are specified by using the Data cube plug-in for Google Refine. The mappings are executed to obtain RDF representations of the source data files. As such they are uploaded to the [http://virtuoso.openlinksw.com/dataspace/doc/dav/wiki/Main/ Virtuoso OSE RDF store] and are ready to be queried at a SPARQL-endpoint.
 
 
The data harmonization process described above is captured by the Reference Model. As shown in Figure 4, the Information Viewpoint models the mapping of data according to [[File:lightbulb_on.png|16px]] [http://confluence.envri.eu:8090/display/ERM/IV+Information+Objects#IVInformationObjects-infobj_mappingrule '''mapping rules'''] which are defined by the use of [[File:lightbulb_on.png|16px]] [http://confluence.envri.eu:8090/display/ERM/IV+Information+Objects#IVInformationObjects-infobj_conceptualmodel '''local'''] and [[File:lightbulb_on.png|16px]] [http://confluence.envri.eu:8090/display/ERM/IV+Information+Objects#IVInformationObjects-infobj_conceptualmodel '''global conceptual model''']. Ontologies and thesauri are defined as '''conceptual models''', and those widely accepted models such as, GEMET, O&M, Data Cube, are declared [[File:lightbulb.png|16px]] [http://confluence.envri.eu:8090/display/ERM/IV+Information+Objects#IVInformationObjects-infobj_conceptualmodel global conceptual models] whereas the ENVRI vocabulary is specified as a [[File:lightbulb.png|16px]] [http://confluence.envri.eu:8090/display/ERM/IV+Information+Objects#IVInformationObjects-infobj_conceptualmodel local] one, because it has been developed within the current project without being yet accepted by a broad community.
 
 
[[File:MappingRM.png|1200px]]
 
<center>'''Figure 4''': The RM Information specification related to the semantic harmonisation</center>
 
 
Describing a process using the ENVRI Reference Model concepts is to instantiate the concepts that can be mapped to the process. Figure 5 illustrates the instantiation (all boxes with a dashed line) of the ENVRI Reference Model concepts focusing at the harmonization process described above. The same could be demonstrated for the EuroArgo dataset with the feature of interest being ocean. For each part of the observation mapping rules have to be defined to be able to query both datasets at a certain time period.
 
 
[[File:Dataharmonisationmapping.png|center]]
 
<center>'''Figure 5''': Mapping of the deployed information model with that of the the Reference Model</center>
 
 
The tables below show the mapping between the harmonisation process and the concepts in the ENVRI RM information viewpoint. The example shows that both bottom up (from the applied operation to the model description) and top down approaches (from the model definitions back to the applied solution) can lead to a better understanding of the Reference Model itself and of how components should work properly in a complex infrastructure.
 
 
<center>'''Table 2''': Mapping between the Reference Model [[File:lightbulb_on.png|16px]] [http://confluence.envri.eu:8090/display/ERM/IV+Information+Objects '''Information objects'''] and those in the deployed service</center>
 
{| class="wikitable" style="background-color:#ffffff; margin: auto;"
 
|-
 
| style="padding: 7px"| '''Information  Object in RM''' || '''Component/Object  in Task 4.2'''
 
|-
 
| style="padding: 7px"| [[File:lightbulb_on.png|16px]] [[IV_Information_Objects#specificationofmeasurementsorobservations|specification of measurements or observations]] || Observation  of the CO2 concentration in samples of '''air'''  at the Mace Head atmospheric station which is located at (53_20'N, 9_54'W): <br>
 
CO2 concentration of the air 25m above the sea level on Jan 1st, 2010 at  00:00 was 391.318 parts per million
 
|-
 
| style="padding: 7px"| [[File:lightbulb_on.png|16px]] [[IV States|mapped]] || GEMET:245 is instance of  FeatureOfInterest class
 
|-
 
| style="padding: 7px"| [[File:lightbulb_on.png|16px]] [[IV_Information_Objects#conceptualmodel|conceptual model]] || GEMET, O&M, DataCube
 
|-
 
| style="padding: 7px"| [[File:lightbulb_on.png|16px]] [[IV_Information_Objects#conceptualmodel|conceptual model]] || ENVRI vocabulary
 
|-
 
| style="padding: 7px"| [[File:lightbulb_on.png|16px]] [[IV_Information_Object_Instances#Local|local concept]] || FeatureOfInterest (ENVRI vocabulary)
 
|-
 
| style="padding: 7px"| [[File:lightbulb_on.png|16px]] [[IV_Information_Object_Instances#Global|global concept]] || Component Property, GEMET:245,  FeatureOfInterest (O&M)
 
|-
 
| style="padding: 7px"| [[File:lightbulb_on.png|16px]] [[IV_Information_Objects#mappingrule|mapping rule]] || GEMET:245 create as instance of  FeatureOfInterest class
 
|-
 
| style="padding: 7px"| [[File:lightbulb_on.png|16px]] [[IV States|published]] || ICOS data CO2 of air, EuroArgo data ocean  temperature
 
|}
 
 
 
<center>'''Table 3''': Mapping between the Reference Model [[File:lightbulb_on.png|16px]] [http://confluence.envri.eu:8090/display/ERM/IV+Information+Action+Types '''Action Types'''] and those in the deployed service</center>
 
{| class="wikitable" style="background-color:#ffffff; margin: auto;"
 
|-
 
|  style="padding: 7px"| '''Information Action Tyoes in RM''' || '''Operation  in Task 4.2'''
 
|-
 
|  style="padding: 7px"| [[File:lightbulb_on.png|16px]] [[IV_Information_Action_Types#buildconceptualmodels|build conceptual models]] || Build  ENVRI vocabulary as extension of DataCube and on basis of O&M concepts
 
|-
 
|  style="padding: 7px"| [[File:lightbulb_on.png|16px]] [[IV_Information_Action_Types#setupmappingrules|setup mapping rules]] || Define rule: GEMET:245 create as instance  of FeatureOfInterest class
 
|-
 
|  style="padding: 7px"| [[File:lightbulb_on.png|16px]] [[IV_Information_Action_Types#performmapping|perform mapping]] || Perform Mapping using Google Refine
 
|-
 
|  style="padding: 7px"| [[File:lightbulb_on.png|16px]] [[IV_Information_Action_Types#querydata|query data]] || SPARQL query: http://staff.science.uva.nl/~ttaraso1/html/queries/Q1.rq
 
|}
 
 
== <span style="color: #BBCE00">Summary</span> ==
 
 
This example demonstrate the feasibility of the design specifications of the reference model.  Instances of selected model components can be developed into common services, in this case, a [[File:lightbulb.png|16px]] '''subsystem''' that supports integrated data discovery and access. Data products from different environmental research infrastructures including, measurements of deep sea, upper space, volcano and seismology, open sea, atmosphere, and biodiversity, can now be pulled out through a [http://89.202.228.220/ single data access interface]. Scientists are using this newly-available data resource to study environmental problems previously unachievable including, the study of the climate impact caused by the eruptions of the Eyjafjallajökull volcano in 2010.
 
 
[[Category:Appendix D Guidlines for using the Reference Model]]
 
[[Category:Appendix D Guidlines for using the Reference Model]]

Please note that all contributions to may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see Copyrights for details). Do not submit copyrighted work without permission!

Cancel Editing help (opens in new window)