[ http://tools.oasis-open.org/issues/browse/CMIS-83?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=10169#action_10169 ]
Ethan Gur-esh commented on CMIS-83:
-----------------------------------
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?)
> Schemas don't allow setting minvalue/maxValue for Decimal property types
> ------------------------------------------------------------------------
>
> Key: CMIS-83
> URL: http://tools.oasis-open.org/issues/browse/CMIS-83
> Project: OASIS Content Management Interoperability Services (CMIS) TC
> Issue Type: Bug
> Components: Schema
> Affects Versions: Draft 0.50
> Reporter: Ethan Gur-esh
> Priority: Minor
> Fix For: Draft 0.61
>
>
> 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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
