sysadmin/paquetes-sprpcb
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

ontologia cargada

Browse Source
This commit is contained in:
root
2026-05-12 04:31:58 +00:00
parent ee78c58cd1
commit b68e4e5dbb
8 changed files with 7493 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

248
ontologies/cidoc-crm-ontology-master/CRMarchaeo_v1.4.rdfs.xml Normal file
View File

@@ -0,0 +1,248 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!--
CRMarchaeo 1.4 Encoded in RDFS
RDFS updated by FORTH-ICS April 14, 2016
Encoding Rules:
1. The RDF spelling rules do not allow blanks. Hence we have replaced them by underscores.
The blank between the concept identifier and concept name is replaced by underscore too.
For instance "A1_Excavation_Process_Unit" or "AP1_produced".
2. RDF does not allow to instantiate properties beginning from a range value.
Therefore, each CRMarchaeo property is represented as two RDFS properties.
For instance "AP1_produced (was_produced_by)" is represented as:
"AP1_produced" for the domain to range direction and "AP1i_was_produced_by" for the range to domain direction.
-->
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#"
xml:base="http://www.ics.forth.gr/isl/CRMarchaeo/" xml:lang="en">
<rdfs:Class rdf:about="A1_Excavation_Process_Unit">
<rdfs:subClassOf rdf:resource="http://www.ics.forth.gr/isl/CRMsci/S1_Matter_Removal"/>
</rdfs:Class>
<rdfs:Class rdf:about="A2_Stratigraphic_Volume_Unit">
<rdfs:subClassOf rdf:resource="A8_Stratigraphic_Unit"/>
</rdfs:Class>
<rdfs:Class rdf:about="A3_Stratigraphic_Interface">
<rdfs:subClassOf rdf:resource="A8_Stratigraphic_Unit"/>
</rdfs:Class>
<rdfs:Class rdf:about="A4_Stratigraphic_Genesis">
<rdfs:subClassOf rdf:resource="http://www.ics.forth.gr/isl/CRMsci/S17_Physical_Genesis"/>
<rdfs:subClassOf rdf:resource="A5_Stratigraphic_Modification"/>
</rdfs:Class>
<rdfs:Class rdf:about="A5_Stratigraphic_Modification">
<rdfs:subClassOf rdf:resource="http://www.ics.forth.gr/isl/CRMsci/S18_Alteration"/>
</rdfs:Class>
<rdfs:Class rdf:about="A6_Group_Declaration_Event">
<rdfs:subClassOf rdf:resource="http://www.ics.forth.gr/isl/CRMsci/S5_Inference_Making"/>
<rdfs:subClassOf rdf:resource="http://www.ics.forth.gr/isl/CRMinf/I5_Inference_Making"/>
</rdfs:Class>
<rdfs:Class rdf:about="A7_Embedding">
<rdfs:subClassOf rdf:resource="http://www.ics.forth.gr/isl/CRMsci/S16_State"/>
</rdfs:Class>
<rdfs:Class rdf:about="A8_Stratigraphic_Unit">
<rdfs:subClassOf rdf:resource="http://www.ics.forth.gr/isl/CRMsci/S20_Physical_Feature"/>
</rdfs:Class>
<rdfs:Class rdf:about="A9_Archaeological_Excavation">
<rdfs:subClassOf rdf:resource="http://www.ics.forth.gr/isl/CRMsci/S1_Matter_Removal"/>
<rdfs:subClassOf rdf:resource="http://www.ics.forth.gr/isl/CRMsci/S4_Observasion"/>
</rdfs:Class>
<rdf:Property rdf:about="AP1_produced">
<rdfs:domain rdf:resource="A1_Excavation_Process_Unit"/>
<rdfs:range rdf:resource="http://www.ics.forth.gr/isl/CRMsci/S11_Amount_of_Matter"/>
</rdf:Property>
<rdf:Property rdf:about="AP1i_was_produced_by">
<rdfs:domain rdf:resource="http://www.ics.forth.gr/isl/CRMsci/S11_Amount_of_Matter"/>
<rdfs:range rdf:resource="A1_Excavation_Process_Unit"/>
</rdf:Property>
<rdf:Property rdf:about="AP2_discarded_into">
<rdfs:domain rdf:resource="A1_Excavation_Process_Unit"/>
<rdfs:range rdf:resource="http://www.ics.forth.gr/isl/CRMsci/S11_Amount_of_Matter"/>
</rdf:Property>
<rdf:Property rdf:about="AP2i_was_discarded_by">
<rdfs:domain rdf:resource="http://www.ics.forth.gr/isl/CRMsci/S11_Amount_of_Matter"/>
<rdfs:range rdf:resource="A1_Excavation_Process_Unit"/>
</rdf:Property>
<rdf:Property rdf:about="AP3_excavated">
<rdfs:domain rdf:resource="A1_Excavation_Process_Unit"/>
<rdfs:range rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E53_Place"/>
</rdf:Property>
<rdf:Property rdf:about="AP3i_was_excavated_by">
<rdfs:domain rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E53_Place"/>
<rdfs:range rdf:resource="A1_Excavation_Process_Unit"/>
</rdf:Property>
<rdf:Property rdf:about="AP4_produced_surface">
<rdfs:domain rdf:resource="A1_Excavation_Process_Unit"/>
<rdfs:range rdf:resource="http://www.ics.forth.gr/isl/CRMsci/S20_Physical_Feature"/>
</rdf:Property>
<rdf:Property rdf:about="AP4i_was_surface_produced_by">
<rdfs:domain rdf:resource="http://www.ics.forth.gr/isl/CRMsci/S20_Physical_Feature"/>
<rdfs:range rdf:resource="A1_Excavation_Process_Unit"/>
</rdf:Property>
<rdf:Property rdf:about="AP5_removed_part_or_all_of">
<rdfs:domain rdf:resource="A1_Excavation_Process_Unit"/>
<rdfs:range rdf:resource="A8_Stratigraphic_Unit"/>
</rdf:Property>
<rdf:Property rdf:about="AP5i_was_partially_or_totally_removed_by">
<rdfs:domain rdf:resource="A8_Stratigraphic_Unit"/>
<rdfs:range rdf:resource="A1_Excavation_Process_Unit"/>
</rdf:Property>
<rdf:Property rdf:about="AP6_intended_to_approximate">
<rdfs:domain rdf:resource="A1_Excavation_Process_Unit"/>
<rdfs:range rdf:resource="A3_Stratigraphic_Interface"/>
<rdfs:subPropertyOf rdf:resource="http://www.ics.forth.gr/isl/CRMsci/O8_observed"/>
</rdf:Property>
<rdf:Property rdf:about="AP6i_was_approximated_by">
<rdfs:domain rdf:resource="A3_Stratigraphic_Interface"/>
<rdfs:range rdf:resource="A1_Excavation_Process_Unit"/>
<rdfs:subPropertyOf rdf:resource="http://www.ics.forth.gr/isl/CRMsci/O8i_was_observed_by"/>
</rdf:Property>
<rdf:Property rdf:about="AP7_produced">
<rdfs:domain rdf:resource="A4_Stratigraphic_Genesis"/>
<rdfs:range rdf:resource="A3_Stratigraphic_Interface"/>
<rdfs:subPropertyOf rdf:resource="http://www.ics.forth.gr/isl/CRMsci/O17_generated"/>
</rdf:Property>
<rdf:Property rdf:about="AP7i_was_produced_by">
<rdfs:domain rdf:resource="A3_Stratigraphic_Interface"/>
<rdfs:range rdf:resource="A4_Stratigraphic_Genesis"/>
<rdfs:subPropertyOf rdf:resource="http://www.ics.forth.gr/isl/CRMsci/O17i_was_generated_by"/>
</rdf:Property>
<rdf:Property rdf:about="AP8_disturbed">
<rdfs:domain rdf:resource="A4_Stratigraphic_Genesis"/>
<rdfs:range rdf:resource="A3_Stratigraphic_Interface"/>
</rdf:Property>
<rdf:Property rdf:about="AP8i_was_disturbed_by">
<rdfs:domain rdf:resource="A3_Stratigraphic_Interface"/>
<rdfs:range rdf:resource="A4_Stratigraphic_Genesis"/>
</rdf:Property>
<rdf:Property rdf:about="AP9_took_matter_from">
<rdfs:domain rdf:resource="A4_Stratigraphic_Genesis"/>
<rdfs:range rdf:resource="http://www.ics.forth.gr/isl/CRMsci/S10_Material_Substantial"/>
</rdf:Property>
<rdf:Property rdf:about="AP9i_provided_matter_to">
<rdfs:domain rdf:resource="http://www.ics.forth.gr/isl/CRMsci/S10_Material_Substantial"/>
<rdfs:range rdf:resource="A4_Stratigraphic_Genesis"/>
</rdf:Property>
<rdf:Property rdf:about="AP10_destroyed">
<rdfs:domain rdf:resource="A1_Excavation_Process_Unit"/>
<rdfs:range rdf:resource="http://www.ics.forth.gr/isl/CRMsci/S22_Segment_of_Matter"/>
<rdfs:subPropertyOf rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P13_destroyed"/>
</rdf:Property>
<rdf:Property rdf:about="AP10i_was_destroyed_by">
<rdfs:domain rdf:resource="http://www.ics.forth.gr/isl/CRMsci/S22_Segment_of_Matter"/>
<rdfs:range rdf:resource="A1_Excavation_Process_Unit"/>
<rdfs:subPropertyOf rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P13i_was_destroyed_by"/>
</rdf:Property>
<rdf:Property rdf:about="AP11_has_physioical_relation">
<rdfs:domain rdf:resource="A8_Stratigraphic_Unit"/>
<rdfs:range rdf:resource="A8_Stratigraphic_Unit"/>
</rdf:Property>
<rdf:Property rdf:about="AP11i_is_physical_relation_of">
<rdfs:domain rdf:resource="A8_Stratigraphic_Unit"/>
<rdfs:range rdf:resource="A8_Stratigraphic_Unit"/>
</rdf:Property>
<rdf:Property rdf:about="AP13_has_stratigraphic_relation">
<rdfs:domain rdf:resource="A8_Stratigraphic_Unit"/>
<rdfs:range rdf:resource="A8_Stratigraphic_Unit"/>
</rdf:Property>
<rdf:Property rdf:about="AP13i_is_stratigraphic_relation_of">
<rdfs:domain rdf:resource="A8_Stratigraphic_Unit"/>
<rdfs:range rdf:resource="A8_Stratigraphic_Unit"/>
</rdf:Property>
<rdf:Property rdf:about="AP15_is_or_contains_remains_of">
<rdfs:domain rdf:resource="A8_Stratigraphic_Unit"/>
<rdfs:range rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E18_Physical_Thing"/>
</rdf:Property>
<rdf:Property rdf:about="AP15i_is_or_has_remains_contained_in">
<rdfs:domain rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E18_Physical_Thing"/>
<rdfs:range rdf:resource="A8_Stratigraphic_Unit"/>
</rdf:Property>
<rdf:Property rdf:about="AP16_assigned_attribute_to">
<rdfs:domain rdf:resource="A6_Group_Declaration_Event"/>
<rdfs:range rdf:resource="A8_Stratigraphic_Unit"/>
<rdfs:subPropertyOf rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P140_assigned_attribute_to"/>
</rdf:Property>
<rdf:Property rdf:about="AP16i_was_attributed_by">
<rdfs:domain rdf:resource="A8_Stratigraphic_Unit"/>
<rdfs:range rdf:resource="A6_Group_Declaration_Event"/>
<rdfs:subPropertyOf rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P140i_was_attributed_by"/>
</rdf:Property>
<rdf:Property rdf:about="AP17_is_found_by">
<rdfs:domain rdf:resource="A7_Embedding"/>
<rdfs:range rdf:resource="http://www.ics.forth.gr/isl/CRMsci/S19_Encounter_Event"/>
</rdf:Property>
<rdf:Property rdf:about="AP17i_found">
<rdfs:domain rdf:resource="http://www.ics.forth.gr/isl/CRMsci/S19_Encounter_Event"/>
<rdfs:range rdf:resource="A7_Embedding"/>
</rdf:Property>
<rdf:Property rdf:about="AP18_is_embedding_of">
<rdfs:domain rdf:resource="A7_Embedding"/>
<rdfs:range rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E18_Physical_Thing"/>
</rdf:Property>
<rdf:Property rdf:about="AP18i_is_embedded">
<rdfs:domain rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E18_Physical_Thing"/>
<rdfs:range rdf:resource="A7_Embedding"/>
</rdf:Property>
<rdf:Property rdf:about="AP19_is_embedding_in">
<rdfs:domain rdf:resource="A7_Embedding"/>
<rdfs:range rdf:resource="A2_Stratigraphic_Volume_Unit"/>
</rdf:Property>
<rdf:Property rdf:about="AP19i_contains_embedding">
<rdfs:domain rdf:resource="A2_Stratigraphic_Volume_Unit"/>
<rdfs:range rdf:resource="A7_Embedding"/>
</rdf:Property>
<rdf:Property rdf:about="AP20_is_embedding_at">
<rdfs:domain rdf:resource="A7_Embedding"/>
<rdfs:range rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E53_Place"/>
</rdf:Property>
<rdf:Property rdf:about="AP20i_contains">
<rdfs:domain rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E53_Place"/>
<rdfs:range rdf:resource="A7_Embedding"/>
</rdf:Property>
</rdf:RDF>

636
ontologies/cidoc-crm-ontology-master/CRMdig_v3.2.1.rdfs.xml Normal file
View File

