obsValue datatype is missing

[aftiqb]

Reported by Soren Roug

We’ve noticed that the sdmx-measure:obsValue doesn’t have a datatype any longer. Is it possible to do some detection of the value so if it is a number, then the datatype is set accordingly? Also, Virtuoso allows scientific notation in xsd:double, but not in xsd:decimal, so we prefer xsd:double.

Further info about this issue can be found in #12

[aftiqb]

the bug is still reproducible

[csarven]

Just a comment.. why would the data modeling be dependent on how a particular implementation (Virtuoso) works? IMO, xsd:decimal is generally safer to go with without loss of precision.

[aftiqb]

Observation values comes in integer, double and string format. Our data modeling is not dependent on Virtuoso or any other implementation. We parse the observations in first iteration to determine the data type of a particular dataset and then assign the appropriate data type to all observation values of that particular data set