[OASIS Issue Tracker] Commented: (CMIS-83) Schemas don't allowsetting minvalue/maxValue for Decimal property types

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ http://tools.oasis-open.org/issues/browse/CMIS-83?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=10170#action_10170 ] 

Al Brown commented on CMIS-83:
------------------------------

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.

> 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