@@ -0,0 +1,636 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!--
CRMdig 3.2.1 Encoded in RDFS
RDFS updated by FORTH-ICS April 2016
Encoding Rules:
1. The RDF spelling rules do not allow blanks. Hence we have replaced them by underscores.
The blank between the concept identifier and concept name is replaced by underscore too.
For instance "D7_Digital_Machine_Event" or "P2i_is_type_of".
2. RDF does not allow to instantiate properties beginning from a range value.
Therefore, each CRMdig property is represented as two RDFS properties.
For instance "L2 used as source (was source for)" is represented as:
"L2_used_as_source" for the domain to range direction and "L2i_was_source_for" for the range to domain direction.
-->
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#"
xml:base="http://www.ics.forth.gr/isl/CRMdig/" xml:lang="en">
<rdfs:Class rdf:about="D1_Digital_Object">
<rdfs:comment>This class comprises identifiable immaterial items that can be represented as sets of bit sequences,
such as data sets, e-texts, images, audio or video items, software, etc., and are documented as single units.
Any aggregation of instances of D1 Digital Object into a whole treated as single unit is also regarded as an instance of D1 Digital Object.
This means that for instance, the content of a DVD, an XML file on it, and an element of this file, are regarded as distinct instances of
D1 Digital Object, mutually related by the P106 is composed of (forms part of) property.
A D1 Digital Object does not depend on a specific physical carrier, and it can exist on one or more carriers simultaneously.
</rdfs:comment>
<rdfs:subClassOf rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E73_Information_Object"/>
</rdfs:Class>
<rdfs:Class rdf:about="D2_Digitization_Process">
<rdfs:comment>This class comprises events that result in the creation of instances of D9 Data Object that
represent the appearance and/or form of an instance of E18 Physical Thing such as paper documents, statues, buildings, paintings, etc.
A particular case is the analogue-to-digital conversion of audiovisual material.
This class represents the transition from a material thing to an immaterial representation of it.
The characteristic subsequent processing steps on digital objects are regarded as instances of D3 Formal Derivation.
</rdfs:comment>
<rdfs:subClassOf rdf:resource="D11_Digital_Measurement_Event"/>
</rdfs:Class>
<rdfs:Class rdf:about="D3_Formal_Derivation">
<rdfs:comment>This class comprises events that result in the creation of a D1 Digital Object from another one following a deterministic algorithm,
such that the resulting instance of digital object shares representative properties with the original object.
In other words, this class describes the transition from an immaterial object referred to by property L21 used as derivation source (was derivation source for)
to another immaterial object referred to by property L22 created derivative (was derivative created by) preserving the
representation of some things but in a different form. Characteristic examples are colour corrections, contrast changes and resizing of images.
</rdfs:comment>
<rdfs:subClassOf rdf:resource="D10_Software_Execution"/>
</rdfs:Class>
<rdfs:Class rdf:about="D7_Digital_Machine_Event">
<rdfs:comment>This class comprises events that happen on physical digital devices following a human activity that intentionally caused its
immediate or delayed initiation and results in the creation of a new instance of D1 Digital Object on behalf of the human actor.
The input of a D7 Digital Machine Event may be parameter settings and/or data to be processed.
Some D7 Digital Machine Events may form part of a wider E65 Creation event.
In this case, all machine output of the partial events is regarded as creation of the overall activity.
</rdfs:comment>
<rdfs:subClassOf rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E11_Modification"/>
<rdfs:subClassOf rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E65_Creation"/>
</rdfs:Class>
<rdfs:Class rdf:about="D8_Digital_Device">
<rdfs:comment>This class comprises identifiable material items such as computers, scanners, cameras, etc. that
have the capability to process or produce instances of D1 Digital Object.
</rdfs:comment>
<rdfs:subClassOf rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E22_Man-Made_Object"/>
</rdfs:Class>
<rdfs:Class rdf:about="D9_Data_Object">
<rdfs:comment>This class comprises instances of D1 Digital Object that are the direct result of a digital
measurement or a formal derivative of it, containing quantitative properties of some physical things or other constellations of matter.
</rdfs:comment>
<rdfs:subClassOf rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E54_Dimension"/>
<rdfs:subClassOf rdf:resource="D1_Digital_Object"/>
</rdfs:Class>
<rdfs:Class rdf:about="D10_Software_Execution">
<rdfs:comment>This class comprises events by which a digital device runs a software program or a series of computing
operations on a digital object as a single task, which is completely determined by its digital input,
the software and the generic properties of the device.
</rdfs:comment>
<rdfs:subClassOf rdf:resource="D7_Digital_Machine_Event"/>
</rdfs:Class>
<rdfs:Class rdf:about="D11_Digital_Measurement_Event">
<rdfs:comment>This class comprises actions measuring physical properties using a digital device,
that are determined by a systematic procedure and creates an instance of D9 Data Object,
which is stored on an instance of D13 Digital Information Carrier.
In contrast to instances of D10 Software Execution, environmental factors have an intended influence on the outcome of an instance of D11 Digital Measurement Event.
Measurement devices may include running distinct software, such as the RAW to JPEG conversion in digital cameras.
In this case, the event is regarded as instance of both classes, D10 Software Execution and D11 Digital Measurement Event.
</rdfs:comment>
<rdfs:subClassOf rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E16_Measurement"/>
<rdfs:subClassOf rdf:resource="D7_Digital_Machine_Event"/>
</rdfs:Class>
<rdfs:Class rdf:about="D12_Data_Transfer_Event">
<rdfs:comment>This class comprises events that transfer a digital object from one digital carrier to another.
Normally, the digital object remains the same. If in general or by observation the transfer implies or has
implied some data corruption, the change of the digital objects may be documented distinguishing input and output
rather than instantiating the property L14 transferred (was transferred by).
</rdfs:comment>
<rdfs:subClassOf rdf:resource="D7_Digital_Machine_Event"/>
</rdfs:Class>
<rdfs:Class rdf:about="D13_Digital_Information_Carrier">
<rdfs:comment>This class comprises all instances of E84 Information Carrier that are explicitly designed to be
used as persistent digital physical carriers of instances of D1 Digital Object.
A D13 Digital Information Carrier may or may not contain information, e.g., an empty diskette.
</rdfs:comment>
<rdfs:subClassOf rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E84_Information_Carrier"/>
</rdfs:Class>
<rdfs:Class rdf:about="D14_Software">
<rdfs:comment>This class comprises software codes,computer programs,procedures, and functions that are
used to operate a system of digital objects. </rdfs:comment>
<rdfs:subClassOf rdf:resource="D1_Digital_Object"/>
</rdfs:Class>
<rdfs:Class rdf:about="D21_Person_Name">
<rdfs:comment>This class comprises the proper noun name that identifies a person that acts
as an entity.</rdfs:comment>
<rdfs:subClassOf rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E82_Actor_Appellation"/>
</rdfs:Class>
<rdfs:Class rdf:about="D23_Room">
<rdfs:comment/>
<rdfs:subClassOf rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E53_Place"/>
</rdfs:Class>
<rdfs:Class rdf:about="D29_Annotation_Object">
<rdfs:comment>This class comprises objects that make propositions about other artefacts.
Instances of this class are not the attributes themselves, by which things are annotated,
but represent the connection between the concepts related in a proposition, and the activities of creation, modification and deletion.
</rdfs:comment>
<rdfs:subClassOf rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E89_Propositional_Object"/>
</rdfs:Class>
<rdfs:Class rdf:about="D30_Annotation_Event">
<rdfs:comment>This class comprises events that describe the creation of associations (Annotation Objects) between objects
or areas of objects of the Repository, with other objects or regions or persons, places, events. It is the event that creates the Annotation Object.</rdfs:comment>
<rdfs:subClassOf rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E65_Creation"/>
</rdfs:Class>
<rdfs:Class rdf:about="D35_Area">
<rdfs:comment>This class describes a part (of any shape or size) of interest in basically any media object stored in the Object Repository,
i.e., a text, an image, a video or a 3D model. It points to content consisting of just a portion or area of a file.
In some contexts, however, the area can also point to content represented by an integral (i.e., proper) file. It is equal to the METS AREA element </rdfs:comment>
<rdfs:subClassOf rdf:resource="D1_Digital_Object"/>
<rdfs:subClassOf rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E26_Physical_Feature"/>
</rdfs:Class>
<rdf:Property rdf:about="L1_digitized">
<rdfs:comment>This property associates an instance of D2 Digitization Process with an instance of E18 Physical Thing which is a material thing.
This property is a specialisation of P39 measured (was measured by).
</rdfs:comment>
<rdfs:domain rdf:resource="D2_Digitization_Process"/>
<rdfs:range rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E18_Physical_Thing"/>
<rdfs:subPropertyOf rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P39_measured"/>
</rdf:Property>
<rdf:Property rdf:about="L1i_was_digitized_by">
<rdfs:domain rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E18_Physical_Thing"/>
<rdfs:range rdf:resource="D2_Digitization_Process"/>
<rdfs:subPropertyOf rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P39i_was_measured_by"/>
</rdf:Property>
<rdf:Property rdf:about="L2_used_as_source">
<rdfs:comment>This property associates an instance of D10 Software Execution with an instance of D1 Digital Object
which is used as a source, a software essential for the performance.
This property is a specialisation of L10F had input (was input of).
</rdfs:comment>
<rdfs:domain rdf:resource="D10_Software_Execution"/>
<rdfs:range rdf:resource="D1_Digital_Object"/>
<rdfs:subPropertyOf rdf:resource="L10_had_input"/>
</rdf:Property>
<rdf:Property rdf:about="L2i_was_source_for">
<rdfs:domain rdf:resource="D1_Digital_Object"/>
<rdfs:range rdf:resource="D10_Software_Execution"/>
<rdfs:subPropertyOf rdf:resource="L10i_was_input_of"/>
</rdf:Property>
<rdf:Property rdf:about="L4_has_preferred_label">
<rdfs:comment>This property associates an instance of E1 Entity with an instance of resource used as a preferred lexical label.
This property is a specialisation of rdf schema label.
</rdfs:comment>
<rdfs:domain rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E1_CRM_Entity"/>
<rdfs:range rdf:resource="http://www.w3.org/2000/01/rdf-schema#Literal"/>
<rdfs:subPropertyOf rdf:resource="http://www.w3.org/2000/01/rdf-schema#label"/>
</rdf:Property>
<rdf:Property rdf:about="L10_had_input">
<rdfs:comment>This property associates an instance of D7 Digital Machine Event with an instance of D1 Digital Object
which is the input used to specify the machine action.
This property is a specialisation of P16 used specific object(was used for).
</rdfs:comment>
<rdfs:domain rdf:resource="D7_Digital_Machine_Event"/>
<rdfs:range rdf:resource="D1_Digital_Object"/>
<rdfs:subPropertyOf rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P16_used_specific_object"/>
</rdf:Property>
<rdf:Property rdf:about="L10i_was_input_of">
<rdfs:domain rdf:resource="D1_Digital_Object"/>
<rdfs:range rdf:resource="D7_Digital_Machine_Event"/>
<rdfs:subPropertyOf rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P16i_was_used_for"/>
</rdf:Property>
<rdf:Property rdf:about="L11_had_output">
<rdfs:comment>This property associates an instance of D7 Digital Machine Event with an instance of D1 Digital Object
which is the output of the activity.
This property is a specialisation of P94 has created (was created by).</rdfs:comment>
<rdfs:domain rdf:resource="D7_Digital_Machine_Event"/>
<rdfs:range rdf:resource="D1_Digital_Object"/>
<rdfs:subPropertyOf rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P94_has_created"/>
</rdf:Property>
<rdf:Property rdf:about="L11i_was_output_of">
<rdfs:domain rdf:resource="D1_Digital_Object"/>
<rdfs:range rdf:resource="D7_Digital_Machine_Event"/>
<rdfs:subPropertyOf rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P94i_was_created_by"/>
</rdf:Property>
<rdf:Property rdf:about="L12_happened_on_device">
<rdfs:comment>This property associates an instance of D7 Digital Machine Event with an object,
the D8 Digital Device, which happened with, e.g a capturing event that happened on/with a digital camera, etc.
This property is a specialisation of P12 occurred in the presence of (was present at).</rdfs:comment>
<rdfs:domain rdf:resource="D7_Digital_Machine_Event"/>
<rdfs:range rdf:resource="D8_Digital_Device"/>
<rdfs:subPropertyOf rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P12_occurred_in_the_presence_of"/>
</rdf:Property>
<rdf:Property rdf:about="L12i_was_device_for">
<rdfs:domain rdf:resource="D8_Digital_Device"/>
<rdfs:range rdf:resource="D7_Digital_Machine_Event"/>
<rdfs:subPropertyOf rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P12i_was_present_at"/>
</rdf:Property>
<rdf:Property rdf:about="L13_used_parameters">
<rdfs:comment>This property associates an instance of D10 Software Execution with a digital object
used as a parameter during the process.This property is a specialisation of L1O had input (was input of).</rdfs:comment>
<rdfs:domain rdf:resource="D10_Software_Execution"/>
<rdfs:range rdf:resource="D1_Digital_Object"/>
<rdfs:subPropertyOf rdf:resource="L10_had_input"/>
</rdf:Property>
<rdf:Property rdf:about="L13i_parameters_for">
<rdfs:domain rdf:resource="D1_Digital_Object"/>
<rdfs:range rdf:resource="D10_Software_Execution"/>
<rdfs:subPropertyOf rdf:resource="L10i_was_input_of"/>
</rdf:Property>
<rdf:Property rdf:about="L14_transferred">
<rdfs:comment>This property identifies a digital object transferred by a D12 Data Transfer Event.
This property is a specialisation of L11 had output (was output of).</rdfs:comment>
<rdfs:domain rdf:resource="D12_Data_Transfer_Event"/>
<rdfs:range rdf:resource="D1_Digital_Object"/>
<rdfs:subPropertyOf rdf:resource="L10_had_input"/>
<rdfs:subPropertyOf rdf:resource="L11_had_output"/>
</rdf:Property>
<rdf:Property rdf:about="L14i_was_transferred_by">
<rdfs:domain rdf:resource="D1_Digital_Object"/>
<rdfs:range rdf:resource="D12_Data_Transfer_Event"/>
<rdfs:subPropertyOf rdf:resource="L10i_was_input_of"/>
<rdfs:subPropertyOf rdf:resource="L11i_was_output_of"/>
</rdf:Property>
<rdf:Property rdf:about="L15_has_sender">
<rdfs:comment>This property identifies a digital device used as a medium on which data are transferred
through a D12 Data Transfer Event.</rdfs:comment>
<rdfs:domain rdf:resource="D12_Data_Transfer_Event"/>
<rdfs:range rdf:resource="D8_Digital_Device"/>
<rdfs:subPropertyOf rdf:resource="L12_happened_on_device"/>
</rdf:Property>
<rdf:Property rdf:about="L15i_was_sender_for">
<rdfs:domain rdf:resource="D8_Digital_Device"/>
<rdfs:range rdf:resource="D12_Data_Transfer_Event"/>
<rdfs:subPropertyOf rdf:resource="L12i_was_device_for"/>
</rdf:Property>
<rdf:Property rdf:about="L16_has_receiver">
<rdfs:comment>This property identifies a digital device used as a medium to receive data
through a D12 Data Transfer Event.</rdfs:comment>
<rdfs:domain rdf:resource="D12_Data_Transfer_Event"/>
<rdfs:range rdf:resource="D8_Digital_Device"/>
<rdfs:subPropertyOf rdf:resource="L12_happened_on_device"/>
</rdf:Property>
<rdf:Property rdf:about="L16i_was_receiver_for">
<rdfs:domain rdf:resource="D8_Digital_Device"/>
<rdfs:range rdf:resource="D12_Data_Transfer_Event"/>
<rdfs:subPropertyOf rdf:resource="L12i_was_device_for"/>
</rdf:Property>
<rdf:Property rdf:about="L17_measured_thing_of_type">
<rdfs:comment>This property associates an instance of D11 Digital Measurement Event with the instance of E55
Type of object to which it applied. This property is a specialisation of P125 used object of type. </rdfs:comment>
<rdfs:domain rdf:resource="D11_Digital_Measurement_Event"/>
<rdfs:range rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E55_Type"/>
<rdfs:subPropertyOf rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P125_used_object_of_type"/>
</rdf:Property>
<rdf:Property rdf:about="L17i_was_type_of_thing_measured_by">
<rdfs:domain rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E55_Type"/>
<rdfs:range rdf:resource="D11_Digital_Measurement_Event"/>
<rdfs:subPropertyOf rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P125i_was_type_of_object_used_in"/>
</rdf:Property>
<rdf:Property rdf:about="L18_has_modified">
<rdfs:comment>This property identifies a Digital Information Carrier modified in a Digital Machine Event.
This property is a specialisation of P31 has modified.</rdfs:comment>
<rdfs:domain rdf:resource="D7_Digital_Machine_Event"/>
<rdfs:range rdf:resource="D13_Digital_Information_Carrier"/>
<rdfs:subPropertyOf rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P31_has_modified"/>
</rdf:Property>
<rdf:Property rdf:about="L18i_was_modified_by">
<rdfs:domain rdf:resource="D13_Digital_Information_Carrier"/>
<rdfs:range rdf:resource="D7_Digital_Machine_Event"/>
<rdfs:subPropertyOf rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P31i_was_modified_by"/>
</rdf:Property>
<rdf:Property rdf:about="L19_stores">
<rdfs:comment>This property associates an instance of a D13 Digital Information Carrier with the instance of Digital Object
that is stored on it. This property is a specialisation of P128 carries.</rdfs:comment>
<rdfs:domain rdf:resource="D13_Digital_Information_Carrier"/>
<rdfs:range rdf:resource="D1_Digital_Object"/>
<rdfs:subPropertyOf rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P128_carries"/>
</rdf:Property>
<rdf:Property rdf:about="L19i_is_stored_on">
<rdfs:domain rdf:resource="D1_Digital_Object"/>
<rdfs:range rdf:resource="D13_Digital_Information_Carrier"/>
<rdfs:subPropertyOf rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P128i_is_carried_by"/>
</rdf:Property>
<rdf:Property rdf:about="L20_has_created">
<rdfs:comment>This property identifies a Data Object that came into existence as a result of a D11 Digital Measurement Event.
This property is a specialisation of P40 observed dimension and L11 had output.</rdfs:comment>
<rdfs:domain rdf:resource="D11_Digital_Measurement_Event"/>
<rdfs:range rdf:resource="D9_Data_Object"/>
<rdfs:subPropertyOf rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P40_observed_dimension"/>
<rdfs:subPropertyOf rdf:resource="L11_had_output"/>
</rdf:Property>
<rdf:Property rdf:about="L20i_was_created_by">
<rdfs:domain rdf:resource="D9_Data_Object"/>
<rdfs:range rdf:resource="D11_Digital_Measurement_Event"/>
<rdfs:subPropertyOf rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P40i_was_observed_in"/>
<rdfs:subPropertyOf rdf:resource="L11i_was_output_of"/>
</rdf:Property>
<rdf:Property rdf:about="L21_used_as_derivation_source">
<rdfs:comment>This property associates an instance of a D3 Formal Derivation with the instance of D1 Digital Object that is used as a derivation source.</rdfs:comment>
<rdfs:domain rdf:resource="D3_Formal_Derivation"/>
<rdfs:range rdf:resource="D1_Digital_Object"/>
<rdfs:subPropertyOf rdf:resource="L2_used_as_source"/>
</rdf:Property>
<rdf:Property rdf:about="L21i_was_derivation_source_for">
<rdfs:domain rdf:resource="D1_Digital_Object"/>
<rdfs:range rdf:resource="D3_Formal_Derivation"/>
<rdfs:subPropertyOf rdf:resource="L2i_was_source_for"/>
</rdf:Property>
<rdf:Property rdf:about="L22_created_derivative">
<rdfs:comment>This property associates an instance of D3 Formal Derivation with the Digital Object it used to create a version of.
This property is a specialisation of L11 had output.</rdfs:comment>
<rdfs:domain rdf:resource="D3_Formal_Derivation"/>
<rdfs:range rdf:resource="D1_Digital_Object"/>
<rdfs:subPropertyOf rdf:resource="L11_had_output"/>
</rdf:Property>
<rdf:Property rdf:about="L22i_was_derivative_created_by">
<rdfs:domain rdf:resource="D1_Digital_Object"/>
<rdfs:range rdf:resource="D3_Formal_Derivation"/>
<rdfs:subPropertyOf rdf:resource="L11i_was_output_of"/>
</rdf:Property>
<rdf:Property rdf:about="L23_used_software_or_firmware">
<rdfs:comment>This property associates an instance of D7 Digital Machine Event with the instance of D14 Software that had used.
This property is a specialisation of P16 used specific object.</rdfs:comment>
<rdfs:domain rdf:resource="D7_Digital_Machine_Event"/>
<rdfs:range rdf:resource="D14_Software"/>
<rdfs:subPropertyOf rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P16_used_specific_object"/>
</rdf:Property>
<rdf:Property rdf:about="L23i_was_software_or_firmware_used_by">
<rdfs:domain rdf:resource="D14_Software"/>
<rdfs:range rdf:resource="D7_Digital_Machine_Event"/>
<rdfs:subPropertyOf rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P16i_was_used_for"/>
</rdf:Property>
<rdf:Property rdf:about="L24_created_logfile">
<rdfs:comment>This property identifies the logfile that was created by a D10 Software Execution in order to record all the activities in the system.</rdfs:comment>
<rdfs:domain rdf:resource="D10_Software_Execution"/>
<rdfs:range rdf:resource="D1_Digital_Object"/>
<rdfs:subPropertyOf rdf:resource="L11_had_output"/>
</rdf:Property>
<rdf:Property rdf:about="L24i_was_logfile_created_by">
<rdfs:domain rdf:resource="D1_Digital_Object"/>
<rdfs:range rdf:resource="D10_Software_Execution"/>
<rdfs:subPropertyOf rdf:resource="L11i_was_output_of"/>
</rdf:Property>
<rdf:Property rdf:about="L29_has_responsible_organization">
<rdfs:comment>This property describes the participation of a Legal Body in being responsible for the outcome of a specific activity.
This property is a specialisation of P14 carried out by.</rdfs:comment>
<rdfs:domain rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E7_Activity"/>
<rdfs:range rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E40_Legal_Body"/>
<rdfs:subPropertyOf rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P14_carried_out_by"/>
</rdf:Property>
<rdf:Property rdf:about="L29i_is_responsible_organization_for">
<rdfs:domain rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E40_Legal_Body"/>
<rdfs:range rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E7_Activity"/>
<rdfs:subPropertyOf rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P14i_performed"/>
</rdf:Property>
<rdf:Property rdf:about="L30_has_operator">
<rdfs:comment>This property describes the activity that is being operated by a person.
This property is a specialisation of P14 carried out by.</rdfs:comment>
<rdfs:domain rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E7_Activity"/>
<rdfs:range rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E21_Person"/>
<rdfs:subPropertyOf rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P14_carried_out_by"/>
</rdf:Property>
<rdf:Property rdf:about="L30i_is_operator_of">
<rdfs:domain rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E21_Person"/>
<rdfs:range rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E7_Activity"/>
<rdfs:subPropertyOf rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P14i_performed"/>
</rdf:Property>
<rdf:Property rdf:about="L31_has_starting_date-time">
<rdfs:comment>This property allows the starting point for a D7 Digital Machine Event to be situated.
This property expresses the approximation of the starting date of a time span.</rdfs:comment>
<rdfs:domain rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E5_Event"/>
<rdfs:range rdf:resource="http://www.w3.org/2001/XMLSchema#dateTime"/>
<rdfs:subPropertyOf rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P82a_begin_of_the_begin"/>
</rdf:Property>
<rdf:Property rdf:about="L32_has_ending_date-time">
<rdfs:comment>This property allows the ending point for a D7 Digital Machine Event to be situated.
This property expresses the approximation of the ending date of a time span.</rdfs:comment>
<rdfs:domain rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E5_Event"/>
<rdfs:range rdf:resource="http://www.w3.org/2001/XMLSchema#dateTime"/>
<rdfs:subPropertyOf rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P82b_end_of_the_end"/>
</rdf:Property>
<rdf:Property rdf:about="L33_has_maker">
<rdfs:comment>This property identifies the maker, the actor who is responsible for the production of a device,
a computer, a digital camera, any kind of a machine that has been produced.
This property is a shortcut of a more fully developed path from CRM E12 Production:P108 has produced:E24 Physical Man-Made Thing.
In this case, there is no need to describe the more detailed property through a production event,so L33 has maker is reccomended to be used instead. </rdfs:comment>
<rdfs:domain rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E72_Legal_Object"/>
<rdfs:range rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E39_Actor"/>
</rdf:Property>
<rdf:Property rdf:about="L33i_is_maker_of">
<rdfs:domain rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E39_Actor"/>
<rdfs:range rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E72_Legal_Object"/>
</rdf:Property>
<!-- EXTENTION for contractor and commissioner -->
<rdf:Property rdf:about="L34_has_contractor">
<rdfs:comment>This property describes the participation of a Legal Body in being contractor for the outcome of a specific activity.
This property is a specialisation of L29_has_responsible_organization.</rdfs:comment>
<rdfs:domain rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E7_Activity"/>
<rdfs:range rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E40_Legal_Body"/>
<rdfs:subPropertyOf rdf:resource="L29_has_responsible_organization"/>
</rdf:Property>
<rdf:Property rdf:about="L34i_is_contractor_for">
<rdfs:domain rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E40_Legal_Body"/>
<rdfs:range rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E7_Activity"/>
<rdfs:subPropertyOf rdf:resource="L29i_is_responsible_organization_for"/>
</rdf:Property>
<rdf:Property rdf:about="L35_has_commissioner">
<rdfs:comment>This property describes the participation of a Legal Body in being commissioner for the outcome of a specific activity.
This property is a specialisation of L29_has_responsible_organization.</rdfs:comment>
<rdfs:domain rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E7_Activity"/>
<rdfs:range rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E40_Legal_Body"/>
<rdfs:subPropertyOf rdf:resource="L29_has_responsible_organization"/>
</rdf:Property>
<rdf:Property rdf:about="L35i_is_commissioner_for">
<rdfs:domain rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E40_Legal_Body"/>
<rdfs:range rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E7_Activity"/>
<rdfs:subPropertyOf rdf:resource="L29i_is_responsible_organization_for"/>
</rdf:Property>
<!-- END of EXTENTION for contractor and commissioner-->
<rdf:Property rdf:about="L43_annotates">
<rdfs:comment>This property describes the associations between objects or areas of objects of the RI,
with other objects or regions or persons, places, events..</rdfs:comment>
<rdfs:domain rdf:resource="D29_Annotation_Object"/>
<rdfs:range rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E1_CRM_Entity"/>
</rdf:Property>
<rdf:Property rdf:about="L43i_is_annotated_by">
<rdfs:domain rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E1_CRM_Entity"/>
<rdfs:range rdf:resource="D29_Annotation_Object"/>
</rdf:Property>
<rdf:Property rdf:about="L47_has_comment">
<rdfs:comment>This property is a specialisation of P3 has note and associates a comment with an instance of an object E1 CRM Entity.</rdfs:comment>
<rdfs:domain rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E1_CRM_Entity"/>
<rdfs:range rdf:resource="http://www.w3.org/2000/01/rdf-schema#Literal"/>
<rdfs:subPropertyOf rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P3_has_note"/>
</rdf:Property>
<rdf:Property rdf:about="L48_created_annotation">
<rdfs:comment>This property identifies the D29 Annotation Object (associations) that came into existence as a result of a D30 Annotation Event.
This property is a specialisation of P94 has created.</rdfs:comment>
<rdfs:domain rdf:resource="D30_Annotation_Event"/>
<rdfs:range rdf:resource="D29_Annotation_Object"/>
<rdfs:subPropertyOf rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P94_has_created"/>
</rdf:Property>
<rdf:Property rdf:about="L48i_was_annotation_created_by">
<rdfs:domain rdf:resource="D29_Annotation_Object"/>
<rdfs:range rdf:resource="D30_Annotation_Event"/>
<rdfs:subPropertyOf rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P94i_was_created_by"/>
</rdf:Property>
<rdf:Property rdf:about="L49_is_primary_area_of">
<rdfs:comment>This property describes the association between a particular area declared in an original digital object.
This property is a specialisation of P106 is composed of.</rdfs:comment>
<rdfs:domain rdf:resource="D35_Area"/>
<rdfs:range rdf:resource="D1_Digital_Object"/>
<rdfs:subPropertyOf rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P106i_forms_part_of"/>
</rdf:Property>
<rdf:Property rdf:about="L49i_has_primary_area">
<rdfs:domain rdf:resource="D1_Digital_Object"/>
<rdfs:range rdf:resource="D35_Area"/>
<rdfs:subPropertyOf rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P106_is_composed_of"/>
</rdf:Property>
<rdf:Property rdf:about="L50_is_propagated_area_of">
<rdfs:comment>This property describes the association between an area and the digital object to which it is propagated.
This property is a specialisation of P106 is composed of.</rdfs:comment>
<rdfs:domain rdf:resource="D35_Area"/>
<rdfs:range rdf:resource="D1_Digital_Object"/>
<rdfs:subPropertyOf rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P106i_forms_part_of"/>
</rdf:Property>
<rdf:Property rdf:about="L50i_has_propagated_area">
<rdfs:domain rdf:resource="D1_Digital_Object"/>
<rdfs:range rdf:resource="D35_Area"/>
<rdfs:subPropertyOf rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P106_is_composed_of"/>
</rdf:Property>
<rdf:Property rdf:about="L51_has_first_name">
<rdfs:comment>This property defines a personal name used to identify a person.</rdfs:comment>
<rdfs:domain rdf:resource="D21_Person_Name"/>
<rdfs:range rdf:resource="http://www.w3.org/2000/01/rdf-schema#Literal"/>
<rdfs:subPropertyOf rdf:resource="http://www.w3.org/2000/01/rdf-schema#label"/>
</rdf:Property>
<rdf:Property rdf:about="L52_has_last_name">
<rdfs:comment>This property defines the last name used to identify a person.
This property is a specialisation of L4 has preferred label.</rdfs:comment>
<rdfs:domain rdf:resource="D21_Person_Name"/>
<rdfs:range rdf:resource="http://www.w3.org/2000/01/rdf-schema#Literal"/>
<rdfs:subPropertyOf rdf:resource="L4_has_preferred_label"/>
</rdf:Property>
<rdf:Property rdf:about="L53_is_not_uniquely_identified_by">
<rdfs:comment>This property describes a non unique identification applied to E1 CRM Entity.</rdfs:comment>
<rdfs:domain rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E1_CRM_Entity"/>
<rdfs:range rdf:resource="http://www.w3.org/2000/01/rdf-schema#Literal"/>
<rdfs:subPropertyOf rdf:resource="http://www.w3.org/2000/01/rdf-schema#label"/>
</rdf:Property>
<rdf:Property rdf:about="L54_is_same-as">
<rdfs:comment>This property describes the association kind of "same as" between objects. It is used to declare that two or more objects are
exactly the same.</rdfs:comment>
<rdfs:domain rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E1_CRM_Entity"/>
<rdfs:range rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E1_CRM_Entity"/>
</rdf:Property>
<rdf:Property rdf:about="L54i_is_same-as">
<rdfs:comment>This property describes the association kind of "same as" between objects. It is used to declare that two or more objects are
exactly the same.</rdfs:comment>
<rdfs:domain rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E1_CRM_Entity"/>
<rdfs:range rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E1_CRM_Entity"/>
</rdf:Property>
<rdf:Property rdf:about="L55_has_inventory_no">
<rdfs:comment>This property records the inventory number that was used to identify an instance of E1 CRM Entity
at the time this property was record. This property is a specialisation of L53F is not uniquely identified by.</rdfs:comment>
<rdfs:domain rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E1_CRM_Entity"/>
<rdfs:range rdf:resource="http://www.w3.org/2000/01/rdf-schema#Literal"/>
<rdfs:subPropertyOf rdf:resource="L53_is_not_uniquely_identified_by"/>
</rdf:Property>
<rdf:Property rdf:about="L56_has_pixel_width">
<rdfs:comment>This property records the pixel width of the data object; it approximates a dimension that is
part of the image data analysis.This property is a specialisation of P90 has value.</rdfs:comment>
<rdfs:domain rdf:resource="D9_Data_Object"/>
<rdfs:range rdf:resource="http://www.w3.org/2000/01/rdf-schema#Literal"/>
<rdfs:subPropertyOf rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P90_has_value"/>
</rdf:Property>
<rdf:Property rdf:about="L57_has_pixel_height">
<rdfs:comment>This property records the pixel height of the data object; it approximates a dimension that is
part of the image data analysis.This property is a specialisation of P90 has value.</rdfs:comment>
<rdfs:domain rdf:resource="D9_Data_Object"/>
<rdfs:range rdf:resource="http://www.w3.org/2000/01/rdf-schema#Literal"/>
<rdfs:subPropertyOf rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P90_has_value"/>
</rdf:Property>
<rdf:Property rdf:about="L59_has_serial_number">
<rdfs:comment>This property records the serial number that was assigned to identify an instance of E22 Man Made Object.
This property is a specialisation of L53 is not uniquely identified by.</rdfs:comment>
<rdfs:domain rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E22_Man-Made_Object"/>
<rdfs:range rdf:resource="http://www.w3.org/2000/01/rdf-schema#Literal"/>
<rdfs:subPropertyOf rdf:resource="L53_is_not_uniquely_identified_by"/>
</rdf:Property>
<rdf:Property rdf:about="L60_documents">
<rdfs:comment>This property describes the CRM Entities documented by instances of Digitization Processes.
This property is a specialisation of P140 assigned attribute to.</rdfs:comment>
<rdfs:domain rdf:resource="D2_Digitization_Process"/>
<rdfs:range rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E1_CRM_Entity"/>
<rdfs:subPropertyOf rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P140_assigned_attribute_to"/>
</rdf:Property>
<rdf:Property rdf:about="L60i_is_documented_by">
<rdfs:domain rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E1_CRM_Entity"/>
<rdfs:range rdf:resource="D2_Digitization_Process"/>
<rdfs:subPropertyOf rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P140i_was_attributed_by"/>
</rdf:Property>
<rdf:Property rdf:about="L61_was_ongoing_at">
<rdfs:comment>This property describes the minimum period of time covered by a digital machine event. It
identifies the minimum extent of the event. This property is a specialisation of P81 ongoing throughout.</rdfs:comment>
<rdfs:domain rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E5_Event"/>
<rdfs:range rdf:resource="http://www.w3.org/2001/XMLSchema#dateTime"/>
<rdfs:subPropertyOf rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P81a_end_of_the_begin"/>
<rdfs:subPropertyOf rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P81b_begin_of_the_end"/>
</rdf:Property>
</rdf:RDF>

