[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Commented: (CMIS-544) 3.2.2.2getRepositoryInfo outputs, cmisVersionSupported should be a String
[ http://tools.oasis-open.org/issues/browse/CMIS-544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17354#action_17354 ]
Al Brown commented on CMIS-544:
-------------------------------
JIRA Cleanup
> 3.2.2.2 getRepositoryInfo outputs, cmisVersionSupported should be a String
> --------------------------------------------------------------------------
>
> Key: CMIS-544
> URL: http://tools.oasis-open.org/issues/browse/CMIS-544
> Project: OASIS Content Management Interoperability Services (CMIS) TC
> Issue Type: Bug
> Components: Domain Model
> Reporter: Ryan McVeigh
> Assignee: Ethan Gur-esh
> Fix For: Committee Draft 04
>
>
> "Decimal cmisVersionSupported: A string that indicates..." How do you fit a string into a Decimal type? Since it is decimal, what precision is required? That is, if cmisVersionSupported is 0.63000000000000000444089209850062616169452667236328125, can you say that you support 0.63? This is significant as most decimal numbers can not be represented exactly in floating point representation. This is also why most products represent version numbers as strings.
> * Note - that long number is the result of Java running System.out.println(new BigDecimal(0.63));
> We could argue that the version is specified as something like x.y but not all values of x.y are representable exactly as floating point numbers in binary.
> 0.63, for example, can not be represented exactly in single-presision (32 bit) IEEE-754 floating point. It has to be converted to a binary fraction, and it just can't be done with only 32 bits.
> If the TC is going to guarantee that it will always generate specification numbers that are exactly representable in some precision floating point representation, then it should specify the precision is it using, so clients and repositories and future bindings can do the appropriate thing.
> --
> It seems easier to just use a String.
--
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
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]