Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge branch 'gh-pages' of github.com:w3c/sdw into gh-pages
- Loading branch information
Showing
8 changed files
with
80 additions
and
54 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Binary file not shown.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,75 +1,75 @@ | ||
# baseURI: http://www.w3.org/ns/sosa/examples | ||
# imports: http://www.w3.org/ns/sosa | ||
|
||
@prefix examples: <http://www.w3.org/ns/sosa/examples#> . | ||
@prefix ex: <http://www.w3.org/ns/sosa/examples#> . | ||
@prefix owl: <http://www.w3.org/2002/07/owl#> . | ||
@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> . | ||
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> . | ||
@prefix sosa-core: <http://www.w3.org/ns/sosa#> . | ||
@prefix sosa: <http://www.w3.org/ns/sosa#> . | ||
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> . | ||
|
||
<http://www.w3.org/ns/sosa/examples> | ||
rdf:type owl:Ontology ; | ||
owl:imports <http://www.w3.org/ns/sosa> ; | ||
. | ||
<http://www.w3.org/ns/sosa/examples#4830EH_UCSB> | ||
rdf:type sosa-core:Sample ; | ||
rdf:type sosa:Sample ; | ||
rdfs:comment "Instead of measuring temperature at every single office, we select room 4830 Ellison Hall, UCSB as a sample and thereby assume that the temperature observed there is a good proxy for the temperatures in other offices."^^xsd:string ; | ||
rdfs:label "4830 Ellison Hall"^^xsd:string ; | ||
sosa-core:isSampleOf examples:UCSB ; | ||
sosa:isSampleOf ex:UCSB ; | ||
. | ||
examples:RoomTemperature | ||
rdf:type sosa-core:Procedure ; | ||
rdfs:comment "How is this linked to platform & sensor?--> It s not explicitly linked (see also the comment for examples:TempObservation1) One could add a back-pointing relation to the observation here but in reality one would not do so as this would crate millions of triples as part of each procedure, thereby cluttering a procedure repository. This is/can be handled via UNION queries in SPARQL pr simply an inverse property (path) in your query."^^xsd:string ; | ||
ex:RoomTemperature | ||
rdf:type sosa:Procedure ; | ||
rdfs:comment "How is this linked to platform & sensor?--> It s not explicitly linked (see also the comment for ex:TempObservation1) One could add a back-pointing relation to the observation here but in reality one would not do so as this would crate millions of triples as part of each procedure, thereby cluttering a procedure repository. This is/can be handled via UNION queries in SPARQL pr simply an inverse property (path) in your query."^^xsd:string ; | ||
rdfs:comment "This is a procedure for measuring room temperatures. To ensure a meaningful interpretation of results and interoperability, all room temperature observations need to follow the same procedure. (1) The sensor should be put at least 1m above ground. (2) The sensor should be shielded from direct sun light and circulating air, e.g., via an open window. Other heat sources such as computers should be avoided as well. (3) The sensor should not be moved during observations. (4) Room temperature observations are only comparable if they were taken during comparable outside conditions and with closed windows and doors. (5)...."^^xsd:string ; | ||
. | ||
examples:SamsungGalaxyS4_23 | ||
rdf:type sosa-core:Platform ; | ||
ex:SamsungGalaxyS4_23 | ||
rdf:type sosa:Platform ; | ||
rdfs:comment "A Samsung Galaxy S4 smartphone that carries multiple sensors. The S4 remains popular as it contains more sensors than later editions. For example, it can sense temperature."^^xsd:string ; | ||
rdfs:label "Samsung Galaxy S4"^^xsd:string ; | ||
sosa-core:hosts examples:TempSensorS4_23 ; | ||
sosa:hosts ex:TempSensorS4_23 ; | ||
. | ||
examples:TempObservation1 | ||
rdf:type sosa-core:Observation ; | ||
ex:TempObservation1 | ||
rdf:type sosa:Observation ; | ||
rdfs:comment "A temperature observation created using the SamsungGalaxyS4_23."^^xsd:string ; | ||
rdfs:comment "Not yet linked through to the platform or sensor. ---> (kj). Yes, this will be 'linked' via SPARQL queries and possible via future axioms outside of SOSA-core. There is no need to habve explicit relations between anything and everything. Also, keep in mind that this is all under the OWA."^^xsd:string ; | ||
rdfs:label "Temperature observation 1."^^xsd:string ; | ||
sosa-core:madeBySensor examples:TempSensorS4_23; | ||
sosa-core:hasFeatureOfInterest <http://www.w3.org/ns/sosa/examples#4830EH_UCSB> ; | ||
sosa-core:hasResult examples:TempObservationResult1 ; | ||
sosa-core:resultTime "2016-08-10T08:30:00"^^xsd:dateTime ; | ||
sosa-core:usedProcedure examples:RoomTemperature ; | ||
sosa:madeBySensor ex:TempSensorS4_23; | ||
sosa:hasFeatureOfInterest <http://www.w3.org/ns/sosa/examples#4830EH_UCSB> ; | ||
sosa:hasResult ex:TempObservationResult1 ; | ||
sosa:resultTime "2016-08-10T08:30:00"^^xsd:dateTime ; | ||
sosa:usedProcedure ex:RoomTemperature ; | ||
. | ||
examples:TempSensorS4_23 | ||
rdf:type sosa-core:Sensor ; | ||
ex:TempSensorS4_23 | ||
rdf:type sosa:Sensor ; | ||
rdfs:label "The temperature sensor mounted on the S4 platform with the ID 23."^^xsd:string ; | ||
sosa-core:hostedBy examples:SamsungGalaxyS4_23 ; | ||
sosa:hostedBy ex:SamsungGalaxyS4_23 ; | ||
. | ||
examples:TempObservationResult1 | ||
rdf:type sosa-core:Result ; | ||
ex:TempObservationResult1 | ||
rdf:type sosa:Result ; | ||
rdfs:comment "The observed temperature for observation 1."^^xsd:string ; | ||
rdfs:label "Result of temperature observation 1."^^xsd:string ; | ||
sosa-core:hasValue "23.8"^^xsd:double ; | ||
sosa:hasValue "23.8"^^xsd:double ; | ||
. | ||
examples:TempObservation2 | ||
rdf:type sosa-core:Observation ; | ||
ex:TempObservation2 | ||
rdf:type sosa:Observation ; | ||
rdfs:comment "A temperature observation created using the SamsungGalaxyS4_23."^^xsd:string ; | ||
rdfs:label "Temperature observation 2. We usue this here to demonstrate that all room temperature observations use the same procedure."^^xsd:string ; | ||
sosa-core:madeBySensor examples:TempSensorS4_23; | ||
sosa-core:hasFeatureOfInterest <http://www.w3.org/ns/sosa/examples#4830EH_UCSB> ; | ||
sosa-core:hasResult examples:TempObservationResult2 ; | ||
sosa-core:resultTime "2016-08-10T09:33:00"^^xsd:dateTime ; | ||
sosa-core:usedProcedure examples:RoomTemperature ; | ||
sosa:madeBySensor ex:TempSensorS4_23; | ||
sosa:hasFeatureOfInterest ex:4830EH_UCSB ; | ||
sosa:hasResult [ rdf:value 23.8 ] ; | ||
sosa:resultTime "2016-08-10T09:33:00"^^xsd:dateTime ; | ||
sosa:usedProcedure ex:RoomTemperature ; | ||
. | ||
examples:TempObservationResult2 | ||
rdf:type sosa-core:Result ; | ||
ex:TempObservationResult2 | ||
rdf:type sosa:Result ; | ||
rdfs:comment "The observed temperature for observation 2."^^xsd:string ; | ||
rdfs:label "Result of temperature observation 2."^^xsd:string ; | ||
sosa-core:hasValue "24.3"^^xsd:double ; | ||
sosa:hasValue "24.3"^^xsd:double ; | ||
. | ||
examples:UCSB | ||
rdf:type sosa-core:FeatureOfInterest ; | ||
sosa-core:hasSample examples:4830EH_UCSB ; | ||
ex:UCSB | ||
rdf:type sosa:FeatureOfInterest ; | ||
sosa:hasSample ex:4830EH_UCSB ; | ||
rdfs:comment "In our example we would like to study the average room temperature of offices at UCSB. Hence, UCSB is the feature of interest. We will only observe the temperature at some offices that will act as samples."^^xsd:string ; | ||
rdfs:label "University of California, Santa Barbara"^^xsd:string ; | ||
. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters