Editing IV Information Objects
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 45: | Line 45: | ||
|- | |- | ||
| style="background-color:#ffffff;"| [[File:IVObjectTypes.png]] | | style="background-color:#ffffff;"| [[File:IVObjectTypes.png]] | ||
− | <div style='text-align: right;'>''' | + | <div style='text-align: right;'>'''Notation'''</div> |
|} | |} | ||
− | == <span style="color: #BBCE00 | + | == <span style="color: #BBCE00">Information Object Definitions</span> == |
− | <span style="color: #5E6C84 | + | <span style="color: #5E6C84">'''backup'''</span> |
A copy of (persistent) data so it may be used to restore the original after a data loss event. | A copy of (persistent) data so it may be used to restore the original after a data loss event. | ||
− | <span style="color: #5E6C84 | + | <span style="color: #5E6C84">'''mapping rule'''</span> |
Configuration directives used for model-to-model transformation. | Configuration directives used for model-to-model transformation. | ||
Line 81: | Line 81: | ||
It is important that the citation is resolvable, which means that the identifiers point to live data sets and that the meaning of the items above are made clear. | It is important that the citation is resolvable, which means that the identifiers point to live data sets and that the meaning of the items above are made clear. | ||
− | <span style="color: #5E6C84 | + | <span style="color: #5E6C84">'''concept'''</span> |
Identifier, name and definition of the meaning of a thing (abstract or real thing). Human readable definition by sentences, machine readable definition by relations to other concepts (machine readable sentences). It can also be meant for the smallest entity of a conceptual model. It can be part of a flat list of concepts, a hierarchical list of concepts, a hierarchical thesaurus or an ontology. | Identifier, name and definition of the meaning of a thing (abstract or real thing). Human readable definition by sentences, machine readable definition by relations to other concepts (machine readable sentences). It can also be meant for the smallest entity of a conceptual model. It can be part of a flat list of concepts, a hierarchical list of concepts, a hierarchical thesaurus or an ontology. | ||
− | <span style="color: #5E6C84 | + | <span style="color: #5E6C84">'''conceptual model'''</span> |
A collection of concepts, their attributes and their relations. It can be unstructured or structured (e.g. glossary, thesaurus, ontology). Usually the description of a concept and/or a relation defines the concept in a human readable form. Conceptual models can also be represented in machine readable formats, for instance RDFS or OWL. Those sentences can be used to construct a self description. It is common practice to provide both the human readable description and the machine readable description within the same system. In this sense, a conceptual model can also be seen as a collection of human and machine readable sentences. They can be local, developed within a project, or global, accepted and used by a wider community (such as GEMET or OBOE). Conceptual models can be used to annotate data (e.g. within a network of triple stores). | A collection of concepts, their attributes and their relations. It can be unstructured or structured (e.g. glossary, thesaurus, ontology). Usually the description of a concept and/or a relation defines the concept in a human readable form. Conceptual models can also be represented in machine readable formats, for instance RDFS or OWL. Those sentences can be used to construct a self description. It is common practice to provide both the human readable description and the machine readable description within the same system. In this sense, a conceptual model can also be seen as a collection of human and machine readable sentences. They can be local, developed within a project, or global, accepted and used by a wider community (such as GEMET or OBOE). Conceptual models can be used to annotate data (e.g. within a network of triple stores). | ||
− | <span style="color: #5E6C84 | + | <span style="color: #5E6C84">'''data'''</span> |
Research data processed by the RI. This is the base information object class from which all other information objects are derived | Research data processed by the RI. This is the base information object class from which all other information objects are derived | ||
− | <span style="color: #5E6C84 | + | <span style="color: #5E6C84">'''data provenance'''</span> |
Metadata that traces the origins of data and records all state changes of data during their lifecycle and their movements between storages. | Metadata that traces the origins of data and records all state changes of data during their lifecycle and their movements between storages. | ||
Line 106: | Line 106: | ||
Data provenance system is an annotation system for managing data provenances. Usually unique identifiers are used to refer the data in their different states and for the description of the different states. | Data provenance system is an annotation system for managing data provenances. Usually unique identifiers are used to refer the data in their different states and for the description of the different states. | ||
− | <span style="color: #5E6C84 | + | <span style="color: #5E6C84">'''measurement result'''</span> |
Quantitative, qualitative, or cataloguing determinations of magnitude, dimension, and uncertainty to the outputs of observation instruments, sensors, sensor networks, human observers and observer networks. | Quantitative, qualitative, or cataloguing determinations of magnitude, dimension, and uncertainty to the outputs of observation instruments, sensors, sensor networks, human observers and observer networks. | ||
− | <span style="color: #5E6C84 | + | <span style="color: #5E6C84">'''metadata'''</span> |
Data about data, in scientific applications is used to describe, explain, locate, or make it easier to retrieve, use, or manage a data resource. | Data about data, in scientific applications is used to describe, explain, locate, or make it easier to retrieve, use, or manage a data resource. | ||
Line 151: | Line 151: | ||
Metadata can be fused with the data. However, in many applications, such as a provenance system or a distributed satellite image annotation system, the metadata and data are often created and stored separately, as they may be generated by different users, in different computing processes, stored at different locations and in different types of storage. Often, there is more than one set of metadata related to a single data resource, e.g. when the existing metadata becomes insufficient, users may design new templates to make another metadata collection. Efficient software and tools are required to facilitate the management of the linkage between metadata and data. Such linkage relationship between metadata and data are vulnerable to failures in the processes that create and maintain them, and to failures in the systems that store their representations. It is important to devise methods that reduce these failures. | Metadata can be fused with the data. However, in many applications, such as a provenance system or a distributed satellite image annotation system, the metadata and data are often created and stored separately, as they may be generated by different users, in different computing processes, stored at different locations and in different types of storage. Often, there is more than one set of metadata related to a single data resource, e.g. when the existing metadata becomes insufficient, users may design new templates to make another metadata collection. Efficient software and tools are required to facilitate the management of the linkage between metadata and data. Such linkage relationship between metadata and data are vulnerable to failures in the processes that create and maintain them, and to failures in the systems that store their representations. It is important to devise methods that reduce these failures. | ||
− | <span style="color: #5E6C84 | + | <span style="color: #5E6C84">'''metadata catalogue'''</span> |
A collection of metadata, usually established to make the metadata available to a community. A metadata catalogue can be exposed through an access service. | A collection of metadata, usually established to make the metadata available to a community. A metadata catalogue can be exposed through an access service. | ||
− | <span style="color: #5E6C84 | + | <span style="color: #5E6C84">'''metadata state'''</span> |
metadata state is an object property that determines the set of all sequences of actions (or traces) in which the metadata object can participate, at a given instant in time (as defined in ODP, ISO/IEC 10746-2). | metadata state is an object property that determines the set of all sequences of actions (or traces) in which the metadata object can participate, at a given instant in time (as defined in ODP, ISO/IEC 10746-2). | ||
Line 174: | Line 174: | ||
|} | |} | ||
− | <span style="color: #5E6C84" | + | <span style="color: #5E6C84">'''<span style="color: #5E6C84">persistent data'''</span> |
Data is the representations of information dealt with by information systems and users thereof (as defined in ODP, ISO/IEC 10746-2). Persistent Data denotes data that are persisted (stored for the long-term). | Data is the representations of information dealt with by information systems and users thereof (as defined in ODP, ISO/IEC 10746-2). Persistent Data denotes data that are persisted (stored for the long-term). | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
[[Category:IV Components]] | [[Category:IV Components]] |