[#CMIS-83] Schemas don't allow setting minvalue/maxValue for Decimal property types

OASIS Content Management Interoperability Services (CMIS) TC

Schemas don't allow setting minvalue/maxValue for Decimal property types

Created: 26/Feb/09 01:50 PM Updated: 04/Jan/10 11:35 PM

Component/s:

Schema

Affects Version/s:

Draft 0.50

Fix Version/s:

Draft 0.62

Proposal:

Add minvalue and maxvalue elements to cmisPropertyDecimalDefinitionType

Description

« Hide

The CMIS schemas currently include "minvalue" and "maxvalue" elements for "cmisPropertyIntegerDefinitionType", but not for "cmisPropertyDecimalDefinitionType".

So you can set min/max-value for integers, but not for decimals.

All

Comments

Change History

Sort Order:

[ Permalink | « Hide ]

Al Brown added a comment - 10/Apr/09 05:03 PM

Decimal has precision - e.g., 32, 64, ...
Are min/max required when precision is provided? I don't think this info is needed.

[ Permalink | « Hide ]

Ethan Gur-esh added a comment - 13/Apr/09 12:11 PM

Why are min/max value constraints more important/valid for Integer property types but not definition property types? It seems equally valid to have constraints on either type (e.g. what if I want to model a currency field as a decimal?)

[ Permalink | « Hide ]

Al Brown added a comment - 13/Apr/09 12:44 PM

Integer is not typically expressed using precision, but rather limits due to signed/unsigned, etc. As I understood it, the prior goal was to convey what could be stored in a particular field rather than exposing contraints. However, many systems do have min/max on float/decimal, so if it is important to model these additional constraints, then I am okay to adding it to the specification.

[ Permalink | « Hide ]

Al Brown added a comment - 04/Jan/10 11:35 PM

JIRA Cleanup