Latest revision |
Your text |
Line 69: |
Line 69: |
| | | |
| <p style="background-color: #fcfcfc; border-radius: 5px; border: 1px solid #ccc; padding: 10px 20px 10px 20px;"> | | <p style="background-color: #fcfcfc; border-radius: 5px; border: 1px solid #ccc; padding: 10px 20px 10px 20px;"> |
| + | '''Note'''<br> |
| A field laboratory is created by a science gateway in order to allow researchers in the field to interact with the data acquisition objects. | | A field laboratory is created by a science gateway in order to allow researchers in the field to interact with the data acquisition objects. |
| | | |
| The degree of freedom with which a field laboratory interacts with other data acquisition objects is contingent on the nature of the research infrastructure and policed by a [[CV_Service_Objects#AAAI_service|'''AAAI service''']] object (as defined for all user laboratories). | | The degree of freedom with which a field laboratory interacts with other data acquisition objects is contingent on the nature of the research infrastructure and policed by a [[CV_Service_Objects#AAAI_service|'''AAAI service''']] object (as defined for all user laboratories). |
− | </p>
| |
− |
| |
− | == <span style="color: #BBCE00">Experiment laboratory</span> ==
| |
− | {| class="wikitable" style="background-color:#ffffff; float:right; margin-left: 10px;"
| |
− | |-
| |
− | |style="padding: 0px"| [[File:CVOExperimentLaboratory.png]]
| |
− | |}
| |
− | ''Community proxy for conducting experiments within a research infrastructure.''
| |
− |
| |
− | A sub-class of [[CV_Presentation_Objects#Virtual_laboratory|'''virtual laboratory''']] object encapsulating the functions required to schedule the processing of curated and user-provided data in order to perform some task (analysis, data mining, modelling, simulation, etc.).
| |
− |
| |
− | An experiment laboratory should provide at least three operational interfaces:
| |
− |
| |
− | * '''data request (client)''' is used to make requests of the research infrastructure pertaining to curated datasets.
| |
− | * '''process request (client)''' is used to make requests of the research infrastructure pertaining to data processing.
| |
− | * '''translate request (client)''' is used to invoke a semantic broker where some mapping between different semantic domains is deemed necessary.
| |
− |
| |
− | <p style="background-color: #fcfcfc; border-radius: 5px; border: 1px solid #ccc; padding: 10px 20px 10px 20px;">
| |
− | An experiment laboratory is created by a science gateway to allow researchers interaction with data held by a research infrastructure in order to achieve some scientific output.
| |
− | </p>
| |
− |
| |
− | == <span style="color: #BBCE00">Semantic laboratory</span> ==
| |
− | {| class="wikitable" style="background-color:#ffffff; float:right; margin-left: 10px;"
| |
− | |-
| |
− | |style="padding: 0px"| [[File:CVOSemanticLaboratory.png]]
| |
− | |}
| |
− | ''Community proxy for interacting with semantic models.''
| |
− |
| |
− | A sub-class of [[CV_Presentation_Objects#Virtual_laboratory|'''virtual laboratory''']] object encapsulating the functions required to update semantic models (such as ontologies) used in the interpretation of curated data (and infrastructure metadata).
| |
− |
| |
− | A semantic laboratory should provide at least one operational interface in addition to those provided by any virtual laboratory:
| |
− |
| |
− | * '''update model (client)''' is used to update semantic models associated with a research infrastructure.
| |
− | * '''semantic data request (client)''' is used to make requests of the research infrastructure about metadata and annotations referring to data stored by the data set.
| |
− | <p style="background-color: #fcfcfc; border-radius: 5px; border: 1px solid #ccc; padding: 10px 20px 10px 20px;">
| |
− | A semantic laboratory is created by a science gateway in order to allow researchers to provide input on the interpretation of data gathered by a research infrastructure.
| |
| </p> | | </p> |
| [[Category:CV Objects]] | | [[Category:CV Objects]] |