489
ontologies/cidoc-crm-ontology-master/CRMgeo_v1.2.rdfs.xml Normal file
View File

@@ -0,0 +1,489 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!--
CRMgeo 1.2 Encoded in RDFS
RDFS updated by FORTH-ICS February 6, 2015
Encoding Rules:
1. The RDF spelling rules do not allow blanks. Hence we have replaced them by underscores.
The blank between the concept identifier and concept name is replaced by underscore too.
For instance "SP6_Declarative_Place" or "Q2_occupied".
2. RDF does not allow to instantiate properties beginning from a range value.
Therefore, each CRMgeo property is represented as two RDFS properties.
For instance "Q2 occupied (is occupied by)" is represented as:
"Q2_occupied" for the domain to range direction and "Q2i_is_occupied_by" for the range to domain direction.
-->
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#"
xml:base="http://www.ics.forth.gr/isl/CRMgeo/"
xml:lang="en">
<rdfs:Class rdf:about="http://www.cidoc-crm.org/cidoc-crm/E16_Measurement">
<rdfs:subClassOf rdf:resource="S4_Observation"/>
</rdfs:Class>
<rdfs:Class rdf:about="http://www.cidoc-crm.org/cidoc-crm/E92_Spacetime_Volume">
<rdfs:subClassOf rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E1_CRM_Entity"/>
<rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string">Scope note:This class comprises 4 dimensional possibly fuzzy point sets (volumes) in physical spacetime regardless its true geometric form (S). They may derive their identity from being the extent of a material phenomenon or from being the interpretation of an expression (I) defining an extent in Space Time. The duration of existence of an instance of a spacetime volume is trivially its projection on time (E).
Examples:
• the spacetime Volume of the Event of Ceasars murdering
• the spacetime Volume where and when the carbon 14 dating of the "Schoeninger Speer II" in 1996 took place
• the spatio-temporal trajectory of the H.M.S. Victory from its building to its actual location
• the spacetime volume defined by a polygon approximating the Danube river flood in Austria between 6th and 9th of August 2002
</rdfs:comment>
</rdfs:Class>
<rdfs:Class rdf:about="SP1_Phenomenal_Spacetime_Volume">
<rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
>Scope note: This class comprises the 4 dimensional point sets (volumes) (S) which material phenomena (I) occupy in Space-Time (S). An instance of S1 Space Time Volume represents the true (I) extent of an instance of E4 Period in spacetime or the true (I) extent of the trajectory of an instance of E18 Physical Thing during the course of its existence, from production to destruction. A fuzziness of the extent lies in the very nature of the phenomenon, and not in the shortcomings of observation (U). The degree of fuzziness with respect to the scale of the phenomenon may vary widely, but the extent is never exact in a mathematical sense. According to modern physics, points in space-time are absolute with respect to the physical phenomena happening at them, regardless the so-called Galilean relativity of spatial or temporal reference systems in terms of which an observer may describe them. Following the theory, points relative to different spatial or temporal reference systems can be related if common points of phenomena in space-time are known in different systems. Instances of S1 Space-Time Volume are sets of such absolute space-time points of phenomena (I).The (Einstein) relativity of spatial and temporal distances is of no concern for the scales of things in the cultural-historical discourse, but does not alter the above principles.[ØE8] The temporal projection of an instance of SP1 Space-Time Volume defines an E52 Time-Span while its spatial projection defines an SP2 Phenomenal Place[ØE9]. The true location of an instance of E18 Physical Thing during some time-span can be regarded as the spatial projection of the restriction of its trajectory to the respective time-span.
Examples:
• The Space Time Volume of the Event of Ceasars murdering
• The Space Time Volume where and when the carbon 14 dating of the "Schoeninger Speer II" in 1996 took place
• The spatio-temporal trajectory of the H.M.S. Victory from its building to its actual location
• The Space Time Volume of the temple in Abu Simbel before its removal</rdfs:comment>
<rdfs:subClassOf rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E92_Spacetime_Volume"/>
</rdfs:Class>
<rdfs:Class rdf:about="SP2_Phenomenal_Place">
<rdfs:subClassOf rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E53_Place"/>
<rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
>Scope note: This class comprises instances of E53 Place (S) whose extent (U) and position is defined by the spatial projection of the spatiotemporal extent of a real world phenomenon that can be observed or measured. The spatial projection depends on the instance of S3 Reference Space onto which the extent of the phenomenon is projected. In general, there are no limitations to the number of Reference Spaces one could regard, but only few choices are relevant for the cultural-historical discourse. Typical for the archaeological discourse is to choose a reference space with respect to which the remains of some events would stay at the same place, for instance, relative to the bedrock of a continental plate. On the other side, for the citizenship of babies born in aeroplanes, the space in which the boundaries of the overflown state are defined may be relevant (I). Instances of SP2 Phenomenal Place exist as long as the respective reference space is defined. Note that we can talk in particular about what was at a place in a country before a city was built there, i.e., before the time the event occurred by which the place is defined, but we cannot talk about the place of earth before it came into existence due to lack of a reasonable reference space (E).
Examples:
• The place where the murder of Ceasar happened
• Place on H.M.S. Victory at which Nelson died
• The Place of the Varus Battle
• The volume in space of my vine glass
• The place the H.M.S Victory occupied over the seafloor when Nelson died
• The space enclosed by this room
• The space in borehole Nr. 405</rdfs:comment>
</rdfs:Class>
<rdfs:Class rdf:about="SP3_Reference_Space">
<rdfs:subClassOf rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E1_CRM_Entity"/>
<rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
>Scope note: This class comprises the (typically Euclidian) Space (S) that is at rest (I) in relation to an instance of E18 Physical Thing and extends (U) infinitely beyond it. It is the space in which we typically expect things to stay in place if no particular natural or human distortion processes occur. This definition requires that at least essential parts of the respective physical thing have a stability of form. The degree of this stability (e.g., elastic deformation of a ship on sea, landslides, geological deformations) limits the precision to which an instance of SP3 Reference Space is defined. It is possible to construct types of (non Euclidian) reference spaces which adapt to elastic deformations or have other geometric and dynamic properties to adapt to changes of form of the reference object, but they are of rare utility in the cultural-historical discourse. [ØE11]
An instance of SP3 Reference Space begins to exist with the largest thing that is at rest in it and ceases to exist with its E6 Destruction[ØE12]. If other things are at rest in the same space and their time-span of existence falls within the one of the reference object, they share the same reference space (I). It has therefore the same temporal extent (time-span of existence) as the whole of the E18 Physical Things it is at rest with (E).
Examples:
• The Space inside and around H.M.S. Victory while it is moving through the Atlantic Ocean
• The Space inside and around the Eurasian Continental Plate
• The Space inside and around the Earth
• The Space inside and around the Solar system</rdfs:comment>
</rdfs:Class>
<rdfs:Class rdf:about="SP4_Spatial_Coordinate_Reference_System">
<rdfs:subClassOf rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E29_Design_or_Procedure"/>
<rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
>Scope note: This class compromises systems that are used to describe locations in a SP3 Reference Space (S). An instance of SP4 Spatial Coordinate Reference System is composed of two parts: The first is a Coordinate System which is a set of coordinate axes with specified units of measurement and axis directions. The second part is a set of reference features at rest in the Reference Space it describes in the real world that relate the Coordinate System to real world locations (U) and fix it with respect to the reference object of its Reference Space .
In surveying and geodesy, instance of SP4 Spatial Coordinate Reference System are called a datum. In the case of spatial coordinate reference systems for the earth the datum consists of the reference points and an ellipsoid that approximates the shape of the earth. National systems often use ellipsoids that approximate their territory best and shift them in an appropriate position relative to the earth while WGS84 is an ellipsoid for the whole earth and used in GPS receivers. In engineering a datum is a reference feature of an object used to create a reference system for measurement.The set of reference features in the real world are subset of E26 Physical Feature that are within the described reference space at rest and pertain to the E18 Physical Thing the reference space is at rest with.
SP4 Spatial Coordinate Reference Systems have a validity for a certain spatial extent of the SP3 Reference Space and in addition a temporal validity. The combination of coordinate reference system and datum provides a unique identity (I). SP4 Spatial Coordinate Reference Systems may be defined for the earth, moving objects like planes or ships, linear features like boreholes or local systems. If there is a standardised identifier system available, such as EPSG codes, it should be used.
Examples:
• Longitude-Latitude(ellipsoidal Coordinate System) in WGS84 (Datum)
• EPSG 3241
• the coordinate system to describe locations on H.M.S. Victory taking the deck foundation of the middle mast as origin, the mast as z axis, the line at right angle to the bow line as x axis and a right angle to both as y axis.
• The printed lines of the millimeter paper on which an archaeological feature is drawn</rdfs:comment>
</rdfs:Class>
<rdfs:Class rdf:about="SP5_Geometric_Place_Expression">
<rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
>Scope note: This class comprises definitions of places by quantitative expressions. An instance of SP5 Geometric Place Expression can be seen as a prescription of how to find the location meant by this expression in the real world (S), which is based on measuring where the quantities referred to in the expression lead to, beginning from the reference points of the respective reference system.
A form of expression may be geometries or map elements defined in a SP4 Spatial Coordinate Reference System that unambiguously identify locations in a SP3 Reference Space. Other forms may refer to areas confined by imaginary lines connecting Phenomenal Places such as trees, islands, cities, mountain tops.
The identity of a SP5 Place Expression is based on its script or symbolic form (I). Several SP5 Place Expressions can denote the same SP6 Declarative Place.
Instances of SP5 Geometric Place Expressions that exist in one SP4 Spatial Coordinate Reference System can be transformed to geometries in other SP4 Spatial Coordinate Reference System if there is a known and valid transformation. The product of the transformation in general defines a new instance of SP6 Declarative Place, albeit close to the source of the transformation. This can be due to distortions resulting from the transformation and the limited precision by which the relative position of the reference points differing between the respective reference systems are determined.     
Examples:
• Coordinate Information in GML like &lt;gml:Point gml:id="p21" srsName="http://www.opengis.net/def/crs/EPSG/0/4326"&gt; &lt;gml:coordinates&gt;45.67, 88.56&lt;/gml:coordinates&gt; &lt;/gml:Point&gt;
• a polygon defining the extent of France</rdfs:comment>
<rdfs:subClassOf rdf:resource="http://www.opengis.net/ont/geosparql#Geometry"/>
<rdfs:subClassOf rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E73_Information_Object"/>
<rdfs:subClassOf rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E47_Spatial_Coordinates"/>
</rdfs:Class>
<rdfs:Class rdf:about="SP6_Declarative_Place">
<rdfs:subClassOf rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E53_Place"/>
<rdfs:subClassOf rdf:resource="http://www.opengis.net/ont/geosparql#Geometry"/>
<rdfs:subClassOf rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E89_Propositional_Object"/>
<rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string">Scope note: This class comprises instances of E53 Place (S) whose extent (U) and position is defined by a SP5 Geometric Place Expression (S). There is one implicit or explicit SP3 Reference Space in which the SP5 Place Expression describes the intended place. Even though SP5 Geometric Place Expressions have an unlimited precision, measurement devices and the precision of the position of reference features relating the SP4 Spatial Coordinate Reference System to a SP3 Reference Space impose limitations to the determination of an SP6 Declarative Place in the real world (U).
Several SP5 Geometric Place Expressions may denote the same SP6 Declarative Place if their precision falls within the same range (I).
Instances of SP6 Declarative Places may be used to approximate instances of E53 Places or parts of them. They may as well be used to define the location and spatial extent of property rights or national borders.
Examples:
• the place defined by &lt;gml:Point gml:id="p21" srsName="http://www.opengis.net/def/crs/EPSG/0/4326"&gt; &lt;gml:coordinates&gt;45.67, 88.56&lt;/gml:coordinates&gt; &lt;/gml:Point&gt;
• the place defined by a line approximating the Danube river
• The place of the Orinoco river defined in the map of Diego Ribeiro in 1529
• the place defined through a polygon that represents the boundaries of the UK in the year 2003
</rdfs:comment>
</rdfs:Class>
<rdfs:Class rdf:about="SP7_Declarative_Spacetime_Volume">
<rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
>Scope note: This class comprises instances of SP8 Spacetime Volumes (S) whose temporal and spatial extent (U) and position is defined by a SP12 Spacetime Volume Expression. There is one implicit or explicit SP3 Reference Space in which the SP12 Spacetime Volume Expression describes the intended Spacetime Volume. As we restrict the model to Galilean physics and explicitly exclude systems with velocities close to the speed of light we do not model a “Reference Time” as it would be necessary for relativistic physics. This implies that there is only one Reference Time.
Even though SP12 Spacetime Volume Expressions have an unlimited precision, measurement devices and the precision of the position of reference features relating the SP4 Spatial Coordinate Reference System to a SP3 Reference Space impose limitations to the determination of the spatial part of a SP7 Declarative Spacetime Volume in the real world (U).
The same limitation to precision is true for the temporal part of a SP7 Declarative Spacetime Volume due to precision of time measurement devices and of the determination of the reference event of a SP11 Temporal Reference System.
Several SP12 Spacetime Volume Expressions may denote the same SP7 Declarative Spacetime Volume if their precision falls within the same range (I).
Instances of SP7 Declarative Spacetime Volumes may be used to approximate instances of SP8 Spacetime Volumes or parts of them. They may as well be used to define the spatial and temporal extent of property rights or national borders.
Examples:
• the spacetime volume defined by a polygon approximating the Danube river flood in Austria between 6th and 9th of August 2002
• the spacetime volume of the Orinoco river in 1529 defined in the map of Diego Ribeiro in 1529
• the spacetime volume representing the boundaries of the UK from 1900-1950</rdfs:comment>
<rdfs:subClassOf rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E92_Spacetime_Volume"/>
</rdfs:Class>
<rdfs:Class rdf:about="SP10_Declarative_Time-Span">
<rdfs:subClassOf rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E52_Time-Span"/>
<rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
>Scope note: This class comprises instances of SP9 Time Intervalls that represent the Time Span defined by a SP 14 Time Expression. Thus they derive their identity through an expression defining an extent in time. Even though SP10 Declarative Time Spans have an unlimited precision, measurement devices and the possible precision within the SP11 Temporal Reference System impose limitations to the determination of a SP10 Declarative Time Span. The accuracy of a SP10 Declarative Time Spans depends upon the documentation and measurement method.
SP10 Declarative Time Spans may be used to approximate actual (phenomenal) Time-Spans of temporal entities.
Examples:
• Extent in time defined by the expression “1961”
• Extent in time defined by the expression “From 12-17-1993 to 12-8-1996”
• Extent in time defined by the expression “14h30 – 16h22 4th July 1945”</rdfs:comment>
</rdfs:Class>
<rdfs:Class rdf:about="SP11_Temporal_Reference_System">
<rdfs:subClassOf rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E29_Design_or_Procedure"/>
<rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
>Scope note: This class compromises systems(S) that are used to describe positions and extents in a Reference Time. If relativistic effects are negligible in the wider spacetime area of interest and the speeds of associated things, then there is only one unique global reference time. The typical way to measure time is to count the cycles of a periodic process for which we have a hypothesis of constant frequency, such as oscillations of a crystal, molecular arrangement, rotation of earth around itself or around the sun. The origin for a Temporal Reference System is fixed on a reference event. As long as the number of cycles passed from that reference event until now are known, the temporal reference system exists (E) and expressions in this Reference System can be interpreted with respect to the Reference Time.
A temporal reference system represents time as a continuous linear interpolation over the infinit series of cycles extended from the reference event to he past and the future, regardless of the temporal position of the mathematical point zero of an instance of E61 Time Primitive, such for instance the gregorian calender begins with the event an arbitrary positiong the point zero as beeing the date of the „Birth of Christ“. The actual date of birth of christ is regarded to be unknown and therefor is not the reference event.
The identity of a Temporal Reference System is defined through the type of periodic process it is based on, the reference event and through the distance of the reference event to the position of the mathematical point zero (I).
A value in the Reference Time is a temporal position measured relative to a temporal reference system. ISO 8601 specifies the use of the Gregorian Calendar and 24 hour local or Coordinated Universal Time (UTC) for information interchange.
In ISO 19108 three common types of temporal reference systems are explicitly stated: calendars (used with clocks for greater resolution), temporal coordinate systems, and ordinal temporal reference systems.
Calendars and clocks are both based on interval scales. A calendar is a discrete temporal reference system that provides a basis for defining temporal position to a resolution of one day. A clock provides a basis for defining temporal position within a day. A clock must be used with a calendar in order to provide a complete description of a temporal position within a specific day. Every calendar provides a set of rules for composing a calendar date from a set of elements such as year, month, and day. In every calendar, years are numbered relative to the date of a reference event that defines a calendar era [ISO 19108].
Specifying temporal position in terms of calendar date and time of day complicates the computation of distances between points and the functional description of temporal operations. A temporal coordinate system may be used to support applications of this kind. [ISO 19108].
Ordinal temporal reference systems as specified in ISO 19108 are no instances of SP11 Temporal Reference Systems as they do not define cycles of a periodic process but define a system of time intervals based on reverence periods related to certain natural or cultural phenomena.
Examples:
• Gregorian Calendar
• Coordinated Universal Time (UTC)
• Julian date
• Greenwich time
• ISO 8601</rdfs:comment>
</rdfs:Class>
<rdfs:Class rdf:about="SP12_Spacetime_Volume_Expression">
<rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string">&lt;p style="margin-top: 0"&gt;
&lt;/p&gt;</rdfs:comment>
<rdfs:subClassOf rdf:resource="http://www.opengis.net/ont/geosparql#Geometry"/>
<rdfs:subClassOf rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E73_Information_Object"/>
</rdfs:Class>
<rdfs:Class rdf:about="SP13_Phenomenal_Time-Span">
<rdfs:subClassOf rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E52_Time-Span"/>
<rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
>Scope note: This class comprises instances of SP9 Time Intervalls whose extent (U) and position is defined by the temporal projection of the spatiotemporal extent that can be observed or measured. Thus they derive their identity through the extent in time of a real world phenomenon (I).
Examples:
• Duration of the phenomenal temporal extent of the Trafalgar battle
• The real duration of the Ming Dynasty
• The real extent of the lifetime of Ceasar starting with his birth and ending with his death</rdfs:comment>
</rdfs:Class>
<rdfs:Class rdf:about="SP14_Time_Expression">
<rdfs:subClassOf rdf:resource="http://www.opengis.net/ont/geosparql#Geometry"/>
<rdfs:subClassOf rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E73_Information_Object"/>
<rdfs:subClassOf rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E49_Time_Appellation"/>
<rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
>Scope note: This class comprises definitions of temporal extents by quantitative expressions(S). An instance of SP14 Time Expression defines a declarative temporal interval using a temporal reference system. The identity of a SP14 Time Expression is based on its script or symbolic form (I). Several SP14 Time Expressions can denote the same SP10 Declarative Time Interval.
Instances of SP14 Time Expression that exist in one SP11 Temporal Reference System can be transformed to time expressions in other SP11 Temporal Reference Systems if there is a known and valid transformation.
Examples:
• Temporal information in GML
&lt;gml:validTime&gt;&lt;gml:TimeInstant&gt;
&lt;gml:timePosition&gt;2005-11-28T13:00:00Z&lt;/gml:timePosition&gt;
&lt;/gml:TimeInstant&gt;&lt;/gml:validTime&gt;
• 1961
• From 12-17-1993 to 12-8-1996
• 14h30 – 16h22 4th July 1945
• 9.30 am 1.1.1999 to 2.00 pm 1.1.1999</rdfs:comment>
</rdfs:Class>
<rdfs:Class rdf:about="SP15_Geometry">
<rdfs:subClassOf rdf:resource="http://www.opengis.net/ont/geosparql#Geometry"/>
<rdfs:subClassOf rdf:resource="SP6_Declarative_Place"/>
<rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
>Scope note: This class comprises ....(to be elaborated further)
Equivalent to: http://www.opengis.net/ont/geosparql#Geometry (geosparql)</rdfs:comment>
</rdfs:Class>
<rdfs:Class rdf:about="http://www.opengis.net/ont/geosparql#gmlLiteral">
<rdfs:subClassOf rdf:resource="SP5_Geometric_Place_Expression"/>
</rdfs:Class>
<rdfs:Class rdf:about="http://www.opengis.net/ont/geosparql#wktLiteral">
<rdfs:subClassOf rdf:resource="SP5_Geometric_Place_Expression"/>
</rdfs:Class>
<rdf:Property rdf:about="asGML">
<rdfs:domain rdf:resource="http://www.opengis.net/ont/geosparql#Geometry"/>
<rdfs:range rdf:resource="http://www.opengis.net/ont/geosparql#gmlLiteral"/>
<rdfs:subClassOf rdf:resource="Q10_defines_place"/>
<rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
>Scope note: </rdfs:comment>
</rdf:Property>
<rdf:Property rdf:about="asWKT">
<rdfs:domain rdf:resource="http://www.opengis.net/ont/geosparql#Geometry"/>
<rdfs:range rdf:resource="http://www.opengis.net/ont/geosparql#wktLiteral"/>
<rdfs:subClassOf rdf:resource="Q10_defines_place"/>
<rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
>Scope note: </rdfs:comment>
</rdf:Property>
<rdf:Property rdf:about="Q1_occupied">
<rdfs:domain rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E4_Period"/>
<rdfs:range rdf:resource="SP1_Phenomenal_Spacetime_Volume"/>
<rdfs:subClassOf rdf:resource="http://www.opengis.net/ont/geosparql#Feature"/>
<rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
>Scope note: This property associates an instance of E4 Period with the 4 dimensional point sets (volumes) in spacetime that it occupied. This instance of SP1 Phenomenal Spacetime Volume includes the trajectories of the participating physical things during their participation in the instance of E4 Period, the open spaces via which they have interacted and the spaces by which they had the potential to interact during that period or event in the way defined by the type of the respective period or event, such as the air in a meeting room transferring the voices. It also comprises the areas controlled by some military power. Therefore instances of E4 Period have fuzzy boundaries in spacetime.</rdfs:comment>
</rdf:Property>
<rdf:Property rdf:about="Q1i_is_occupied_by">
<rdfs:domain rdf:resource="SP1_Phenomenal_Spacetime_Volume"/>
<rdfs:range rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E4_Period"/>
<rdfs:subClassOf rdf:resource="http://www.opengis.net/ont/geosparql#Feature"/>
</rdf:Property>
<rdf:Property rdf:about="Q2_occupied">
<rdfs:domain rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E18_Physical_Thing"/>
<rdfs:range rdf:resource="SP1_Phenomenal_Spacetime_Volume"/>
<rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
>Scope note: This property describes the 4 dimensional point sets (volumes) in spacetime that the trajectory of an instance of E18 Physical Thing occupies in spacetime in the course of its existence. We include in the occupied space the space filled by the matter of the physical thing and all inner spaces not accessible in regular function.</rdfs:comment>
</rdf:Property>
<rdf:Property rdf:about="Q2i_is_occupied_by">
<rdfs:domain rdf:resource="SP1_Phenomenal_Spacetime_Volume"/>
<rdfs:range rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E18_Physical_Thing"/>
</rdf:Property>
<rdf:Property rdf:about="Q3_has_temporal_projection">
<rdfs:domain rdf:resource="SP1_Phenomenal_Spacetime_Volume"/>
<rdfs:range rdf:resource="SP13_Phenomenal_Time-Span"/>
<rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
>Scope note: This property describes the temporal projection of an instance of a SP1 Phenomenal Spacetime Volume. The property P4 has time-span is a shortcut of the more fully developed path from E4 Period through Q1 occupied, SP1 Phenomenal Spacetime Volume Q3 has temporal projection to E52 Time Span.</rdfs:comment>
</rdf:Property>
<rdf:Property rdf:about="Q3i_is_temporal_projection">
<rdfs:domain rdf:resource="SP13_Phenomenal_Time-Span"/>
<rdfs:range rdf:resource="SP1_Phenomenal_Spacetime_Volume"/>
</rdf:Property>
<rdf:Property rdf:about="Q4_has_spatial_projection">
<rdfs:domain rdf:resource="SP1_Phenomenal_Spacetime_Volume"/>
<rdfs:range rdf:resource="SP2_Phenomenal_Place"/>
<rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
>Scope note: This property describes the spatial projection of an instance of a SP1 Phenomenal Spacetime Volume on an instance of SP2 Phenomenal Place. Even though the projection of a spacetime volume to one instance of SP3 Reference Space is unique, each reference space gives rise to another projection. The projections overlap at the time of the spacetime volume, the respective instances of SP2 Phenomenal Place may later drift apart, or earlier be yet apart.
The property P7 took place at is a shortcut of the more fully developed path from E4 Period through Q1 occupied, SP1 Phenomenal Spacetime Volume Q4 has spatial projection to SP2 Phenomenal Place.</rdfs:comment>
</rdf:Property>
<rdf:Property rdf:about="Q4i_is_spatial_projection">
<rdfs:domain rdf:resource="SP2_Phenomenal_Place"/>
<rdfs:range rdf:resource="SP1_Phenomenal_Spacetime_Volume"/>
<rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
>i of</rdfs:comment>
</rdf:Property>
<rdf:Property rdf:about="Q5_defined_in">
<rdfs:domain rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E53_Place"/>
<rdfs:range rdf:resource="SP3_Reference_Space"/>
<rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
>Scope note: This property associates an instance of E53 Place with the instance of SP3 Reference Space it is defined in.</rdfs:comment>
</rdf:Property>
<rdf:Property rdf:about="Q5i_defined_in">
<rdfs:domain rdf:resource="SP3_Reference_Space"/>
<rdfs:range rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E53_Place"/>
</rdf:Property>
<rdf:Property rdf:about="Q6_is_at_rest_in_relation_to">
<rdfs:domain rdf:resource="SP3_Reference_Space"/>
<rdfs:range rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E18_Physical_Thing"/>
<rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
>Scope note: This property associates an instance of SP3 Reference Space with the instance of E18 Physical Thing that is at rest in it. For all instances of E18 Physical Thing exist at least one reference space it is at rest with because of their relative stability of form. Larger constellations of matter may comprise many physical features that are at rest with them.</rdfs:comment>
</rdf:Property>
<rdf:Property rdf:about="Q6i_rests_in_relation_to">
<rdfs:range rdf:resource="SP3_Reference_Space"/>
<rdfs:domain rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E18_Physical_Thing"/>
</rdf:Property>
<rdf:Property rdf:about="Q6_is_at_rest_in_relation_to">
<rdfs:domain rdf:resource="SP3_Reference_Space"/>
<rdfs:range rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E18_Physical_Thing"/>
<rdfs:subClassOf rdf:resource="http://www.opengis.net/ont/geosparql#Feature"/>
</rdf:Property>
<rdf:Property rdf:about="Q6i_rests_in_relation_to">
<rdfs:domain rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E18_Physical_Thing"/>
<rdfs:range rdf:resource="SP3_Reference_Space"/>
<rdfs:subClassOf rdf:resource="http://www.opengis.net/ont/geosparql#Feature"/>
</rdf:Property>
<rdf:Property rdf:about="Q7_describes">
<rdfs:domain rdf:resource="SP4_Spatial_Coordinate_Reference_System"/>
<rdfs:range rdf:resource="SP3_Reference_Space"/>
<rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
>Scope note: This property associates an instance of SP4 Spatial Coordinate Reference System with the instance of SP3 Reference Space for which it can be used to describe locations.</rdfs:comment>
</rdf:Property>
<rdf:Property rdf:about="Q7i_is_described_by">
<rdfs:domain rdf:resource="SP3_Reference_Space"/>
<rdfs:range rdf:resource="SP4_Spatial_Coordinate_Reference_System"/>
</rdf:Property>
<rdf:Property rdf:about="Q8_is_fixed_on">
<rdfs:domain rdf:resource="SP4_Spatial_Coordinate_Reference_System"/>
<rdfs:range rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E26_Physical_Feature"/>
<rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
>Scope note: This property defines the physical reference features that ground a spatial coordinate reference system in the real world.
In surveying and geodesy this is part of the datum definition and is often a point identified by a physical feature on earth (sometimes monuments) where the earth approximation ellipsoid touches the earth and one axis of the ellipsoid runs through.</rdfs:comment>
</rdf:Property>
<rdf:Property rdf:about="Q8i_fixes">
<rdfs:domain rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E26_Physical_Feature"/>
<rdfs:range rdf:resource="SP4_Spatial_Coordinate_Reference_System"/>
</rdf:Property>
<rdf:Property rdf:about="Q9_is_expressed_in_terms_of">
<rdfs:domain rdf:resource="SP5_Geometric_Place_Expression"/>
<rdfs:range rdf:resource="SP4_Spatial_Coordinate_Reference_System"/>
<rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
>Scope note: This property defines the coordinate reference system in terms of which a geometric place expression is formulated.</rdfs:comment>
</rdf:Property>
<rdf:Property rdf:about="Q9i_terms_express">
<rdfs:domain rdf:resource="SP4_Spatial_Coordinate_Reference_System"/>
<rdfs:range rdf:resource="SP5_Geometric_Place_Expression"/>
</rdf:Property>
<rdf:Property rdf:about="Q10_defines_place">
<rdfs:domain rdf:resource="SP5_Geometric_Place_Expression"/>
<rdfs:range rdf:resource="SP6_Declarative_Place"/>
<rdfs:subPropertyOf rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P87i_identifies"/>
<rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
>Scope note: This property associates an instance of SP5 Geometric Place Expression with the instance of SP6 Declarative Place it defines. Syntactic variants or use of different scripts may result in multiple instances of SP5 Geometric Place Expression defining exactly the same place. Transformations between different reference systems in general result in new definitions of places approximating each other.</rdfs:comment>
</rdf:Property>
<rdf:Property rdf:about="Q10i_place_is_defined_by">
<rdfs:domain rdf:resource="SP6_Declarative_Place"/>
<rdfs:range rdf:resource="SP5_Geometric_Place_Expression"/>
</rdf:Property>
<rdf:Property rdf:about="Q11_approximates">
<rdfs:domain rdf:resource="SP6_Declarative_Place"/>
<rdfs:range rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E53_Place"/>
<rdfs:subPropertyOf rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P121_overlaps_with"/>
<rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
>Scope note: This property approximates a phenomenal place which is defined in the same reference space. The property does not state the quality or accuracy of the approximation, but an overlap in area is the minimal requirement.</rdfs:comment>
</rdf:Property>
<rdf:Property rdf:about="Q11i_is_approximated_by">
<rdfs:domain rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E53_Place"/>
<rdfs:range rdf:resource="SP6_Declarative_Place"/>
<rdfs:subPropertyOf rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P121_overlaps_with"/>
</rdf:Property>
<rdf:Property rdf:about="Q12_approximates">
<rdfs:domain rdf:resource="SP7_Declarative_Spacetime_Volume"/>
<rdfs:range rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E92_Spacetime_Volume"/>
<rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
>Scope note: This property approximates a SP8 Spacetime Volume. The property does not state the quality or accuracy of the approximation, but an overlap of the spacetime volume is the minimal requirement.</rdfs:comment>
</rdf:Property>
<rdf:Property rdf:about="Q12i_approximates">
<rdfs:domain rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E92_Spacetime_Volume"/>
<rdfs:range rdf:resource="SP7_Declarative_Spacetime_Volume"/>
</rdf:Property>
<rdf:Property rdf:about="Q13_approximates">
<rdfs:domain rdf:resource="SP10_Declarative_Time-Span"/>
<rdfs:range rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E52_Time-Span"/>
<rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
>Scope note: This property approximates a SP9 Time Intervall. The property does not state the quality or accuracy of the approximation, but an overlap in time is the minimal requirement.</rdfs:comment>
</rdf:Property>
<rdf:Property rdf:about="Q13i_approximates">
<rdfs:domain rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E52_Time-Span"/>
<rdfs:range rdf:resource="SP10_Declarative_Time-Span"/>
</rdf:Property>
<rdf:Property rdf:about="Q14_defines_time">
<rdfs:domain rdf:resource="SP14_Time_Expression"/>
<rdfs:range rdf:resource="SP10_Declarative_Time-Span"/>
<rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
>Scope note: This property associates an instance of SP14 Time Expression with the instance of SP10 Declarative Time Span it defines. Syntactic variants or use of different scripts may result in multiple instances of SP14 Time Expression defining exactly the same time span. Transformations between different temporal reference systems in general result in new definitions of time spans approximating each other.</rdfs:comment>
</rdf:Property>
<rdf:Property rdf:about="Q14i_defines_time">
<rdfs:domain rdf:resource="SP10_Declarative_Time-Span"/>
<rdfs:range rdf:resource="SP14_Time_Expression"/>
</rdf:Property>
<rdf:Property rdf:about="Q15_is_expressed_in_terms_of">
<rdfs:domain rdf:resource="SP14_Time_Expression"/>
<rdfs:range rdf:resource="SP11_Temporal_Reference_System"/>
<rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
>Scope note: This property defines the temporal reference system in terms of which an SP14 Time Expression is formulated.</rdfs:comment>
</rdf:Property>
<rdf:Property rdf:about="Q15i_is_expressed_in_terms_of">
<rdfs:domain rdf:resource="SP11_Temporal_Reference_System"/>
<rdfs:range rdf:resource="SP14_Time_Expression"/>
</rdf:Property>
<rdf:Property rdf:about="Q16_defines_spacetime_volume">
<rdfs:domain rdf:resource="SP12_Spacetime_Volume_Expression"/>
<rdfs:range rdf:resource="SP7_Declarative_Spacetime_Volume"/>
<rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
>Scope note: This property associates an instance of SP12 Spacetime Volume Expression with the instance of SP7 Declarative Spacetime Volume it defines. Syntactic variants or use of different scripts may result in multiple instances of SP12 Spacetime Volume Expressions defining exactly the same SP7 Declarative Spacetime Volume. Transformations between different temporal or spatial reference systems in general result in new definitions of Spacetime Volumes approximating each other.</rdfs:comment>
</rdf:Property>
<rdf:Property rdf:about="Q16i_defines_spacetime_volume">
<rdfs:domain rdf:resource="SP7_Declarative_Spacetime_Volume"/>
<rdfs:range rdf:resource="SP12_Spacetime_Volume_Expression"/>
</rdf:Property>
<rdf:Property rdf:about="Q17_is_expressed_in_terms_of">
<rdfs:domain rdf:resource="SP12_Spacetime_Volume_Expression"/>
<rdfs:range rdf:resource="SP11_Temporal_Reference_System"/>
<rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
>Scope note: This property defines the temporal reference system in terms of which a SP12 Spacetime Volume Expression is formulated.</rdfs:comment>
</rdf:Property>
<rdf:Property rdf:about="Q17i_is_expressed_in_terms_of">
<rdfs:domain rdf:resource="SP11_Temporal_Reference_System"/>
<rdfs:range rdf:resource="SP12_Spacetime_Volume_Expression"/>
</rdf:Property>
<rdf:Property rdf:about="Q18_is_expressed_in_terms_of">
<rdfs:domain rdf:resource="SP12_Spacetime_Volume_Expression"/>
<rdfs:range rdf:resource="SP4_Spatial_Coordinate_Reference_System"/>
<rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
>Scope note: This property defines the spatial coordinate reference system in terms of which a SP12 Spacetime Volume Expression is formulated.</rdfs:comment>
</rdf:Property>
<rdf:Property rdf:about="Q18i_is_expressed_in_terms_of">
<rdfs:domain rdf:resource="SP4_Spatial_Coordinate_Reference_System"/>
<rdfs:range rdf:resource="SP12_Spacetime_Volume_Expression"/>
</rdf:Property>
<rdf:Property rdf:about="Q19_has_reference_event">
<rdfs:domain rdf:resource="SP11_Temporal_Reference_System"/>
<rdfs:range rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E5_Event"/>
</rdf:Property>
<rdf:Property rdf:about="Q19i_has_reference_event">
<rdfs:domain rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E5_Event"/>
<rdfs:range rdf:resource="SP11_Temporal_Reference_System"/>
</rdf:Property>
</rdf:RDF>

