Some conversion factors exceed the xsd:decimal range for a minimally conforming processor

[rjyounes]

We got an error when loading the client's reference data excerpt into a triplestore. According to the XSD spec, a minimally conforming processor must support 18 significant digits. The client is using RDFox, which apparently only supports this minimum, in contrast to AllegroGraph.

Examples:

gistd:_UnitOfMeasure_ounce_per_foot gist:conversionFactor "0.093010246473097102666"^^xsd:decimal ;
gistd:_UnitOfMeasure_cubic_foot_per_minute gist:conversionFactor "0.0004719474432000001"^^xsd:decimal ;

@philblackwood Do you have an immediate suggestion for how I can fix this short-term for the client? Should I type all conversion factors xsd:double? Or just round it to 18 decimal places? What are you likely to do to fix it?

[Jamie-SA]

I would not suggest using xsd:double as it's limitations are poorly understood by most people.

Does RDFox not handle it at all (fails on import)? If it just truncates the input then I guess that would give you what you want, so I'm guessing it fails to accept a number with more precision than it can support. I wonder if the xsd spec specifies what should happen.

[MichaelSullivanArchitect]

curious, what are the limitations on xsd:double? Or is the behavior vendor specific?

[rjyounes]

Does RDFox not handle it at all (fails on import)? If it just truncates the input then I guess that would give you what you want, so I'm guessing it fails to accept a number with more precision than it can support. I wonder if the xsd spec specifies what should happen.

RDFox fails with an error on ingest.