decimalValue misleadingly suggests that the range would be xsd:decimal

[uscholdm]

One would expect that a property named decimalValue would have xsd:decimal as its range. It does not. The range is now xsd:double.

FIX: change the name to doubleValue or change the range to xsd:decimal.

This future-proofing allows for other properties that may need to point to particular datatypes. E.g. floatValue, integerValue etc.

See also #171

[Jamie-SA]

No one commented on this so I don't know if that means there is no support for it, or everyone agreed with it.
Should we consider this for the v10 release?

[rjyounes]

@uscholdm @Jamie-SA Are this and #171 the same or different? If the same, please combine them.

[Jamie-SA]

@rjyounes the title of these two issues address different problems, but I think @uscholdm 's 2nd suggestion in #171 covers the solution for this issue as well.

I don't see that we need 2 issues for this. I could see closing this issue and changing the title of 171 to include fixing all problems with gist:decimalValue if you wanted to go that route.

[uscholdm]

That makes sense to me.

[rjyounes]

Duplicate of #171.