using typed integers? - Githubissues

eroux commented 7 years ago

Should we keep xsd:positiveInteger instead of xsd:integer in the data?

A few info I gathered this morning:

Fuseki converts all integer types to xsd:integer, so query results don't know the original type (all come as xsd:integer, I did a small test)
When using JSON native types, only xsd:integers get converted
it's quite easy to figure out if an integer is positive or not, and SHACL has some rules to define a range

If we keep the type, jsonld documents will look like

"workNumberOfVolumes" : {
  "@type" : "xsd:positiveInteger",
  "@value" : "1"
},

instead of

"workNumberOfVolumes" : 1

based on that I propose to make the ranges xsd:integer all the time and to use SHACL rules in the future to check some ranges. wdyt?

xristy commented 7 years ago

+1 I'll make the changes in the owl doc

eroux commented 7 years ago

Reopening for 3 more properties: volumePagesIntro, volumePagesTbrcIntro and volumePagesText have xsd:nonNegativeInteger as Range.

buda-base / owl-schema