189
ontologies/cidoc-crm-ontology-master/CRMinf_v0.7.rdfs.xml Normal file
View File

@@ -0,0 +1,189 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!--
CRMinf 0.7 Encoded in RDFS
RDFS created by FORTH <maria@ics.forth.gr> June 22, 2015
Encoding Rules:
1. The RDF spelling rules do not allow blanks. Hence we have replaced them by underscores.
The blank between the concept identifier and concept name is replaced by underscore too.
For instance "I1_Argumentation" or "J2_concluded_that".
2. RDF does not allow to instantiate properties beginning from a range value.
Therefore, each CRMinf property is represented as two RDFS properties.
For instance "J2_concluded_that (was_concluded_by)" is represented as:
"J2_concluded_that" for the domain to range direction and "J2i_was_concluded_by" for the range to domain direction.
3. The primitive value "I6 Belief Value" referred in
the Model for formal completeness is interpreted as rdf: literal.
4. RDF does not provide a way to declare equivalence between two classes. So the information that I5 Inference Making is
equivalent to S5 Inference Making is lost.
-->
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#"
xml:base="http://www.ics.forth.gr/isl/CRMinf/" xml:lang="en">
<rdfs:Class rdf:about="I1_Argumentation">
<rdfs:comment>
This class comprises the activity of making honest inferences or observations. An honest inference or observation is one in which the E39 Actor carrying out the I1 Argumentation justifies and believes that the I6 Belief Value associated with resulting I2 Belief about the I4 Proposition Set is the correct value at the time that the activity was undertaken and that any I3 Inference Logic or methodology was correctly applied.
Only one instance of E39 Actor may carry out an instance of I1 Argumentation, though the E39 Actor may, of course, be an instance of E74 Group.
</rdfs:comment>
</rdfs:Class>
<rdfs:Class rdf:about="http://www.ics.forth.gr/isl/CRMsci/S4_Observation">
<rdfs:subClassOf rdf:resource="I1_Argumentation"/>
</rdfs:Class>
<rdfs:Class rdf:about="I2_Belief">
<rdfs:comment>
This class comprises the notion that the associated I4 Proposition Set is held to have a particular I6 Belief Value by a particular E39 Actor. This can be understood as the period of time that an individual or group holds a particular set of propositions to be true, false or somewhere in between.</rdfs:comment>
<rdfs:subClassOf rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E2_Temporal_Entity"/>
</rdfs:Class>
<rdfs:Class rdf:about="I3_Inference_Logic">
<rdfs:comment>
This class comprises the rules used as inputs to I5 Inference Making.
In this context the term “logic” is used in the most general sense of the Greek term, and not in the mathematical sense only. Examples are the direct application of formal logic, mathematical theories and calculus, formal or informal default reasoning based on default values associated with categories, probabilistic reasoning based mathematical models and assumed or observed frequencies for certain categories, application of theoretical social models and comparisons with “cultural parallels”, etc. An instance of Inference Logic could also be a reference to the exact software release of a Bayesian reasoner, a rule such as “later layers are on top of earlier layers”, or even a term like “social intuition”, if this is scholarly acceptable. (after Doerr, Kritsotaki and Boutsika 2011). Indeed anything that is scientifically or academically acceptable as a method for drawing conclusions may be included for instance human pattern recognition.
A particular instance of I3 Inference Logic would be the algorithm implemented in a particular revision of a software package.
Instances of I3 Inference Logic not only comprise the method of reasoning, but also the set of categorical laws or axioms used in the argumentation. Often both are inextricably interwoven, for instance in a software implementation.
</rdfs:comment>
<rdfs:subClassOf rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E89_Propositional_Object"/>
</rdfs:Class>
<rdfs:Class rdf:about="I4_Proposition_Set">
<rdfs:comment>
This class comprises the sets of formal, binary propositions that an I2 Belief is held about. It could be implemented as a named graph, a spreadsheet or any other structured data-set. Regardless of the specific syntax employed, the effective propositions it contains should be made up of unambiguous identifiers, concepts of a formal ontology and constructs of logic.</rdfs:comment>
<rdfs:subClassOf rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E73_Information_Object"/>
</rdfs:Class>
<rdfs:Class rdf:about="I5_Inference_Making">
<rdfs:comment>
This class comprises the action of making honest propositions and statements about particular states of affairs in reality or in possible realities or categorical descriptions of reality by using inferences from other statements based on hypotheses and any form of formal or informal logic. It includes evaluations, calculations, and interpretations based on mathematical formulations and propositions.
It is characterized by the use of an existing I2 Belief as the premise that together with a set of I3 Inference Logic draws a further I2 Belief as a conclusion.
Documenting instances of I5 Inference Making primarily enables tracing the dependency of knowledge from conclusion to premise through subsequent inferences, possibly back to primary evidence, so that the range of influence of knowledge revision at any intermediate stage of complex inference chains on current convictions can be narrowed down by query. The explicit reference to the applied inference logic further allows scholars or scientists to assess if they can or would follow the documented argument. The class is not intended to promote the use of computationally decidable systems of logic as replacements of scholarly justifications of arguments, even though it allows for documenting the use of decidable logic, if that was deemed adequate for the problem at hand. Principles of scholarly justifications of arguments are also regarded as kinds of inference logic.
</rdfs:comment>
<rdfs:subClassOf rdf:resource="I1_Argumentation"/>
</rdfs:Class>
<rdfs:Class rdf:about="http://www.ics.forth.gr/isl/CRMsci/S6_Data_Evaluation">
<rdfs:subClassOf rdf:resource="I5_Inference_Making"/>
</rdfs:Class>
<rdfs:Class rdf:about="http://www.ics.forth.gr/isl/CRMsci/S7_Simulation_or_Prediction">
<rdfs:subClassOf rdf:resource="I5_Inference_Making"/>
</rdfs:Class>
<rdfs:Class rdf:about="http://www.ics.forth.gr/isl/CRMsci/S8_Categorical_Hypothesis_Building">
<rdfs:subClassOf rdf:resource="I5_Inference_Making"/>
</rdfs:Class>
<rdfs:Class rdf:about="I7_Belief_Adoption">
<rdfs:comment>
This class comprises the action of an E39 Actor adopting a particular instance of I2 Belief to create a new instance of I2 Belief that shares some of the same propositions in the original I4 Proposition Set and the associated I6 Belief Value.
The basis of I7 Belief Adoption is trust in the source of the instance of I2 Belief rather than the application of the rules in instances of I3 Inference Logic.
Typical examples are the citation of academic papers or the reuse of data sets.
Where an instance of I7 Belief Adoption is based on personal communication (pers.comm.) this should be represented by using P2 has type: “Pers.Comm.” directly from the instance of I7 Belief Adoption.
</rdfs:comment>
<rdfs:subClassOf rdf:resource="I1_Argumentation"/>
</rdfs:Class>
<rdf:Property rdf:about="J1_used_as_premise">
<rdfs:domain rdf:resource="I5_Inference_Making"/>
<rdfs:range rdf:resource="I2_Belief"/>
<rdfs:subPropertyOf rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P17_was_motivated_by"/>
<rdfs:comment>
This property associates an instance of I2 Belief with the instance of I5 Inference Making that used it as a premise.
</rdfs:comment>
</rdf:Property>
<rdf:Property rdf:about="J1i_was_premise_for">
<rdfs:domain rdf:resource="I2_Belief"/>
<rdfs:range rdf:resource="I5_Inference_Making"/>
<rdfs:subPropertyOf rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P17i_motivated"/>
</rdf:Property>
<rdf:Property rdf:about="J2_concluded_that">
<rdfs:domain rdf:resource="I1_Argumentation"/>
<rdfs:range rdf:resource="I2_Belief"/>
<rdfs:subPropertyOf rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P116_starts"/>
<rdfs:comment>
This property associates an instance of I2 Belief with the instance of I1 Argumentation that concluded it.
</rdfs:comment>
</rdf:Property>
<rdf:Property rdf:about="J2i_was_concluded_by">
<rdfs:domain rdf:resource="I2_Belief"/>
<rdfs:range rdf:resource="I1_Argumentation"/>
<rdfs:subPropertyOf rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P116i_is_started_by"/>
</rdf:Property>
<rdf:Property rdf:about="J3_applies">
<rdfs:domain rdf:resource="I5_Inference_Making"/>
<rdfs:range rdf:resource="I3_Inference_Logic"/>
<rdfs:subPropertyOf rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P16_used_specific_object"/>
<rdfs:comment>
This property associates an instance of I3 Inference Logic with the instance of I5 Inference Making that used it to draw its conclusion.
</rdfs:comment>
</rdf:Property>
<rdf:Property rdf:about="J3i_was_applied_by">
<rdfs:domain rdf:resource="I3_Inference_Logic"/>
<rdfs:range rdf:resource="I5_Inference_Making"/>
<rdfs:subPropertyOf rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P16i_was_used_for"/>
</rdf:Property>
<rdf:Property rdf:about="J4_that">
<rdfs:domain rdf:resource="I2_Belief"/>
<rdfs:range rdf:resource="I4_Proposition_Set"/>
<rdfs:comment>
This property associates an instance of I4 Proposition Set with the instance of I2 Belief that holds an opinion about it.
</rdfs:comment>
</rdf:Property>
<rdf:Property rdf:about="J4i_is_subject_of">
<rdfs:domain rdf:resource="I4_Proposition_Set"/>
<rdfs:range rdf:resource="I2_Belief"/>
</rdf:Property>
<rdf:Property rdf:about="J5_holds_to_be">
<rdfs:domain rdf:resource="I2_Belief"/>
<rdfs:range rdf:resource="http://www.w3.org/2000/01/rdf-schema#Literal"/>
<rdfs:subPropertyOf rdf:resource="O2_removed"/>
</rdf:Property>
<rdf:Property rdf:about="J6_adopted">
<rdfs:domain rdf:resource="I7_Belief_Adoption"/>
<rdfs:range rdf:resource="I2_Belief"/>
<rdfs:subPropertyOf rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P17_was_motivated_by"/>
<rdfs:comment>
This property associates an instance of I2 Belief with the instance of I7 Belief Adoption that used it as the source of the I6 Belief Value and propositions used in the resulting new I2 Belief.
</rdfs:comment>
</rdf:Property>
<rdf:Property rdf:about="J6i_adopted_by">
<rdfs:domain rdf:resource="I2_Belief"/>
<rdfs:range rdf:resource="I7_Belief_Adoption"/>
<rdfs:subPropertyOf rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P17i_motivated"/>
</rdf:Property>
<rdf:Property rdf:about="J7_is_based_on_evidence">
<rdfs:domain rdf:resource="I7_Belief_Adoption"/>
<rdfs:range rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E73_Information_Object"/>
<rdfs:subPropertyOf rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P16_used_specific_object"/>
<rdfs:comment>
This property associates an instance of I7 Belief Adoption with the instance of E73 Information Object that was the source of or evidence for the I4 Proposition Set that was adopted.
</rdfs:comment>
</rdf:Property>
<rdf:Property rdf:about="J7i_is_evidence_for">
<rdfs:domain rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E73_Information_Object"/>
<rdfs:range rdf:resource="I7_Belief_Adoption"/>
<rdfs:subPropertyOf rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P16i_was_used_for"/>
</rdf:Property>
</rdf:RDF>

