From 329795e7c8405953e287447c2fa649ff1cc9832a Mon Sep 17 00:00:00 2001 From: Nicholas Jarboe Date: Tue, 28 Jun 2022 13:57:15 -0600 Subject: [PATCH 1/7] Update Dataset.md fixed typo --- guides/Dataset.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/guides/Dataset.md b/guides/Dataset.md index f3099d1..ebede08 100644 --- a/guides/Dataset.md +++ b/guides/Dataset.md @@ -316,7 +316,7 @@ Or as a URL: } -However, if the identifier is a persistent identifier such as a DOI, ARK, or accession nmumber, then the best way to represent these identifiers is by using a [schema:PropertyValue](https://schema.org/PropertyValue). The PropertyValue allows for more information about the identifier to be represented such as the identifier type or scheme, the identifier's value, it's URL and more. Because of this flexibility, we recommend using PropertyValue for all identifier types. +However, if the identifier is a persistent identifier such as a DOI, ARK, or accession number, then the best way to represent these identifiers is by using a [schema:PropertyValue](https://schema.org/PropertyValue). The PropertyValue allows for more information about the identifier to be represented such as the identifier type or scheme, the identifier's value, it's URL and more. Because of this flexibility, we recommend using PropertyValue for all identifier types. [schema:Dataset](https://schema.org/Dataset) also defines a field for the [schema:citation](https://schema.org/citation) as either text or a [schema:CreativeWork](https://schema.org/CreativeWork). To provide citation text: From 5c982f623e765c214489d9797fb097a3cc9ddade Mon Sep 17 00:00:00 2001 From: Nick Jarboe Date: Tue, 28 Jun 2022 17:14:56 -0600 Subject: [PATCH 2/7] Removed text elements from temporalCoverage examples and edited the descriptions --- guides/Dataset.md | 24 ++++++++++++------------ 1 file changed, 12 insertions(+), 12 deletions(-) diff --git a/guides/Dataset.md b/guides/Dataset.md index 58f423a..a0f6e72 100644 --- a/guides/Dataset.md +++ b/guides/Dataset.md @@ -615,7 +615,7 @@ https://github.com/ESIPFed/science-on-schema.org/blob/master/examples/dataset/te }, "@type": "Dataset", "description": "Eruptive activity at Mt. St. Helens, Washington, March 1980 - January 1981", - "temporalCoverage": ["1980-03-27T19:36:00/1981-01-03T00:00:00Z", + "temporalCoverage": [ { "@type": "time:ProperInterval", "time:hasBeginning": { @@ -630,7 +630,7 @@ https://github.com/ESIPFed/science-on-schema.org/blob/master/examples/dataset/te } -2. The dataset's temporalCoverage is described using Instant, inTimePosition, hasTRS, and numericPosition elements for a single geological date/age without uncertainties from [OWL Time](http://www.w3.org/2006/time). Use a decimal value with appropriate timescale temporal reference system (TRS) and date/age unit abbreviation. Also provide a text form of the temporalCoverage (here "760 ka"). The human readable description can be found in the description field: "Eruption of Bishop Tuff, about 760,000 years ago". +2. The dataset's temporalCoverage is described using Instant, inTimePosition, hasTRS, and numericPosition elements for a single geological date/age without uncertainties from [OWL Time](http://www.w3.org/2006/time). Use a decimal value with appropriate timescale temporal reference system (TRS) and date/age unit abbreviation. The human readable description can be found in the description field: "Eruption of Bishop Tuff, about 760,000 years ago". *Example*: @@ -644,7 +644,7 @@ https://github.com/ESIPFed/science-on-schema.org/blob/master/examples/dataset/te { "@type": "Dataset", "description": "Eruption of Bishop Tuff, about 760,000 years ago", - "temporalCoverage": ["760 ka", + "temporalCoverage": [ { "@type": "time:Instant", "time:inTimePosition": { @@ -666,7 +666,7 @@ https://github.com/ESIPFed/science-on-schema.org/blob/master/examples/dataset/te } -3. The dataset's temporalCoverage is described using the Instant, inTimePosition, TimePosition, numericPosition from [OWL Time](http://www.w3.org/2006/time) with a geological date/age with uncertainties. Use a decimal value with appropriate timescale temporal reference system(TRS), date/age unit abbreviation, the uncertainty value and specify at what sigma. Also provide a text form of the temporalCoverage (here "4.404 +/-+/- 0.008 Ga"). "+/-+/-" indicates the uncertainty is given at 2-sigma. The human readable description can be found in the description field: "Very old zircons from the Jack Hills formation Australia 4.404 +- 0.008 Ga (2-sigma)". +3. The dataset's temporalCoverage is described using the Instant, inTimePosition, TimePosition, numericPosition from [OWL Time](http://www.w3.org/2006/time) with a geological date/age with uncertainties. Use a decimal value with appropriate timescale temporal reference system(TRS), date/age unit abbreviation, the uncertainty value and specify at what sigma. The human readable description can be found in the description field: "Very old zircons from the Jack Hills formation Australia 4.404 +- 0.008 Ga (2-sigma)". *Example*: @@ -681,7 +681,7 @@ https://github.com/ESIPFed/science-on-schema.org/blob/master/examples/dataset/te { "@type": "Dataset", "description": "Very old zircons from the Jack Hills formation Australia 4.404 +- 0.008 Ga (2-sigma)", - "temporalCoverage": ["4.404 +/-+/- 0.008 Ga", + "temporalCoverage": [ { "@type": "time:Instant", "time:inTimePosition": { @@ -711,7 +711,7 @@ https://github.com/ESIPFed/science-on-schema.org/blob/master/examples/dataset/te } -4. The dataset's temporalCoverage is described using the ProperInterval, hasBeginning, hasEnd, Instant, inTimePosition, TimePosition, and hasTRS elements from [OWL Time](http://www.w3.org/2006/time) with a geological date/age range with uncertainties. Use a decimal value with appropriate timescale temporal reference system(TRS), date/age unit abbreviation, uncertainty value and at what sigma. Also provide a text form of the temporalCoverage (here "17.1 +/- 0.15 to 15.7 +/- 0.14 Ma"). "+/-" indicates the uncertainty is given at 1-sigma. The human readable description can be found in the description field: "Isotopic ages determined at the bottom and top of a stratigraphic section in the Columbia River Basalts". +4. The dataset's temporalCoverage is described using the ProperInterval, hasBeginning, hasEnd, Instant, inTimePosition, TimePosition, and hasTRS elements from [OWL Time](http://www.w3.org/2006/time) with a geological date/age range with uncertainties. Use a decimal value with appropriate timescale temporal reference system(TRS), date/age unit abbreviation, uncertainty value and at what sigma. The human readable description can be found in the description field: "Isotopic ages determined at the bottom and top of a stratigraphic section in the Columbia River Basalts". *Example*: @@ -728,7 +728,7 @@ https://github.com/ESIPFed/science-on-schema.org/blob/master/examples/dataset/te { "@type": "Dataset", "description": "Isotopic ages determined at the bottom and top of a stratigraphic section in the Columbia River Basalts", - "temporalCoverage": ["17.1 +/- 0.15 to 15.7 +/- 0.14 Ma", + "temporalCoverage": [ { "@type": "time:ProperInterval", "time:hasBeginning": { @@ -788,7 +788,7 @@ https://github.com/ESIPFed/science-on-schema.org/blob/master/examples/dataset/te } -5. The dataset's temporalCoverage is described using the Instant, inTimePosition, TimePosition, and hasTRS elements from [OWL Time](http://www.w3.org/2006/time) with a archeological date/age range with uncertainties. Use a decimal value with appropriate timescale temporal reference system(TRS), date/age unit abbreviation, the older and younger uncertainty values and at what sigma. Also provide a text form of the temporalCoverage (here "2640 +130 -80 BP-CAL (INTCAL20)"). The human readable description can be found in the description field: "Age of a piece of charcoal found in a burnt hut at an archeological site in Kenya carbon dated at BP Calibrated of 2640 +130 -80 (one-sigma) using the INTCAL20 carbon dating curve." +5. The dataset's temporalCoverage is described using the Instant, inTimePosition, TimePosition, and hasTRS elements from [OWL Time](http://www.w3.org/2006/time) with a archeological date/age range with uncertainties. Use a decimal value with appropriate timescale temporal reference system(TRS), date/age unit abbreviation, the older and younger uncertainty values and at what sigma. The human readable description can be found in the description field: "Age of a piece of charcoal found in a burnt hut at an archeological site in Kenya carbon dated at BP Calibrated of 2640 +130 -80 (one-sigma) using the INTCAL20 carbon dating curve." *Example:* @@ -804,7 +804,7 @@ https://github.com/ESIPFed/science-on-schema.org/blob/master/examples/dataset/te { "@type": "Dataset", "description": "Age of a piece of charcoal found in a burnt hut at an archeological site in Kenya carbon dated at BP Calibrated of 2640 +130 -80 (one-sigma) using the INTCAL20 carbon dating curve.", - "temporalCoverage": ["2640 +130 -80 BP-CAL (INTCAL20)", + "temporalCoverage": [ { "@type": "time:Instant", "time:inTimePosition": { @@ -838,7 +838,7 @@ https://github.com/ESIPFed/science-on-schema.org/blob/master/examples/dataset/te } -6. The dataset's temporalCoverage is described using the Instant, TimePosition, inTimePosition, NominalPosition, Interval, hasBeginning, hasEnd, and hasTRS elements from [OWL Time](http://www.w3.org/2006/time). With temporal coverage that is a named time interval from a geologic time scale, provide numeric positions of the beginning and end for interoperability. Providing the numeric values is only critical, but still recommended, if the TRS for the nominalPosition is not the [International Chronostratigraphic Chart](https://stratigraphy.org/chart). +6. The dataset's temporalCoverage is described using the Instant, TimePosition, inTimePosition, NominalPosition, Interval, hasBeginning, hasEnd, and hasTRS elements from [OWL Time](http://www.w3.org/2006/time). With temporal coverage that is a named time interval from a geologic time scale, provide numeric positions of the beginning and end for interoperability. Providing the numeric values is only critical, but still recommended, if the TRS for the nominalPosition is not the [International Chronostratigraphic Chart](https://stratigraphy.org/chart). In this example the temporalCoverage is described in two ways: by the named interval Bartonian and by defining a time interval using numerical beginning and end values. *Example:* @@ -856,7 +856,7 @@ https://github.com/ESIPFed/science-on-schema.org/blob/master/examples/dataset/te { "@type": "Dataset", "description": "Temporal position expressed with a named time ordinal era from [International Chronostratigraphic Chart](https://stratigraphy.org/chart):", - "temporalCoverage": ["Bartonian", + "temporalCoverage": [ { "@type": "time:Instant", "time:inTimePosition": { @@ -926,7 +926,7 @@ https://github.com/ESIPFed/science-on-schema.org/blob/master/examples/dataset/te }, "@type": "Dataset", "description": "Temporal position expressed with an interval bounded by named time ordinal eras from [International Chronostratigraphic Chart](https://stratigraphy.org/chart). NumericPositions not included, expect clients can lookup bounds for ISC nominal positions:", - "temporalCoverage": ["Triassic to Jurassic", { + "temporalCoverage": [{ "@type": "time:ProperInterval", "time:hasBeginning": { "@type": "time:Instant", From e03bc94069ebb8395a21803b43c3c2c631caa8fd Mon Sep 17 00:00:00 2001 From: Melinda Minch Date: Thu, 30 Jun 2022 11:52:45 -0700 Subject: [PATCH 3/7] Fix the 'publisher-provider' anchor link This link wasn't working because the actual anchor has an extra dash in it. --- guides/Dataset.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/guides/Dataset.md b/guides/Dataset.md index f3099d1..9a22553 100644 --- a/guides/Dataset.md +++ b/guides/Dataset.md @@ -24,7 +24,7 @@ - [Handling multiple locations](#handling-multiple-locations) - [Spatial Reference Systems](#spatial-reference-systems) - [Roles of People](#roles-of-people) - - [Publisher / Provider](#publisher-provider) + - [Publisher / Provider](#publisher--provider) - [Funding](#funding) - [License](#license) - [Checksum](#checksum) From dd9f7697a832f279e984f3472ca354f5747e8c5a Mon Sep 17 00:00:00 2001 From: Adam Shepherd <2117576+ashepherd@users.noreply.github.com> Date: Fri, 29 Jul 2022 12:21:17 -0400 Subject: [PATCH 4/7] rename spdx:checksumAlgorithm to spdx:algorithm --- guides/Dataset.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/guides/Dataset.md b/guides/Dataset.md index 27bb8c6..10bb34c 100644 --- a/guides/Dataset.md +++ b/guides/Dataset.md @@ -1574,14 +1574,14 @@ Here's an example that provides two different checksum values for a single digit { "@type": "spdx:Checksum", "spdx:checksumValue": "39ae639d33cea4a287198bbcdca5e6856e6607a7c91dc4c54348031be2ad4c51", - "spdx:checksumAlgorithm": { + "spdx:algorithm": { "@id": "spdx:checksumAlgorithm_sha256" } }, { "@type": "spdx:Checksum", "spdx:checksumValue": "65d3616852dbf7b1a6d4b53b00626032", - "spdx:checksumAlgorithm": { + "spdx:algorithm": { "@id": "spdx:checksumAlgorithm_md5" } } From 8f57e3e8c04929433443ae0af661b7b6f38bbf13 Mon Sep 17 00:00:00 2001 From: Adam Shepherd <2117576+ashepherd@users.noreply.github.com> Date: Mon, 1 Aug 2022 17:50:47 -0400 Subject: [PATCH 5/7] remove Monday mtg --- GOVERNANCE.md | 1 - 1 file changed, 1 deletion(-) diff --git a/GOVERNANCE.md b/GOVERNANCE.md index 70e1772..1f733dd 100644 --- a/GOVERNANCE.md +++ b/GOVERNANCE.md @@ -5,7 +5,6 @@ We will leverage the [Earth Science Information Partners - Science on Schema.org Meetings are scheduled twice monthly: - When: - - 1st Monday at 5pmET - 4th Thursday, 2:30pmET - Where: Telecons via Zoom - Connection: https://us02web.zoom.us/j/85680809640?pwd=a09zQTl2eFd6NnpoRkRxNHlDdFN0dz09 From c745e4c970e17aa540ff0a594056714b4755ffaa Mon Sep 17 00:00:00 2001 From: Adam Shepherd <2117576+ashepherd@users.noreply.github.com> Date: Mon, 1 Aug 2022 17:51:07 -0400 Subject: [PATCH 6/7] Update README.md --- README.md | 1 - 1 file changed, 1 deletion(-) diff --git a/README.md b/README.md index 87daf89..743fe50 100644 --- a/README.md +++ b/README.md @@ -30,7 +30,6 @@ Science on Schema.org (SOSO) releases are archived on Zenodo, and the current re This guidance has been created by members of the ESIP [science-on-schema.org cluster](http://wiki.esipfed.org/index.php/Schema.org_Cluster). The cluster will be seeking endorsement across all members of ESIP, and in the meantime is releasing a series of progressively more mature guidance documents for the community. Your feedback and contributions are welcome. The cluster meets twice monthly, and all are welcome: - When: - - 1st Monday at 5pm ET - 4th Thursday, 2:30pm ET - Where: Telecons via Zoom - Connection: https://us02web.zoom.us/j/84043422486?pwd=bGM4YkFyMkFGSW1FZG5yaFRNaGNvdz09 From b6e5a9aba3ed6631db2048aaf3d0a01f6fffb383 Mon Sep 17 00:00:00 2001 From: Matt Jones Date: Mon, 1 Aug 2022 15:25:28 -0800 Subject: [PATCH 7/7] Fix auto-link to publisher-and-provider section so it avoids special characters. --- guides/Dataset.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/guides/Dataset.md b/guides/Dataset.md index 70ec705..7245232 100644 --- a/guides/Dataset.md +++ b/guides/Dataset.md @@ -24,7 +24,7 @@ - [Handling multiple locations](#handling-multiple-locations) - [Spatial Reference Systems](#spatial-reference-systems) - [Roles of People](#roles-of-people) - - [Publisher / Provider](#publisher--provider) + - [Publisher and Provider](#publisher-and-provider) - [Funding](#funding) - [License](#license) - [Checksum](#checksum) @@ -1386,7 +1386,7 @@ Notice that since Uta Passow has already been defined in the document with `"@id Back to [top](#top) -### Publisher / Provider +### Publisher and Provider ![Publisher/Provider](/assets/diagrams/dataset/dataset_publisher-provider.svg "Dataset - Publisher/Provider")