Adam Shepherd

I can confirm this issue on `Virtuoso version 07.20.3215 on Linux (x86_64-pc-linux-gnu), Single Server Edition` RDF Data: [N-Triples](https://github.com/openlink/virtuoso-opensource/files/7122798/n-triples.txt) SPARQL Query: ``` PREFIX opp: PREFIX sosa: SELECT DISTINCT ?label ?depth ?station...

Our SPARQL endpoint is open to the public for now. Here's a URL to the query with duplicate results: https://kg.oceanproteinportal.org/sparql?default-graph-uri=&query=PREFIX+opp%3A+%3Chttp%3A%2F%2Fschema.oceanproteinportal.org%2Fv2%2F%3E%0D%0APREFIX+sosa%3A+%3Chttp%3A%2F%2Fwww.w3.org%2Fns%2Fsosa%2F%3E%0D%0ASELECT+DISTINCT+%3Flabel+%3Fdepth+%3Fstation%0D%0AWHERE+%7B+%0D%0A++%3Curn%3Aopp%3Adataset%3Ametzyme-0.2%3E+opp%3AstoresResultsForSample+%3Fsample+.%0D%0A++++%3Fsample+rdfs%3Alabel+%3Flabel+.+%0D%0A++++FILTER+REGEX%28%3Flabel%2C+%22CID%22%29+.%0D%0A++++%3Fsample+sosa%3AisSampleOf+%3Ffeature+.%0D%0A++++%3Ffeature+opp%3Adepth+%3Fdepth+.%0D%0A++++%3Ffeature+opp%3AinVicinityOfStation+%3FstationInfo+.%0D%0A++++%3FstationInfo+opp%3AstationName+%3Fstation+.%09%0D%0A%7D%0D%0AORDER+BY+%3Flabel&should-sponge=&format=text%2Fhtml&timeout=0&debug=on SNORQL Browser here: https://kg.oceanproteinportal.org/

ah, thank you @kidehen, my apologies! apparently, I'm missing good SPARQL knowledge. sorry for the false alarm

Just wanted to add our use case for the ```missingValues``` property on a field. @BCODMO provides data management support for individual researchers on short-term funding (1-3 yrs) from NSF. Our...

+1

If there's a vocabulary that does geospatial well, we can publish our own context with an update to schema:spatialCoverage to allow valaues for that vocabulary. @charlesvardeman , is there one...

An attempt at adding other representations of a spatial coverage: ``` { "@context": "http://schema.org/", "@type": "Dataset", "name": "XYZ", ... "spatialCoverage": { "@type": "Place", "geo": { "@type": "GeoShape", ... }, "additionalProperty":...

@alko-k, thanks for the suggestion! I'm curious if the responses above mean you are OK with the way the guidance is now (until schema.org makes improvements) or if you have...

I agree with @mbjones on following the schema.org recommended ranges. For those `Dataset` publishers (outside of our discipline(s), possibly) that want to express the actual observed/monitored value of the variable...

see related BoF: https://docs.google.com/document/d/17hrcLpxcAA3_U3MZ3sWHrbaeNVa1k8yaigBzbjmxFHk/edit