500
ontologies/cidoc-crm-ontology-master/CRMsci_v1.2.3.rdfs.xml Normal file
View File

@@ -0,0 +1,500 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!--
CRMsci 1.2.3 Encoded in RDFS
RDFS updated by FORTH <maria@ics.forth.gr> April 14, 2016
RDFS updated by SednaSoft <info@sedna-soft.de> Thursday, April 02, 2015
Changes:
- fixed mistyped references to S19 Observable Entity [sic] in O12 has dimension (is dimension of)
RDFS updated by FORTH <maria@ics.forth.gr> Friday, May 8, 2015
Changes:
- S7_Simulation-Prediction changed to S7_Simulation_or_Prediction
- reversed the domain and range of O9i_property_type_was_observed_by
No other changes found to be relevant for RDFS since CRMsci 1.2
Encoding Rules:
1. The RDF spelling rules do not allow blanks. Hence we have replaced them by underscores.
The blank between the concept identifier and concept name is replaced by underscore too.
For instance "S1_Matter_Removal" or "O3_sampled_from".
2. RDF does not allow to instantiate properties beginning from a range value.
Therefore, each CRMdig property is represented as two RDFS properties.
For instance "O3_sampled_from (was_sample_by)" is represented as:
"O3_sampled_from" for the domain to range direction and "O3i_was_sample_by" for the range to domain direction.
-->
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#"
xml:base="http://www.ics.forth.gr/isl/CRMsci/" xml:lang="en">
<rdfs:Class rdf:about="S1_Matter_Removal">
<rdfs:comment>
This class comprises the activities that result in an instance of S10 Material Substantial being decreased by the removal of an amount of matter.
Typical scenarios include the removal of a component or piece of a physical object, removal of an archaeological or geological layer, taking a tissue sample from a body or a sample of fluid from a body of water. The removed matter may acquire a persistent identity of different nature beyond the act of its removal, such as becoming a physical object in the narrower sense. Such cases should be modeled by using multiple instantiation with adequate concepts of creating the respective items.
</rdfs:comment>
<rdfs:subClassOf rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E7_Activity"/>
</rdfs:Class>
<rdfs:Class rdf:about="http://www.cidoc-crm.org/cidoc-crm/E80_Part_Removal">
<rdfs:subClassOf rdf:resource="S1_Matter_Removal"/>
</rdfs:Class>
<rdfs:Class rdf:about="S2_Sample_Taking">
<rdfs:comment>
This class comprises the activity that results in taking an amount of matter as sample for further analysis from a material substantial such as a body of water, a geological formation or an archaeological object. The removed matter may acquire a persistent identity of different nature beyond the act of its removal, such as becoming a physical object in the narrower sense. The sample is typically removed from a physical feature which is used as a frame of reference, the place of sampling. In case of non-rigid Material Substantials, the source of sampling may regarded not to be modified by the activity of sample taking.
</rdfs:comment>
<rdfs:subClassOf rdf:resource="S1_Matter_Removal"/>
</rdfs:Class>
<rdfs:Class rdf:about="S3_Measurement_by_Sampling">
<rdfs:comment>
This class comprises activities of taking a sample and measuring or analyzing it as one managerial unit of activity, in which the sample may not be identified and preserved beyond the context of this activity. Instances of this class are constrained to describe the taking of exactly one sample, in general not further identified, and the dimensions observed by the respective measurement are implicitly understood to describe this particular sample as representative of the place on the instance of S10 Material Substantial from which the sample was taken. Therefore the class S3 Measurement by Sampling inherits the properties of S2 Sample Taking.O3 sampled from: S10 Material Substantial and O4 sampled at: E53 Place, and the properties of S21(E16) Measurement.P40 observed dimension: E54 Dimension, due to multiple inheritance, whereas it needs not instantiate the properties O5 removed: S13 Sample and O24 measured: S15 Observable Entity, if the sample is not documented beyond the context of the activity.
</rdfs:comment>
<rdfs:subClassOf rdf:resource="S2_Sample_Taking"/>
<rdfs:subClassOf rdf:resource="S21_Measurement"/>
</rdfs:Class>
<rdfs:Class rdf:about="S4_Observation">
<rdfs:comment>
This class comprises the activity of gaining scientific knowledge about particular states of physical reality gained by empirical evidence, experiments and by measurements. We define observation in the sense of natural sciences, as a kind of human activity: at some Place and within some Time-Span, certain Physical Things and their behavior and interactions are observed, either directly by human sensory impression, or enhanced with tools and measurement devices. The output of the internal processes of measurement devices that do not require additional human interaction are in general regarded as part of the observation and not as additional inference. Manual recordings may serve as additional evidence. Measurements and witnessing of events are special cases of observations. Observations result in a belief about certain propositions. In this model, the degree of confidence in the observed properties is regarded to be “true” per default, but could be described differently by adding a property P3 has note to an instance of S4 Observation, or by reification of the property O16 observed value. Primary data from measurement devices are regarded in this model to be results of observation and can be interpreted as propositions believed to be true within the (known) tolerances and degree of reliability of the device. Observations represent the transition between reality and propositions in the form of instances of a formal ontology, and can be subject to data evaluation from this point on.
</rdfs:comment>
<rdfs:subClassOf rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E13_Attribute_Assignment"/>
</rdfs:Class>
<rdfs:Class rdf:about="S5_Inference_Making">
<rdfs:comment>
This class comprises the action of concluding propositions on a respective reality from observational data by making evaluations based on mathematical inference rules and calculations using established hypotheses, such as the calculation of an earthquake epicenter. S6 Data Evaluation is not defined as S21/E16 Measurement; Secondary derivations of dimensions of an object from data measured by different processes are regarded as S6 Data Evaluation and not determining instances of Measurement in its own right. For instance, the volume of a statue concluded from a 3D model is an instance of S6 Data Evaluation and not of Measurement.
</rdfs:comment>
<rdfs:subClassOf rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E13_Attribute_Assignment"/>
</rdfs:Class>
<rdfs:Class rdf:about="S6_Data_Evaluation">
<rdfs:comment>
This class comprises the action of concluding propositions on a respective reality from observational data by making evaluations based on mathematical inference rules and calculations using established hypotheses, such as the calculation of an earthquake epicenter. S6 Data Evaluation is not defined as S21/E16 Measurement; Secondary derivations of dimensions of an object from data measured by different processes are regarded as S6 Data Evaluation and not determining instances of Measurement in its own right. For instance, the volume of a statue concluded from a 3D model is an instance of S6 Data Evaluation and not of Measurement.
</rdfs:comment>
<rdfs:subClassOf rdf:resource="S5_Inference_Making"/>
</rdfs:Class>
<rdfs:Class rdf:about="S7_Simulation_or_Prediction">
<rdfs:comment>
This class comprises activities of executing algorithms or software for simulating the behavior and the properties of a system of interacting components that form part of reality or not by using a mathematical model of the respective interactions. In particular it implies making predictions about the future behaviors of a system of interacting components of reality by starting simulation from an actually observed state, such as weather forecasts. Simulations may also be used to understand the effects of a theory, to compare theoretical predictions with reality, or to show differences with another theory.
</rdfs:comment>
<rdfs:subClassOf rdf:resource="S5_Inference_Making"/>
</rdfs:Class>
<rdfs:Class rdf:about="S8_Categorical_Hypothesis_Building">
<rdfs:comment>
This class comprises the action of making categorical hypotheses based on inference rules and theories; By categorical hypotheses we mean assumptions about the kinds of interactions and related kinds of structures of a domain that have the character of “laws” of nature or human behavior, be it necessary or probabilistic. Categorical hypotheses are developed by “induction” from finite numbers of observation and the absence of observations of particular kinds. As such, categorical hypotheses are always subject to falsification by new evidence. Instances of S8 Categorical Hypothesis Building include making and questioning categorical hypotheses.
</rdfs:comment>
<rdfs:subClassOf rdf:resource="S5_Inference_Making"/>
</rdfs:Class>
<rdfs:Class rdf:about="S9_Property_Type">
<rdfs:comment>
This class comprises types of properties. Typically, instances of S9 Property Type would be taken from an ontology or terminological system. In particular, instances of this class can be used to describe in a parametric way what kind of properties the values in scientific data sets are about. By virtue of such descriptions, numeric data can be interpreted as sets of propositions in terms of a formal ontology, such as “concentration of nitrate”, observed in the ground water from a certain borehole.
</rdfs:comment>
<rdfs:subClassOf rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E55_Type"/>
</rdfs:Class>
<rdfs:Class rdf:about="S10_Material_Substantial">
<rdfs:comment>
This class comprises constellations of matter with a relative stability of any form sufficient to associate them with a persistent identity, such as being confined to certain extent, having a relative stability of form or structure, or containing a fixed amount of matter. In particular, it comprises physical things in the narrower sense and fluid bodies. It is an abstraction of physical substance for solid and non-solid things of matter.
</rdfs:comment>
<rdfs:subClassOf rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E70_Thing"/>
</rdfs:Class>
<rdfs:Class rdf:about="http://www.cidoc-crm.org/cidoc-crm/E18_Physical_Thing">
<rdfs:subClassOf rdf:resource="S10_Material_Substantial"/>
</rdfs:Class>
<rdfs:Class rdf:about="S11_Amount_of_Matter">
<rdfs:comment>
This class comprises fixed amounts of matter specified as some air, some water, some soil, etc., defined by the total and integrity of their material content.
</rdfs:comment>
<rdfs:subClassOf rdf:resource="S10_Material_Substantial"/>
</rdfs:Class>
<rdfs:Class rdf:about="S12_Amount_of_Fluid">
<rdfs:comment>
This class comprises fixed amounts of fluid defined by the total of its material content, typically molecules. They frequently acquire identity in laboratory practice by the fact of being kept or handled together within some adequate containers.
</rdfs:comment>
<rdfs:subClassOf rdf:resource="S11_Amount_of_Matter"/>
<rdfs:subClassOf rdf:resource="S14_Fluid_Body"/>
</rdfs:Class>
<rdfs:Class rdf:about="S13_Sample">
<rdfs:comment>
This class comprises instances of S11 Amount of Matter taken from some instance of S10 Material Substantial with the intention to be representative for some material qualities of the instance of S10 Material Substantial or part of it was taken from for further analysis. We typically regard a sample as ceasing to exist when the respective representative qualities become corrupted, such as the purity of a water sample or the layering of a bore core.
</rdfs:comment>
<rdfs:subClassOf rdf:resource="S11_Amount_of_Matter"/>
</rdfs:Class>
<rdfs:Class rdf:about="S14_Fluid_Body">
<rdfs:comment>
This class comprises a mass of matter in fluid form environmentally constraint in some persistent form allowing for identifying it for the management or research of material phenomena, such as a part of the sea, a river, the atmosphere or the milk in a bottle. Fluids are generally defined by the continuity criterion which is characteristic of their substance: their amorphous matter is continuous and tends to flow. Therefore, contiguous amounts of matter within a fluid body may stay contiguous or at least be locally spatially confined for a sufficiently long time in order to be temporarily identified and traced. This is a much weaker concept of stability of form than the one we would apply to what one would call a physical object. In general, an instance of Fluid Body may gain or lose matter over time through so-called sources or sinks in its surface, in contrast to physical things, which may lose or gain matter by exchange of pieces such as spare parts or corrosion.
</rdfs:comment>
<rdfs:subClassOf rdf:resource="S10_Material_Substantial"/>
</rdfs:Class>
<rdfs:Class rdf:about="S15_Observable_Entity">
<rdfs:comment>
This class comprises instances of E2 Temporal Entity or E77 Persistent Item, i.e. items or phenomena that can be observed, either directly by human sensory impression, or enhanced with tools and measurement devices, such as physical things, their behavior, states and interactions or events.
Conceptual objects can be present in events by their carriers such as books, digital media, or even human memory. By virtue of this presence, properties of conceptual objects, such as number of words can be observed on their carriers. If the respective properties between carriers differ, either they carry different instances of conceptual objects or the difference can be attributed to accidental deficiencies in one of the carriers. In that sense even immaterial objects are observable. By this model we give credit to the fact that frequently, the actually observed carriers of conceptual objects are not explicitly identified in documentation, i.e., the actual carrier is assumed having existed but is unknown as an individual.
</rdfs:comment>
<rdfs:subClassOf rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E1_CRM_Entity"/>
</rdfs:Class>
<rdfs:Class rdf:about="http://www.cidoc-crm.org/cidoc-crm/E2_Temporal_Entity">
<rdfs:subClassOf rdf:resource="S15_Observable_Entity"/>
</rdfs:Class>
<rdfs:Class rdf:about="http://www.cidoc-crm.org/cidoc-crm/E77_Persistent_Item">
<rdfs:subClassOf rdf:resource="S15_Observable_Entity"/>
</rdfs:Class>
<rdfs:Class rdf:about="S16_State">
<rdfs:comment>
This class comprises the persistence of a particular value range of the properties of a particular thing or things over a time-span.
</rdfs:comment>
<rdfs:subClassOf rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E2_Temporal_Entity"/>
</rdfs:Class>
<rdfs:Class rdf:about="http://www.cidoc-crm.org/cidoc-crm/E3_Condition_State">
<rdfs:subClassOf rdf:resource="S16_State"/>
</rdfs:Class>
<rdfs:Class rdf:about="S17_Physical_Genesis">
<rdfs:comment>
This class comprises events or processes that result in (generate) physical things, man-made or natural, coming into being in the form by which they are later identified. The creation of a new physical item, at the same time, can be a result of an alteration (modification) – it can become a new thing due to an alteration activity.
</rdfs:comment>
<rdfs:subClassOf rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E63_Beginning_of_Existence"/>
<rdfs:subClassOf rdf:resource="S18_Alteration"/>
</rdfs:Class>
<rdfs:Class rdf:about="http://www.cidoc-crm.org/cidoc-crm/E12_Production">
<rdfs:subClassOf rdf:resource="S17_Physical_Genesis"/>
</rdfs:Class>
<rdfs:Class rdf:about="S18_Alteration">
<rdfs:comment>
This class comprises natural events or man-made processes that create, alter or change physical things, by affecting permanently their form or consistency without changing their identity. Examples include alterations on depositional features-layers by natural factors or disturbance by roots or insects, organic alterations, petrification, etc.
</rdfs:comment>
<rdfs:subClassOf rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E5_Event"/>
</rdfs:Class>
<rdfs:Class rdf:about="http://www.cidoc-crm.org/cidoc-crm/E11_Modification">
<rdfs:subClassOf rdf:resource="S18_Alteration"/>
</rdfs:Class>
<rdfs:Class rdf:about="S19_Encounter_Event">
<rdfs:comment>
This class comprises activities of S4 Observation (substance) where an E39 Actor encounters an instance of E18 Physical Thing of a kind relevant for the mission of the observation or regarded as potentially relevant for some community (identity). This observation produces knowledge about the existence of the respective thing at a particular place in or on surrounding matter. This knowledge may be new to the group of people the actor belongs to. In that case we would talk about a discovery. The observer may recognize or assign an individual identity of the thing encountered or regard only the type as noteworthy in the associated documentation or report.
In archaeology there is a particular interest if an object is found “in situ”, i.e. if its embedding in the surrounding matter supports the assumption that the object was not moved since the archaeologically relevant deposition event. The surrounding matter with the relative position of the object in it as well as the absolute position and time of the observation may be recorded in order to enable inferences about the history of the E18 Physical Thing.
In Biology, additional parameters may be recorded like the kind of ecosystem, if the biological individual survives the observation, what detection or catching devices have been used or if the encounter event supported the detection of a new biological kind (“taxon”).
</rdfs:comment>
<rdfs:subClassOf rdf:resource="S4_Observation"/>
</rdfs:Class>
<rdfs:Class rdf:about="S20_Physical_Feature">
<rdfs:comment>
This class comprises identifiable features that are physically attached in an integral way to particular physical objects. An instance of S20 Physical Feature also represents the place it occupies with respect to the surrounding matter. More precisely, it is the maximal real volume in space that an instance of S20 Physical Feature is occupying during its lifetime with respect to the default reference space relative to which the feature is at rest. In cases of features on or in the surface of earth, the default reference is typically fixed to the closer environment of the tectonic plate or sea floor. In cases of features on mobile objects, the reference space is typically fixed to the geometry of the bearing object.
Instances of E26 Physical Feature share many of the attributes of instances of E19 Physical Object. They may have a one-, two- or three-dimensional geometric extent, but there are no natural borders that separate them completely in an objective way from the carrier objects. For example, a doorway is a feature but the door itself, being attached by hinges, is not.
Instances of E26 Physical Feature can be features in a narrower sense, such as scratches, holes, reliefs, surface colors, reflection zones in an opal crystal or a density change in a piece of wood. In the wider sense, they are portions of particular objects with partially imaginary borders, such as the core of the Earth, an area of property on the surface of the Earth, a landscape or the head of a contiguous marble statue. They can be measured and dated, and it is sometimes possible to state who or what is or was responsible for them. They cannot be separated from the carrier object, but a segment of the carrier object may be identified (or sometimes removed) carrying the complete feature.
This definition coincides with the definition of "fiat objects" (Smith and Varzi, 2000, pp.401-420), with the exception of aggregates of “bona fide objects”.
</rdfs:comment>
<rdfs:subClassOf rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E18_Physical_Thing"/>
<rdfs:subClassOf rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E53_Place"/>
</rdfs:Class>
<rdfs:Class rdf:about="http://www.cidoc-crm.org/cidoc-crm/E27_Site">
<rdfs:subClassOf rdf:resource="S20_Physical_Feature"/>
</rdfs:Class>
<rdfs:Class rdf:about="http://www.cidoc-crm.org/cidoc-crm/E25_Man-Made_Feature">
<rdfs:subClassOf rdf:resource="S20_Physical_Feature"/>
</rdfs:Class>
<rdfs:Class rdf:about="S21_Measurement">
<rdfs:comment>
This class comprises actions measuring instances of E2 Temporal Entity or E77 Persistent Items, properties of physical things, or phenomena, states and interactions or events, that can be determined by a systematic procedure. Primary data from measurement devices are regarded to be results of an observation process.
</rdfs:comment>
<rdfs:subClassOf rdf:resource="S4_Observation"/>
<rdfs:subClassOf rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E16_Measurement"/>
</rdfs:Class>
<rdfs:Class rdf:about="S22_Segment_of_Matter">
<rdfs:comment>
This class comprises physical material in a relative stability of form (substance) within a specific spacetime volume (unity, extend). The spatial extend of a S22 Segment of Matter is defined by humans usually because the constellation is subject to a specific interest for and investigations of the geometric arrangement of physical features or parts of them on or within the specified S22 Segment of Matter. It comes into existence as being an object of discourse through S4 Observation or declaration and is restricted to the time span starting after the last change through an S18 Alteration before the S4 Observation or declaration and ending with the next S18 Alteration Event (identity). A S22 Segment of Matter exists as long as there is no modification of the geometric arrangement of its particles. Therefore the temporal boundaries of the defining Spacetime Volume are given by two S18 Alteration events.
The history of a S22 Segment of Matter started with the first S17 Physical Genesis event that deposited still existing matter within the defined spatial extend. The collection of all S18 Alteration events represent its history. Some of the events will not leave any physical material within the S22 Segment of Matter.
(to be elaborated further)
</rdfs:comment>
<rdfs:subClassOf rdf:resource="S20_Physical_Feature"/>
</rdfs:Class>
<rdf:Property rdf:about="O1_diminished">
<rdfs:domain rdf:resource="S1_Matter_Removal"/>
<rdfs:range rdf:resource="S10_Material_Substantial"/>
</rdf:Property>
<rdf:Property rdf:about="O1i_was_diminished_by">
<rdfs:domain rdf:resource="S10_Material_Substantial"/>
<rdfs:range rdf:resource="S1_Matter_Removal"/>
</rdf:Property>
<rdf:Property rdf:about="O2_removed">
<rdfs:domain rdf:resource="S1_Matter_Removal"/>
<rdfs:range rdf:resource="S11_Amount_of_Matter"/>
</rdf:Property>
<rdf:Property rdf:about="O2i_was_removed_by">
<rdfs:domain rdf:resource="S11_Amount_of_Matter"/>
<rdfs:range rdf:resource="S1_Matter_Removal"/>
</rdf:Property>
<rdf:Property rdf:about="O3_sampled_from">
<rdfs:domain rdf:resource="S2_Sample_Taking"/>
<rdfs:range rdf:resource="S10_Material_Substantial"/>
</rdf:Property>
<rdf:Property rdf:about="O3i_was_sample_by">
<rdfs:domain rdf:resource="S10_Material_Substantial"/>
<rdfs:range rdf:resource="S2_Sample_Taking"/>
</rdf:Property>
<rdf:Property rdf:about="O4_sampled_at">
<rdfs:domain rdf:resource="S2_Sample_Taking"/>
<rdfs:range rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E53_Place"/>
</rdf:Property>
<rdf:Property rdf:about="O4i_was_sampling_location_of">
<rdfs:domain rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E53_Place"/>
<rdfs:range rdf:resource="S2_Sample_Taking"/>
</rdf:Property>
<rdf:Property rdf:about="O5_removed">
<rdfs:domain rdf:resource="S2_Sample_Taking"/>
<rdfs:range rdf:resource="S13_Sample"/>
<rdfs:subPropertyOf rdf:resource="O2_removed"/>
</rdf:Property>
<rdf:Property rdf:about="O5i_was_removed_by">
<rdfs:domain rdf:resource="S13_Sample"/>
<rdfs:range rdf:resource="S2_Sample_Taking"/>
<rdfs:subPropertyOf rdf:resource="O2i_was_removed_by"/>
</rdf:Property>
<rdf:Property rdf:about="O6_forms_former_or_current_part_of">
<rdfs:domain rdf:resource="S12_Amount_of_Fluid"/>
<rdfs:range rdf:resource="S14_Fluid_Body"/>
</rdf:Property>
<rdf:Property rdf:about="O6i_has_former_or_current_part">
<rdfs:domain rdf:resource="S14_Fluid_Body"/>
<rdfs:range rdf:resource="S12_Amount_of_Fluid"/>
</rdf:Property>
<rdf:Property rdf:about="O7_contains_or_confines">
<rdfs:domain rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E53_Place"/>
<rdfs:range rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E53_Place"/>
</rdf:Property>
<rdf:Property rdf:about="O7i_is_contained_or_confined">
<rdfs:domain rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E53_Place"/>
<rdfs:range rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E53_Place"/>
</rdf:Property>
<rdf:Property rdf:about="O8_observed">
<rdfs:domain rdf:resource="S4_Observation"/>
<rdfs:range rdf:resource="S15_Observable_Entity"/>
<rdfs:subPropertyOf rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P140_assigned_attribute_to"/>
</rdf:Property>
<rdf:Property rdf:about="O8i_was_observed_by">
<rdfs:domain rdf:resource="S15_Observable_Entity"/>
<rdfs:range rdf:resource="S4_Observation"/>
<rdfs:subPropertyOf rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P140i_was_attributed_by"/>
</rdf:Property>
<rdf:Property rdf:about="O9_observed_property_type">
<rdfs:domain rdf:resource="S4_Observation"/>
<rdfs:range rdf:resource="S9_Property_Type"/>
</rdf:Property>
<rdf:Property rdf:about="O9i_property_type_was_observed_by">
<rdfs:domain rdf:resource="S9_Property_Type"/>
<rdfs:range rdf:resource="S4_Observation"/>
</rdf:Property>
<rdf:Property rdf:about="O10_assigned_dimension">
<rdfs:domain rdf:resource="S6_Data_Evaluation"/>
<rdfs:range rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E54_Dimension"/>
</rdf:Property>
<rdf:Property rdf:about="O10i_dimension_was_assigned_by">
<rdfs:domain rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E54_Dimension"/>
<rdfs:range rdf:resource="S6_Data_Evaluation"/>
</rdf:Property>
<rdf:Property rdf:about="O11_described">
<rdfs:domain rdf:resource="S6_Data_Evaluation"/>
<rdfs:range rdf:resource="S15_Observable_Entity"/>
</rdf:Property>
<rdf:Property rdf:about="O11i_was_described_by">
<rdfs:domain rdf:resource="S15_Observable_Entity"/>
<rdfs:range rdf:resource="S6_Data_Evaluation"/>
</rdf:Property>
<rdf:Property rdf:about="O12_has_dimension">
<rdfs:domain rdf:resource="S15_Observable_Entity"/>
<rdfs:range rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E54_Dimension"/>
</rdf:Property>
<rdf:Property rdf:about="O12i_is_dimension_of">
<rdfs:domain rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E54_Dimension"/>
<rdfs:range rdf:resource="S15_Observable_Entity"/>
</rdf:Property>
<rdf:Property rdf:about="O13_triggers">
<rdfs:domain rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E5_Event"/>
<rdfs:range rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E5_Event"/>
</rdf:Property>
<rdf:Property rdf:about="O13i_is_triggered_by">
<rdfs:domain rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E5_Event"/>
<rdfs:range rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E5_Event"/>
</rdf:Property>
<rdf:Property rdf:about="O14_initializes">
<rdfs:domain rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E5_Event"/>
<rdfs:range rdf:resource="S16_State"/>
</rdf:Property>
<rdf:Property rdf:about="O14i_is_initialized_by">
<rdfs:domain rdf:resource="S16_State"/>
<rdfs:range rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E5_Event"/>
</rdf:Property>
<rdf:Property rdf:about="O15_occupied">
<rdfs:domain rdf:resource="S10_Material_Substantial"/>
<rdfs:range rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E53_Place"/>
</rdf:Property>
<rdf:Property rdf:about="O15i_was_occupied_by">
<rdfs:domain rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E53_Place"/>
<rdfs:range rdf:resource="S10_Material_Substantial"/>
</rdf:Property>
<rdf:Property rdf:about="O16_observed_value">
<rdfs:domain rdf:resource="S4_Observation"/>
<rdfs:range rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E1_CRM_Entity"/>
<rdfs:subPropertyOf rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P141_assigned"/>
</rdf:Property>
<rdf:Property rdf:about="O16i_value_was_observed_by">
<rdfs:domain rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E1_CRM_Entity"/>
<rdfs:range rdf:resource="S4_Observation"/>
<rdfs:subPropertyOf rdf:resource="http://www.cidoc-crm.org/cidoc-crm/P141i_was_assigned_by"/>
</rdf:Property>
<rdf:Property rdf:about="O17_generated">
<rdfs:domain rdf:resource="S17_Physical_Genesis"/>
<rdfs:range rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E18_Physical_Thing"/>
</rdf:Property>
<rdf:Property rdf:about="O17i_was_generated_by">
<rdfs:domain rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E18_Physical_Thing"/>
<rdfs:range rdf:resource="S17_Physical_Genesis"/>
</rdf:Property>
<rdf:Property rdf:about="http://www.cidoc-crm.org/cidoc-crm/P108_has_produced">
<rdfs:subPropertyOf rdf:resource="O17_generated"/>
</rdf:Property>
<rdf:Property rdf:about="http://www.cidoc-crm.org/cidoc-crm/P108i_was_produced_by">
<rdfs:subPropertyOf rdf:resource="O17i_was_generated_by"/>
</rdf:Property>
<rdf:Property rdf:about="O18_altered">
<rdfs:domain rdf:resource="S18_Alteration"/>
<rdfs:range rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E18_Physical_Thing"/>
</rdf:Property>
<rdf:Property rdf:about="O18i_was_altered_by">
<rdfs:domain rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E18_Physical_Thing"/>
<rdfs:range rdf:resource="S18_Alteration"/>
</rdf:Property>
<rdf:Property rdf:about="http://www.cidoc-crm.org/cidoc-crm/P31_has_modified">
<rdfs:subPropertyOf rdf:resource="O18_altered"/>
</rdf:Property>
<rdf:Property rdf:about="http://www.cidoc-crm.org/cidoc-crm/P31i_was_modified_by">
<rdfs:subPropertyOf rdf:resource="O18i_was_altered_by"/>
</rdf:Property>
<rdf:Property rdf:about="O19_has_found_object">
<rdfs:domain rdf:resource="S19_Encounter_Event"/>
<rdfs:range rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E18_Physical_Thing"/>
</rdf:Property>
<rdf:Property rdf:about="O19i_was_object_found_by">
<rdfs:domain rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E18_Physical_Thing"/>
<rdfs:range rdf:resource="S19_Encounter_Event"/>
</rdf:Property>
<rdf:Property rdf:about="O20_sampled_from_type_of_part">
<rdfs:domain rdf:resource="S2_Sample_Taking"/>
<rdfs:range rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E55_Type"/>
</rdf:Property>
<rdf:Property rdf:about="O20i_type_of_part_was_sampled_by">
<rdfs:domain rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E55_Type"/>
<rdfs:range rdf:resource="S2_Sample_Taking"/>
</rdf:Property>
<rdf:Property rdf:about="O21_has_found_at">
<rdfs:domain rdf:resource="S19_Encounter_Event"/>
<rdfs:range rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E53_Place"/>
</rdf:Property>
<rdf:Property rdf:about="O21i_witnessed">
<rdfs:domain rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E53_Place"/>
<rdfs:range rdf:resource="S19_Encounter_Event"/>
</rdf:Property>
<rdf:Property rdf:about="O22_partly_or_completely_contains">
<rdfs:domain rdf:resource="S22_Segment_of_Matter"/>
<rdfs:range rdf:resource="S20_Physical_Feature"/>
</rdf:Property>
<rdf:Property rdf:about="O22i_is_part_of">
<rdfs:domain rdf:resource="S20_Physical_Feature"/>
<rdfs:range rdf:resource="S22_Segment_of_Matter"/>
</rdf:Property>
<rdf:Property rdf:about="O23_is_defined_by">
<rdfs:domain rdf:resource="S22_Segment_of_Matter"/>
<rdfs:range rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E92_Spacetime_Volume"/>
</rdf:Property>
<rdf:Property rdf:about="O23i_defines">
<rdfs:domain rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E92_Spacetime_Volume"/>
<rdfs:range rdf:resource="S22_Segment_of_Matter"/>
</rdf:Property>
<rdf:Property rdf:about="O24_measured">
<rdfs:domain rdf:resource="S21_Measurement"/>
<rdfs:range rdf:resource="S15_Observable_Entity"/>
</rdf:Property>
<rdf:Property rdf:about="O24i_was_measured_by">
<rdfs:domain rdf:resource="S15_Observable_Entity"/>
<rdfs:range rdf:resource="S21_Measurement"/>
</rdf:Property>
</rdf:RDF>

