Merge pull request #1104 from lewismc/ISSUE-1103

ISSUE-1103 Update References to SWEET in eo-qb document

UseCases/SDWUseCasesAndRequirements.html

@@ -598,7 +598,7 @@ <h3>Use of a place name ontology for geo-parsing text and geo-enabling searches<
           <div class="visible">
           <p>The British Geological Survey (BGS) has valuable geoscience data in text form dating back 180 years, which is gradually being scanned and OCR to make it more accessible and searchable. Much of the information in the reports concerns observations or interpretations made at a location or about a named geological feature. We would like the relevant information in those documents to be retrievable from a Web search using coordinate limit criteria or using a place name criteria, so this use case requires a place name ontology (or federated ontologies).</p>
           <p>For BGS's purposes the ontology should contain historical place names, named subsurface geological features (e.g. Widmerpool Gulf), palaeogeographic place names, and named submarine features (e.g. <a href="http://www.gebco.net/data_and_products/undersea_feature_names/">GEBCO undersea feature names </a>).</p>
-          <p>To extend the capabilities into the vertical dimension then the ontology should also contain the names of qualitative earth realms (vertical divisions within the atmosphere, ocean and solid earth – such as in <a href="https://sweet.jpl.nasa.gov/">the SWEET ontology</a>).</p>
+          <p>To extend the capabilities into the vertical dimension then the ontology should also contain the names of qualitative earth realms (vertical divisions within the atmosphere, ocean and solid earth – such as in <a href="https://sweetontology.net">the SWEET ontology</a>).</p>
           <p>To extend the capabilities into the time dimension then the ontology should also contain the names of historical and geological time periods (e.g. <a href="https://www.seegrid.csiro.au/wiki/CGIModel/GeologicTime#GeologicTime_XML">https://www.seegrid.csiro.au/wiki/CGIModel/GeologicTime#GeologicTime_XML</a>, used in a recent example of geological age name parser at <a href="http://www.agenames.org">http://www.agenames.org</a>)</p>
           <p>With a resource like this, all text resources could be parsed to locate them in time and space.</p>
           <p>Each named feature should have a spatial attribute, either as topological relations to other named features, or as spatial-temporal extent appropriate for various scales and with appropriate uncertainties (i.e. fuzzy definitions of geometry and time periods). Versioning will be important e.g. for administrative boundaries that change frequently.</p>

eo-qb/ANU-LED-example.ttl

@@ -12,7 +12,7 @@
 @prefix time: <http://www.w3.org/2006/time#> .
 @prefix foaf: <http://xmlns.com/foaf/0.1/> .
 @prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
-@prefix sweet: <http://sweet.jpl.nasa.gov/2.3/prop.owl#> .
+@prefix sweet: <http://sweetontology.net/propFraction/> .
 @prefix prov: <http://www.w3.org/ns/prov#> .
 @prefix skos: <http://www.w3.org/2004/02/skos/core#> .
 @prefix sdmx-concept:  <http://purl.org/linked-data/sdmx/2009/concept#> .

eo-qb/config.js

@@ -116,9 +116,9 @@ var respecConfig = {
          title: "DOLCE+DnS Ultralite (DUL)"
       },
         "sweet": {
-            href: "https://sweet.jpl.nasa.gov/",
-            authors: ["JPL"],
-            title: "SWEET Overview"
+            href: "https://sweetontology.net",
+            authors: ["ESIP"],
+            title: "SWEET Home"
         },
         "perf-vgraph": {
             href: "http://ceur-ws.org/Vol-248/paper2.pdf",

eo-qb/index.html

@@ -978,7 +978,7 @@ <h2>Summary of ontologies used</h2>
     <tr><td><code>skos:</code></td><td><a href="http://www.w3.org/2004/02/skos/core">http://www.w3.org/2004/02/skos/core#</a></td><td>[[skos-reference]]</td></tr>
     <tr><td><code>sosa:</code></td><td><a href="http://www.w3.org/ns/sosa/">http://www.w3.org/ns/sosa/</a></td><td rowspan="2">[[vocab-ssn]]</td></tr>
     <tr><td><code>ssn:</code></td><td><a href="http://www.w3.org/ns/ssn/">http://www.w3.org/ns/ssn/</a></td></tr>
-    <tr><td><code>sweet:</code></td><td><a href="http://sweet.jpl.nasa.gov/2.3/prop.owl#">http://sweet.jpl.nasa.gov/2.3/prop.owl#</a></td><td>[[sweet]]</td></tr>
+    <tr><td><code>sweet:</code></td><td><a href="http://sweetontology.net/propFraction/">http://sweetontology.net/propFraction/</a></td><td>[[sweet]]</td></tr>
     <tr><td><code>time:</code></td><td><a href="http://www.w3.org/2006/time#">http://www.w3.org/2006/time#</a></td><td>[[owl-time]]</td></tr>
     <tr><td><code>xsd:</code></td><td><a href="http://www.w3.org/2001/XMLSchema#">http://www.w3.org/2001/XMLSchema#</a></td><td>[[swbp-xsch-datatypes]]</td></tr>
 </tbody>

publishing-snapshots/2015-12-17-UseCases/diff-20151217.html

@@ -12128,7 +12128,7 @@ <h3 resource="#h-useofaplacenameontologyforgeo-parsingtextandgeo-enablingsearche
 such
 as
 in
-<a href=" https://sweet.jpl.nasa.gov/">
+<a href=" https://sweetontology.net">
 the
 SWEET
 ontology

publishing-snapshots/2015-12-17-UseCases/index.html

@@ -542,7 +542,7 @@ <h3 id="h-useofaplacenameontologyforgeo-parsingtextandgeo-enablingsearches" reso
 					<div class="visible">
           <p>BGS has valuable geoscience data in text form dating back 180 years, which is gradually being scanned and OCR to make it more accessible and searchable. Much of the information in the reports concerns observations or interpretations made at a location or about a named geological feature. We would like the relevant information in those documents to be retrievable from a Web search using coordinate limit criteria or using a place name criteria, so this use case requires a place name ontology (or federated ontologies).</p>
           <p>For BGS's purposes the ontology should contain historical place names, named subsurface geological features (e.g. Widmerpool Gulf), palaeogeographic place names, and named submarine features (e.g. <a href="http://www.gebco.net/data_and_products/undersea_feature_names/">GEBCO undersea feature names </a>).</p>
-          <p>To extend the capabilities into the vertical dimension then the ontology should also contain the names of qualitative earth realms (vertical divisions within the atmosphere, ocean and solid earth – such as in <a href=" https://sweet.jpl.nasa.gov/">the SWEET ontology</a>).</p>
+          <p>To extend the capabilities into the vertical dimension then the ontology should also contain the names of qualitative earth realms (vertical divisions within the atmosphere, ocean and solid earth – such as in <a href=" https://sweetontology.net">the SWEET ontology</a>).</p>
           <p>To extend the capabilities into the time dimension then the ontology should also contain the names of historical and geological time periods (e.g. <a href="https://www.seegrid.csiro.au/wiki/CGIModel/GeologicTime#GeologicTime_XML">https://www.seegrid.csiro.au/wiki/CGIModel/GeologicTime#GeologicTime_XML</a>, used in a recent example of geological age name parser at <a href="http://www.agenames.org">http://www.agenames.org</a>)</p>
           <p>With a resource like this, all text resources could be parsed to locate them in time and space.</p>
           <p>Each named feature should have a spatial attribute, either as topological relations to other named features, or as spatial-temporal extent appropriate for various scales and with appropriate uncertainties (i.e. fuzzy definitions of geometry and time periods). Versioning will be important e.g. for administrative boundaries that change frequently.</p>

publishing-snapshots/2016-10-24-UseCases/index.html

@@ -815,7 +815,7 @@ <h3 id="h-useofaplacenameontologyforgeo-parsingtextandgeo-enablingsearches" reso
       <div class="visible">
         <p>The British Geological Survey (BGS) has valuable geoscience data in text form dating back 180 years, which is gradually being scanned and OCR to make it more accessible and searchable. Much of the information in the reports concerns observations or interpretations made at a location or about a named geological feature. We would like the relevant information in those documents to be retrievable from a Web search using coordinate limit criteria or using a place name criteria, so this use case requires a place name ontology (or federated ontologies).</p>
         <p>For BGS's purposes the ontology should contain historical place names, named subsurface geological features (e.g. Widmerpool Gulf), palaeogeographic place names, and named submarine features (e.g. <a href="http://www.gebco.net/data_and_products/undersea_feature_names/">GEBCO undersea feature names </a>).</p>
-        <p>To extend the capabilities into the vertical dimension then the ontology should also contain the names of qualitative earth realms (vertical divisions within the atmosphere, ocean and solid earth – such as in <a href="https://sweet.jpl.nasa.gov/">the SWEET ontology</a>).</p>
+        <p>To extend the capabilities into the vertical dimension then the ontology should also contain the names of qualitative earth realms (vertical divisions within the atmosphere, ocean and solid earth – such as in <a href="https://sweetontology.net">the SWEET ontology</a>).</p>
         <p>To extend the capabilities into the time dimension then the ontology should also contain the names of historical and geological time periods (e.g. <a href="https://www.seegrid.csiro.au/wiki/CGIModel/GeologicTime#GeologicTime_XML">https://www.seegrid.csiro.au/wiki/CGIModel/GeologicTime#GeologicTime_XML</a>, used in a recent example of geological age name parser at <a href="http://www.agenames.org">http://www.agenames.org</a>)</p>
         <p>With a resource like this, all text resources could be parsed to locate them in time and space.</p>
         <p>Each named feature should have a spatial attribute, either as topological relations to other named features, or as spatial-temporal extent appropriate for various scales and with appropriate uncertainties (i.e. fuzzy definitions of geometry and time periods). Versioning will be important e.g. for administrative boundaries that change frequently.</p>

publishing-snapshots/FPWD-2015-06-11-UseCases/Overview.html

@@ -511,7 +511,7 @@ <h3 resource="#h-useofaplacenameontologyforgeo-parsingtextandgeo-enablingsearche
           <div>
           <p>BGS has valuable geoscience data in text form dating back 180 years, which is gradually being scanned and OCR to make it more accessible and searchable. Much of the information in the reports concerns observations or interpretations made at a location or about a named geological feature. We would like the relevant information in those documents to be retrievable from a Web search using coordinate limit criteria or using a place name criteria, so this use case requires a place name ontology (or federated ontologies).</p>
           <p>For BGS's purposes the ontology should contain historical place names, named subsurface geological features (e.g. Widmerpool Gulf), palaeogeographic place names, and named submarine features (e.g. <a href="http://www.gebco.net/data_and_products/undersea_feature_names/">GEBCO undersea feature names </a>).</p>
-          <p>To extend the capabilities into the vertical dimension then the ontology should also contain the names of qualitative earth realms (vertical divisions within the atmosphere, ocean and solid earth – such as in <a href="https://sweet.jpl.nasa.gov/">the SWEET ontology</a>).</p>
+          <p>To extend the capabilities into the vertical dimension then the ontology should also contain the names of qualitative earth realms (vertical divisions within the atmosphere, ocean and solid earth – such as in <a href="https://sweetontology.net">the SWEET ontology</a>).</p>
           <p>To extend the capabilities into the time dimension then the ontology should also contain the names of historical and geological time periods (e.g. <a href="https://www.seegrid.csiro.au/wiki/CGIModel/GeologicTime#GeologicTime_XML">https://www.seegrid.csiro.au/wiki/CGIModel/GeologicTime#GeologicTime_XML</a>, used in a recent example of geological age name parser at <a href="http://www.agenames.org">http://www.agenames.org</a>)</p>
           <p>With a resource like this, all text resources could be parsed to locate them in time and space.</p>
           <p>Each named feature should have a spatial attribute, either as topological relations to other named features, or as spatial-temporal extent appropriate for various scales and with appropriate uncertainties (i.e. fuzzy definitions of geometry and time periods). Versioning will be important e.g. for administrative boundaries that change frequently.</p>

publishing-snapshots/FPWD-2017-01-05-eo-qb/ANU-LED-example.ttl

@@ -11,7 +11,7 @@
 @prefix time: <http://www.w3.org/2006/time#> .
 @prefix foaf: <http://xmlns.com/foaf/0.1/> .
 @prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
-@prefix sweet: <http://sweet.jpl.nasa.gov/2.3/prop.owl#> .
+@prefix sweet: <http://sweetontology.net/propFraction/> .
 @prefix prov: <http://www.w3.org/ns/prov#> .
 @prefix skos: <http://www.w3.org/2004/02/skos/core#> .
 @prefix sdmx-concept:  <http://purl.org/linked-data/sdmx/2009/concept#> .

ssn/integrated/examples/om-20.ttl

@@ -40,7 +40,7 @@ examples:COTest3
   rdfs:comment "Complex Observation test instance" ;
   sosa:hasFeatureOfInterest <http://www.ga.gov.au/bin/gazd01?rec=293604> ;
   sosa:hasResult examples:a1 ;
-  sosa:observedProperty <http://sweet.jpl.nasa.gov/2.0/atmo.owl#Weather> ;
+  sosa:observedProperty <http://sweetontology.net/phenAtmo/Weather> ;
   sosa:phenomenonTime examples:ot1t-3 ;
   sosa:resultTime "2005-01-11T17:22:25.00+10:00"^^xsd:dateTime ;
   sosa:usedProcedure <http://www.example.org/register/process/weatherStation3> ;
@@ -154,7 +154,7 @@ examples:b1_p1
   rdfs:comment "Porosity log Result is encoded using OGC Discrete Point Coverage/interleaved pattern" ;
   sosa:hasFeatureOfInterest examples:b1 ;
   sosa:hasResult examples:CV123476 ;
-  sosa:observedProperty <http://sweet.jpl.nasa.gov/ontology/property.owl#Porosity> ;
+  sosa:observedProperty <http://sweetontology.net/propFraction/Porosity> ;
   sosa:phenomenonTime examples:T9897 ;
   sosa:resultTime "2007-06-06T14:20:30.00+08:00"^^xsd:dateTime ;
   sosa:usedProcedure <http://www.geophysics.org/PO34> ;
@@ -188,7 +188,7 @@ examples:obsTest1
       skos:editorialNote "Use qudt:QuantityValue for sosa:Result" ;
     ] ;
   sosa:madeBySensor <http://www.example.org/register/process/scales34.xml> ;
-  sosa:observedProperty <http://sweet.jpl.nasa.gov/2.0/phys.owl#Mass> ;
+  sosa:observedProperty <http://sweetontology.net/propMass/Mass> ;
   sosa:phenomenonTime examples:ot1t ;
   sosa:resultTime "2005-01-11T16:22:25.00+10:00"^^xsd:dateTimeStamp ;
 .
@@ -204,7 +204,7 @@ examples:obsTest2
   sosa:hasFeatureOfInterest <http://wfs.example.org?request=getFeature&amp;featureid=fruit37f> ;
   sosa:hasResult <http://en.wikipedia.org/wiki/List_of_fruits#Banana> ;
   sosa:madeBySensor <http://www.example.org/party/individual/abc123> ;
-  sosa:observedProperty <http://sweet.jpl.nasa.gov/2.0/biol.owl#Species> ;
+  sosa:observedProperty <http://sweetontology.net/matrBiomass/Species> ;
   sosa:phenomenonTime examples:ot2t ;
   sosa:resultTime "2005-01-11T17:22:25.00+10:00"^^xsd:dateTime ;
   sosa:usedProcedure <http://www.example.org/party/role/field_worker> ;
@@ -216,7 +216,7 @@ examples:obsTest4
   sosa:hasFeatureOfInterest <http://wfs.example.org?request=getFeature&#38;featureid=stc1> ;
   sosa:hasResult examples:DC756254 ;
   sosa:madeBySensor <urn:ogc:object:feature:Sensor:NASA:xyz345> ;
-  sosa:observedProperty <http://sweet.jpl.nasa.gov/2.0/physRadiation.owl#Radiance> ;
+  sosa:observedProperty <http://sweetontology.net/propEnergyFlux/Radiance> ;
   sosa:phenomenonTime examples:ots1t ;
   sosa:resultTime "2005-06-17"^^xsd:date ;
 .