Property "magnitude" of DV_COUNT should be an Integer but it is a long in XML-Schema

Description

The property "magnitude" of DV_COUNT according to OpenEHR specification should be an Integer, but in the XML-Schema (http://www.openehr.org/releases/1.0.2/its/XML-schema/documentation/BaseTypes.xsd.html#h1138537063) it is a long!

Environment

None

Activity

Show:
Heath Frankel
May 8, 2015, 12:53 AM

XML schema is a implementation of the logical specifications, so there will be some variations based on the best way to implement in that technology. In XML schema, integer will be limited to a not very big number so to avoid this limitation long has been used.

Sebastian Iancu
May 8, 2015, 8:30 PM

I think the issue is rightfully reported: specification is stating DV_COUNT.magnitude should be INTEGER, which according to support_im.pdf is a 32-bit integer, which according to w3schools is INTEGER or INT in XSD. XSD-LONG has no equivalent in openEHR, perhaps DOUBLE is the closest one, but that's not intended by DV_COUNT.magnitude.
Is there a request to support 64-bit integers for a magnitude?

Heath Frankel
May 9, 2015, 4:22 AM

In that case, I am happy with the change but we need to see if this has any impact on system vendors. Perhaps we should offer two options: change DV_COUNT to 64 bit integer or reduce the XML schema to INT.

Personally I don't see why we wouldn't support 64-bit integers and don't see why we would have a new type to do so unless it is to comply with the ISO data types standard.

Ian McNicoll
May 9, 2015, 6:52 AM

I am struggling to think of any use cases for a maximal 32 but integer in the archetypes we have modelled so far, never mind a 64 bit integer.

No harm in supporting 64-bit but no requirement either.

Making DV_COUNT 64-bit would seem to be the least disruptive option.

Boštjan Lah
May 11, 2015, 7:08 AM

I agree with Ian - making it 64bit is the least disruptive option.

Reporter

Moretti Leonardo

Labels

None

Affects versions

Priority

Minor
Configure