68
ontologies/cidoc-crm-ontology-master/arches_crm_enhancements.xml Normal file
View File

@@ -0,0 +1,68 @@
<?xml version="1.0" encoding="UTF-8"?>
<!--
CIDOC CRM v6.2 (draft) encoded in RDFS
ADDITIONS TO THE CIDOC CRM v6.2 SPEC FOR ARCHES:
Added E59, E60, E61, E62, and E94 classes for primitives.
Add E94_Space class.
Add BM.PX_is_related_to property.
Added missing P168i_defines_place property
-->
<rdf:RDF xml:lang="en" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#" xml:base="http://www.cidoc-crm.org/cidoc-crm/">
<rdfs:Class rdf:about="E59_Primitive_Value">
<rdfs:subClassOf rdf:resource="http://www.w3.org/2000/01/rdf-schema#Literal"/>
<rdfs:label xml:lang="en-US">Primitive Value</rdfs:label>
<rdfs:comment>This class comprises values of primitive data types of programming languages or database management systems and data types composed of such values used as documentation elements, as well as their mathematical abstractions.</rdfs:comment>
</rdfs:Class>
<rdfs:Class rdf:about="E60_Number">
<rdfs:label xml:lang="en-US">Number</rdfs:label>
<rdfs:comment>This class comprises any encoding of computable (algebraic) values such as integers, real numbers, complex numbers, vectors, tensors etc., including intervals of these values to express limited precision</rdfs:comment>
<rdfs:subClassOf rdf:resource="E59_Primitive_Value"/>
</rdfs:Class>
<rdfs:Class rdf:about="E61_Time_Primitive">
<rdfs:label xml:lang="en">Time Primitive</rdfs:label>
<rdfs:comment>This class comprises instances of E59 Primitive Value for time that should be implemented with appropriate validation, precision and interval logic to express date ranges relevant to cultural documentation.</rdfs:comment>
<rdfs:subClassOf rdf:resource="E59_Primitive_Value"/>
<rdfs:subClassOf rdf:resource="http://www.w3.org/2001/XMLSchema#dateTime"/>
</rdfs:Class>
<rdfs:Class rdf:about="E62_String">
<rdfs:label xml:lang="en">String</rdfs:label>
<rdfs:comment>This class comprises the instances of E59 Primitive Values used for documentation such as free text strings, bitmaps, vector graphics, etc.</rdfs:comment>
<rdfs:subClassOf rdf:resource="E59_Primitive_Value"/>
</rdfs:Class>
<rdfs:Class rdf:about="E94_Space_Primitive">
<rdfs:label xml:lang="en">Space</rdfs:label>
<rdfs:comment>This class comprises instances of E59 Primitive Value for space that should be implemented with appropriate validation, precision and references to spatial coordinate systems to express geometries on or relative to earth, or any other stable constellations of matter, relevant to cultural and scientific documentation.
An E94 Space Primitive defines an E53 Place in the sense of a declarative place as elaborated in CRMgeo (Doerr and Hiebel 2013), which means that the identity of the place is derived from its geometric definition. This declarative place allows for the application of all place properties to relate phenomenal places to their approximations expressed with geometries.
Instances of E94 Space Primitive provide the ability to link CRM encoded data to the kinds of geometries used in maps or Geoinformation systems. They may be used for visualisation of the instances of E53 Place they define, in their geographic context and for computing topological relations between places based on these geometries.
E94 Space Primitive is not further elaborated upon within this model. Statement of compatibility with OPENGIS</rdfs:comment>
<rdfs:subClassOf rdf:resource="E59_Primitive_Value"/>
</rdfs:Class>
<!-- <rdfs:Class rdf:about="E94_Space">
<rdfs:label xml:lang="en">Space</rdfs:label>
<rdfs:comment>This class comprises instances of E92 Spacetime Volume that result from intersection of instances of E92 Spacetime Volume with an instance of E52 Time-Span. The identity of an instance of this class is determined by the identities of the constituing spacetime volume and the time-span.</rdfs:comment>
<rdfs:subClassOf rdf:resource="E92_Spacetime_Volume"/>
</rdfs:Class> -->
<rdf:Property rdf:about="BM.PX_is_related_to">
<rdfs:label xml:lang="en">is related to</rdfs:label>
<rdfs:comment>Relates E18 to E1</rdfs:comment>
<rdfs:domain rdf:resource="E18_Physical_Thing"/>
<rdfs:range rdf:resource="E1_CRM_Entity"/>
</rdf:Property>
<rdf:Property rdf:about="P168i_defines_place">
<rdfs:label xml:lang="en">defines place</rdfs:label>
<rdfs:domain rdf:resource="http://www.w3.org/2000/01/rdf-schema#Literal"/>
<rdfs:range rdf:resource="E53_Place"/>
</rdf:Property>
</rdf:RDF>

5349
ontologies/cidoc-crm-ontology-master/cidoc_crm_v6.2.xml Normal file
View File

File diff suppressed because it is too large Load Diff

14
ontologies/cidoc-crm-ontology-master/ontology_config.json Normal file
View File

@@ -0,0 +1,14 @@
{
"base": "cidoc_crm_v6.2.xml",
"base_name": "CIDOC CRM v6.2",
"extensions": [
"CRMsci_v1.2.3.rdfs.xml",
"CRMarchaeo_v1.4.rdfs.xml",
"CRMgeo_v1.2.rdfs.xml",
"CRMdig_v3.2.1.rdfs.xml",
"CRMinf_v0.7.rdfs.xml",
"arches_crm_enhancements.xml"
],
"base_version": "6.2",
"base_id": "e6e8db47-2ccf-11e6-927e-b8f6b115d7dd"
}