CRMsci: An Extension of CIDOC CRM to support scientific observation Root
CRMsci: An Extension of CIDOC CRM to support scientific observation
Description:
What is the CRMsci?
The Scientific Observation Model (CRMsci) is a formal ontology intended to be used as a global schema for integrating metadata about scientific observation, measurements and processed data in descriptive and empirical sciences such as biodiversity, geology, geography, archaeology, cultural heritage conservation and others in research IT environments and research data libraries. Its primary purpose is facilitating the management, integration, mediation, interchange and access to research data by description of semantic relationships, in particular causal ones. It is not primarily a model to process the data themselves in order to produce new research results, even though its representations offer themselves to be used for some kind of processing.
CRMsci uses and extends the CIDOC CRM (ISO21127) as a general ontology of human activity, things and events happening in spacetime. It uses the same encoding-neutral formalism of knowledge representation (“data model” in the sense of computer science) as the CIDOC CRM, which can be implemented in RDFS, OWL, on RDBMS and in other forms of encoding. Since the model reuses, wherever appropriate, parts of CIDOC Conceptual Reference Model, we provide in this document also a comprehensive list of all constructs used from ISO21127, together with their definitions following the version 6.2 maintained by CIDOC.
What is the idea?
The CRMsci has been developed bottom up from specific metadata examples from biodiversity, geology, archeology, cultural heritage conservation and clinical studies, such as water sampling in aquifer systems, earthquake shock recordings, landslides, excavation processes, species occurrence and detection of new species, tissue sampling in cancer research, 3D digitization, based on communication with the domain experts and the implementation and validation in concrete applications. It takes into account relevant standards, such as INSPIRE, OBOE, national archeological standards for excavation, Digital Provenance models and others. For each application, another set of extensions is needed in order to describe those data at an adequate level of specificity, such as semantics of excavation layers or specimen capture in biology. However, the model presented here describes, together with the CIDOC CRM, a discipline neutral level of genericity, which can be used to implement effective management functions and powerful queries for related data. It aims at providing superclasses and superproperties for any application-specific extension, such that any entity referred to by a compatible extension can be reached with a more general query based on this model.
CRMsci is a proposal for approval by CIDOC CRM SIG
Description
Identification
Start date: 2017-10-07
Base URI: http://www.cidoc-crm.org/cidoc-crm/CRMsci/
Project of belonging: CRMsci
Root namespace prefix: crmsci
This namespace is a root namespace. Find all its versions in the Versions tab.
Labels
Label | Language | Last updated |
---|---|---|
CRMsci: An Extension of CIDOC CRM to support scientific observation * | en | 2019-03-28 |
* : Standard label for this language
Versions
CRMsci: An Extension of CIDOC CRM to support scientific observation is a root namespace.
Published versions
Namespace | Publication date |
---|---|
CRMsci version 1.2.3 | 2017-03-31 |
CRMsci version 2.0 | 2023-03-31 |
Classes
Identifier | Class | Last updated |
---|
Properties
Domain | Domain namespace | Identifier | Property | Range | Range namespace | Last updated |
---|
Relations
Filter by
Source | Source namespace | Relation | Target | Target namespace | Last updated | Type |
---|
Notes
Show | Note | Type | Language | Entity |
---|
Graph
The webvowl graph cannot be displayed because there is no class or property in this namespace.
List of mismatches with reference namespaces
Entities listed here are not correctly associated with your reference namespaces.
They are displayed in red in your ongoing namespace. They may not be available in the version of the selected space.
Or you may not have selected any version of a reference namespace.
Please make the necessary corrections before proceeding.
Type of relation | Entity | Namespace | Error type |
---|
Comments
No comment found.