Numeric Datatype Properties Default to Decimal Even When Previous and Current Value is Integer #1285
Description
When you edit a numeric data property the datatype always defaults to xsd:decimal, even if the previous value was an integer and even if you are entering an integer value. Here's an example where I'm editing the year for a Kyoto Protocol instance (built on the Gist Upper Model). The year value is 2005 and I want the datatype to be xsd:integer because a year can't have decimals. In screen one you see the existing value which is an integer. In screen two as soon as I change the value, the datatype converts to xsd:decimal even though the value is still an integer. This is on Protege 5.6.4 on Windows 11 Pro.
