From 686e47c7d429041888797dd72607eb9f2aeeff6d Mon Sep 17 00:00:00 2001 From: philblackwood Date: Mon, 24 Aug 2026 16:00:02 -0400 Subject: [PATCH 1/3] simplify the range of gist:numericValue --- ontologies/gistCore.ttl | 14 +------------- 1 file changed, 1 insertion(+), 13 deletions(-) diff --git a/ontologies/gistCore.ttl b/ontologies/gistCore.ttl index 194b55a0..7134ea96 100644 --- a/ontologies/gistCore.ttl +++ b/ontologies/gistCore.ttl @@ -3124,28 +3124,16 @@ gist:numericValue rdfs:range [ a rdfs:Datatype ; owl:unionOf ( - xsd:byte xsd:decimal xsd:double xsd:float - xsd:int xsd:integer - xsd:long - xsd:negativeInteger - xsd:nonNegativeInteger - xsd:nonPositiveInteger - xsd:positiveInteger - xsd:short - xsd:unsignedByte - xsd:unsignedInt - xsd:unsignedLong - xsd:unsignedShort owl:rational - owl:real ) ; ] ; skos:definition "The actual value of a magnitude."^^xsd:string ; skos:prefLabel "numeric value"^^xsd:string ; + skos:scopeNote "Caution is advised when using the xsd:float, xsd:integer, or owl:rational datatypes. The xsd:float datatype is less precise than xsd:double, and not recommended unless the source data is xsd:float or if precision is not as important as the size of the data or speed of computation. Some downstream applications might be limited to using the 32-bit xsd:int datatype instead of xsd:integer; if so, check to see that the xsd:integer values being passed downstream are within the 32-bit range. Some triple-stores cannot do math using values of the owl:rational datatype."^^xsd:string ; . gist:occursIn From e4e6ef1ed1c7c1a8ed1f1ff67bba39f791693cd4 Mon Sep 17 00:00:00 2001 From: philblackwood Date: Mon, 24 Aug 2026 16:04:43 -0400 Subject: [PATCH 2/3] simplify range of gist:numericValue --- docs/release_notes/1386-numericValue | 4 ++++ 1 file changed, 4 insertions(+) create mode 100644 docs/release_notes/1386-numericValue diff --git a/docs/release_notes/1386-numericValue b/docs/release_notes/1386-numericValue new file mode 100644 index 00000000..c0f68f7c --- /dev/null +++ b/docs/release_notes/1386-numericValue @@ -0,0 +1,4 @@ +### Major Updates + +- Simplified the range of `gist:numericValue`. Issue [#1386](https://github.com/semanticarts/gist/issues/1386). + From 8dcf431bc20742566c8e9a8c7ffb62f18b0a8f06 Mon Sep 17 00:00:00 2001 From: Phil Blackwood <82112369+philblackwood@users.noreply.github.com> Date: Mon, 28 Sep 2026 10:33:46 -0400 Subject: [PATCH 3/3] Update ontologies/gistCore.ttl Co-authored-by: Rebecca Younes --- ontologies/gistCore.ttl | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ontologies/gistCore.ttl b/ontologies/gistCore.ttl index 7134ea96..2780bb95 100644 --- a/ontologies/gistCore.ttl +++ b/ontologies/gistCore.ttl @@ -3133,7 +3133,7 @@ gist:numericValue ] ; skos:definition "The actual value of a magnitude."^^xsd:string ; skos:prefLabel "numeric value"^^xsd:string ; - skos:scopeNote "Caution is advised when using the xsd:float, xsd:integer, or owl:rational datatypes. The xsd:float datatype is less precise than xsd:double, and not recommended unless the source data is xsd:float or if precision is not as important as the size of the data or speed of computation. Some downstream applications might be limited to using the 32-bit xsd:int datatype instead of xsd:integer; if so, check to see that the xsd:integer values being passed downstream are within the 32-bit range. Some triple-stores cannot do math using values of the owl:rational datatype."^^xsd:string ; + skos:scopeNote "Caution is advised when using the xsd:float, xsd:integer, or owl:rational datatypes. The xsd:float datatype is less precise than xsd:double, and not recommended unless the source data is xsd:float or if precision is not as important as the size of the data or speed of computation. Some downstream applications might be limited to using the 32-bit xsd:int datatype instead of xsd:integer; if so, check to see that the xsd:integer values being passed downstream are within the 32-bit range. Some triplestores cannot do math using values of the owl:rational datatype."^^xsd:string ; . gist:occursIn