{"id":3079,"date":"2019-10-20T15:18:01","date_gmt":"2019-10-20T06:18:01","guid":{"rendered":"https:\/\/www.sambuichi.jp\/?p=3079"},"modified":"2019-10-23T13:34:58","modified_gmt":"2019-10-23T04:34:58","slug":"issues-on-spec-2-1-jis-x-72062020","status":"publish","type":"post","link":"https:\/\/www.sambuichi.jp\/?p=3079&lang=en","title":{"rendered":"Issues on Spec 2.1 JIS X 7206:2020"},"content":{"rendered":"

Views: 103<\/p>

Issues on Spec 2.1
\nSpec 2.1 is NOT edited sufficiently clear and consistently<\/h1>\n

21 October 2019<\/p>\n

SAMBUICHI Nobuyuki
\nXBRL Japan Advisor
\nRepresentative of JIS X 7206:2020 editorial working group
\nISO TC 295 Audit data services
\nHead of delegate Japanese Industrial Standards Committee<\/p>\n

Additional PDF Files for presentation;<\/h3>\n

Today’s presentation slides<\/b>(PDF 724KB)<\/a>
\nJIS X 7206:2020 4.6.3 ~ 4.6.7<\/b> (Translated into English)(PDF 93KB)<\/a><\/p>\n

References<\/h2>\n

IETF RFC 2119
\nIETF (Internet Engineering Task Force). “RFC 2119: Key words for use in RFCs to Indicate Requirement Levels”<\/b>
\nScott Bradner.
\n(See http:\/\/www.ietf.org\/rfc\/rfc2119.txt<\/a>)
\nIEEE
\nIEEE. “IEEE Standard for Floating Point Arithmetic, IEEE Std 754\u2122-2008”<\/b>
\n(See http:\/\/ieeexplore.ieee.org\/xpl\/mostRecentIssue.jsp?punumber=4610933)
\nThis standard is equivalent to following ISO standard
\nISO\/IEC\/IEEE 60559:2011(en)
\nInformation technology \u2014 Microprocessor Systems \u2014 Floating-Point arithmetic<\/b>
\n(see https:\/\/www.iso.org\/obp\/ui\/#iso:std:iso-iec-ieee:60559:ed-1:v1:en<\/a>)
\nISO 80000-1
\nISO 80000-1:2009
\nQuantities and units \u2014 Part 1: General<\/b>
\n(see https:\/\/www.iso.org\/standard\/30669.html<\/a>)<\/p>\n

Errata<\/h2>\n

74. Changed from inferring precision to inferring decimals
\n07 March 2011
\nSection 4.6.6, Section 4.10, Section 5.2.5.2
\n75. Changed rounding descriptions to IEEE standard recommendation
\n31 October 2011
\nSection 4.6.7.1, Section 4.6.7.2<\/p>\n

Ambiguous definition for \u201cround\u201d and \u201ctruncate\u201d<\/h2>\n

PREVIOUS RECOMMENDATION – 2003-12-31 + Corrected Errata – 2008-07-02<\/h3>\n

It is often necessary to round significant figures following a calculation. This is known as rounding. To round a number to n significant figures, discard all digits to the right of the nth place. This step is known as truncation. Then, if the left-most discarded digit is less than 5, leave the nth digit unchanged; if the left-most discarded digit is greater than or equal to 5, add 1 to the nth digit (propagating any carries to digits further to the left according to the normal rules of arithmetic and removing the final 0 if necessary). <\/p>\n

CURRENT Recommendation 31 December 2003 with errata corrections to 20 February 2013<\/h3>\n

It is often necessary to round significant figures following a calculation. This is known as rounding [IEEE] [IEEE 4.3.1 Rounding-direction attributes to nearest, roundTiesToEven]. To round a number to n significant figures, discard all digits to the right of the nth place. This step is known as truncation. Then, if the original number is equally near two truncated numbers, the one with an even nth digit is chosen. <\/p>\n

PROBLEM 1<\/h3>\n

We can not get equally near two truncated numbers with this description.
\nDiscarding all digits to the right of the nth place of original number results a single truncated number.
\nRequirement level is not clearly stated with statement is known as.<\/p>\n

PROBLEM 2<\/h3>\n

IEEE Std. 754 is not general definition for rounding. It defines rounding for representing floating-point in binary format or decimal format in microprocessor. <\/p>\n

Rounding of numbers by JIS X 7206:2020<\/h2>\n

Clear definition \u201cround\u201d and \u201ctruncate\u201d referencing to ISO 80000-1 Annex B<\/p>\n

“Rounding” and “Truncation” MUST be performed as specified in [ISO] (ISO80000-1, Annex B Rounding of numbers). Rounding means replacing the magnitude of an original number by another number called the rounded number, selected from the sequence of integral multiples of a chosen rounding range. [IEEE] (IEEE 4.3 Rounding-direction) lists the rounding-direction attribute affects all computational operations that might be inexact.
\n\u00a0
\nThe first rounding is \u201cRounding\u201d, and its rounding-direction is \u201croundTiesToEven\u201d.
\nIf there is only one integral multiple nearest the original number, then that is accepted as the rounded number.
\nIf there are two successive integral multiples equally near the original number. the even multiple is selected as the rounded number. This rule is of special advantage when treating. for example. series of measurements in such a way that the rounding errors are minimized.
\n\u00a0
\nThe second rounding is \u201cTruncate\u201d, and its rounding-direction is \u201croundTowardZzero\u201d. An integral multiple closest to and no greater in multitude than infinity precise result the original number is accepted as the truncated number.
\n\u00a0
\nRounding in more than one stage by the application of the rules given above may lead to errors. Therefore, the rounding MUST always be carried out in only one step.
\n\u00a0
\nEXAMPLE 12,254 should be rounded to 12,3 and not first to 12,25 and then to 12,2.
\n\u00a0
\nThe rules given above should be used only if no special criteria for the selection of the rounded number MUST be taken into account. For instance, in case where safety requirements or other limits MUST be respected, it is advisable to round only in one direction.<\/p>\n


\n\"\"
\n<\/a><\/p>\n

JIS Z 7206:2010 V-Equal definition<\/h2>\n


\n\"\"
\n<\/a><\/p>\n


\n\"\"
\n<\/a><\/p>\n

Inconsistency between example 11 and example 52<\/h2>\n
<a contextRef=\"c1\" unitRef=\"u1\" precision=\"2\">1559<\/a>\r\n<b contextRef=\"c1\" unitRef=\"u1\" precision=\"3\">984.8<\/b>\r\n<c contextRef=\"c1\" unitRef=\"u1\" decimals=\"1\">582.334973<\/c><\/pre>\n
4.6.4 The\u00a0@precision\u00a0attribute (optional)<\/h3>\n
TRUNCATE
\nIf a numeric fact has a\u00a0@precision\u00a0attribute that has the value “n” then it is correct to “n” significant figures (see\u00a0Section 4.6.1\u00a0for the normative definition of ‘correct to “n” significant figures\u2019).
\nAn application\u00a0SHOULD\u00a0ignore (i.e. replace with zeroes) any digits after the first “n” decimal digits, counting from the left, starting at the first non-zero digit in the lexical representation of any number for which the value of precision is specified or inferred to be\u00a0n.<\/p>\n
Example 52. Calculations involving decimals and precision<\/h3>\n
ROUND
\nSuppose that the numeric item a is a summation for numeric items b and c (with weight 1.0) and there exists a context with id ‘c1’ and unit with id ‘u1’ in the instance so that the summation binds.
\nTo perform the calculation, first round 984.8 to precision 3 to give 985 and then round 582.334973 to the inferred precision 4 to give 582.3 resulting in a total of 1567.3. The total is then equal to the summation item after rounding to precision 2 (the precision of the summation item a) at 1600, so that this calculation is consistent.<\/p>\n
Consuming application are required to handle inconsistent ways.<\/h4>\n
The rounding shall always be carried out in only one step.<\/h4>\n
Modify example 52 to carry out rounding in single step<\/h2>\n
Example 52. Calculations involving decimals and precision<\/h3>\n
Suppose that the numeric item a is a summation for numeric items b and c (with weight 1.0) and there exists a context with id ‘c1’ and unit with id ‘u1’ in the instance so that the summation binds.
\nTo perform the calculation, first round 984.8 to precision 3 to give 985 and then round 582.334973 to the inferred precision 4 to give 582.3 resulting in a total of 1567.3. The total is then equal to the summation item after rounding to precision 2 (the precision of the summation item a) at 1600, so that this calculation is consistent.<\/p>\n
JIS Z 7206:2020<\/h3>\n
Suppose that the numeric item a is a summation for numeric items b and c (with weight 1.0) and there exists a context with id ‘c1’ and unit with id ‘u1’ in the instance so that the summation binds.
\nTo perform the calculation, first add 984.8 and 582.334 973 to get 1567.13497, then check if the total is v-equal. The inferred decimals of the summation item a is -2 and 1559 correct to -2 decimal places is1600. The total 1567.13497 correct to -2 decimal places is also1600. These two values are not only both C-Equal and U-equal but also V-Equal, so that this calculation is consistent.<\/p>\n
The rounding shall always be carried out in only one step. <\/h4>\n
The final V-Equal test step.<\/h4>\n
Calculation based on 4.6.4 vs JIS<\/h2>\n
<\/a>\"\"<\/a><\/p>\n
Rounding in more than one stage by the application may lead to errors. <\/h4>\n
Therefore, the rounding MUST always be carried out in only one step for V-Equal test.<\/h4>\n
\"\"<\/a><\/p>\n
IEEE Standard for Floating-Point Arithmetic<\/h1>\n
4. Attributes and rounding<\/h2>\n
4.1 Attribute specification<\/h3>\n
An attribute is logically associated with a program block to modify its numerical and exception semantics. A user can specify a constant value for an attribute parameter. Some attributes have the effect of an implicit parameter to most individual operations of this standard; language standards shall specify \u2015 rounding-direction attributes (see 4.3) and should specify \u2015 alternate exception handling attributes (see Clause 8). Other attributes change the mapping of language expressions into operations of this standard; language standards that permit more than one such mapping should provide support for: \u2015 preferredWidth attributes (see 10.3) \u2015 value-changing optimization attributes (see 10.4) \u2015 reproducibility attributes (see Clause 11). For attribute specification, the implementation shall provide language-defined means, such as compiler directives, to specify a constant value for the attribute parameter for the operations in a block; the scope of the attribute value is the block with which it is associated. Language standards shall provide for constant specification of the default and each specific value of the attribute.<\/p>\n
4.2 Dynamic modes for attributes<\/h3>\n
Attributes in this standard shall be supported with the constant specification of 4.1. Particularly to support debugging, language standards should also support dynamic-mode specification of attributes. With dynamic-mode specification, a user can specify that the attribute parameter assumes the value of a dynamic-mode variable whose value might not be known until program execution. This standard does not specify the underlying implementation mechanisms for constant attributes or dynamic modes. For dynamic-mode specification, the implementation shall provide language-defined means to specify that the attribute parameter assumes the value of a dynamic-mode variable for the operations within the scope of the dynamic-mode specification in a block. The implementation initializes a dynamic-mode variable to the default value for the dynamic mode. Within its language-defined (dynamic) scope, changes to the value of a dynamic-mode variable are under the control of the user via the operations in 9.3.1 and 9.3.2. The following aspects of dynamic-mode variables are language-defined; language standards may explicitly defer the definitions to implementations: \u2015 The precedence of static attribute specifications and dynamic-mode assignments. \u2015 The effect of changing the value of the dynamic-mode variable in an asynchronous event, such as in another thread or signal handler. \u2015 Whether the value of the dynamic-mode variable can be determined by non-programmatic means, such as a debugger. NOTE\u2014A constant value for an attribute can be specified and meet the requirements of 4.1 by a dynamic mode specification with appropriate scope of that constant value. <\/p>\n
4.3 Rounding-direction attributes<\/h3>\n
Rounding takes a number regarded as infinitely precise and, if necessary, modifies it to fit in the destination\u2019s format while signaling the inexact exception, underflow, or overflow when appropriate (see Clause 7). Except where stated otherwise, every operation shall be performed as if it first produced an intermediate result correct to infinite precision and with unbounded range, and then rounded that result according to one of the attributes in this clause. Except where stated otherwise, the rounding-direction attribute affects all computational operations that might be inexact. Inexact numeric floating-point results always have the same sign as the unrounded result. The rounding-direction attribute affects the signs of exact zero sums (see 6.3), and also affects the thresholds beyond which overflow (see 7.4) and underflow (see 7.5) are signaled. Implementations supporting both decimal and binary formats shall provide separate rounding-direction attributes for binary and decimal, the binary rounding direction and the decimal rounding direction. Operations returning results in a floating-point format shall use the rounding-direction attribute associated with the radix of the results. Operations converting from an operand in a floating-point format to a result in integer format or to an external character sequence (see 5.8 and 5.12) shall use the rounding-direction attribute associated with the radix of the operand. NaNs are not rounded (but see 6.2.3).<\/p>\n
4.3.1 Rounding-direction attributes to nearest<\/h4>\n
In the following two rounding-direction attributes, an infinitely precise result with magnitude at least bemax<\/sup> \u00d7(b\u2212\u00bdb1\u2212p<\/sup> ) shall round to \u221e with no change in sign; here emax and p are determined by the destination format (see 3.3). With:
\n\u2015 roundTiesToEven<\/b>, the floating-point number nearest to the infinitely precise result shall be delivered; if the two nearest floating-point numbers bracketing an unrepresentable infinitely precise result are equally near, the one with an even least significant digit shall be delivered; if that is not possible, the one larger in magnitude shall be delivered (this can happen for one-digit precision, possible with convertToDecimalCharacter for example, as when rounding 9.5 to one digit in which case both 9 and 1\u00d7101 have odd significands)
\n\u2015 roundTiesToAway<\/b>, the floating-point number nearest to the infinitely precise result shall be delivered; if the two nearest floating-point numbers bracketing an unrepresentable infinitely precise result are equally near, the one with larger magnitude shall be delivered.<\/p>\n
4.3.2 Directed rounding attributes<\/h3>\n
Three other user-selectable rounding-direction attributes are defined, the directed rounding attributes roundTowardPositive, roundTowardNegative, and roundTowardZero. With:
\n\u2015 roundTowardPositive<\/b>, the result shall be the format\u2019s floating-point number (possibly +\u221e) closest to and no less than the infinitely precise result
\n\u2015 roundTowardNegative<\/b>, the result shall be the format\u2019s floating-point number (possibly \u2212\u221e) closest to and no greater than the infinitely precise result
\n\u2015 roundTowardZero<\/b>, the result shall be the format\u2019s floating-point number closest to and no greater in magnitude than the infinitely precise result.
\n\u00a0<\/p>\n
4.3.3 Rounding attribute requirements<\/h3>\n
An implementation of this standard shall provide roundTiesToEven and the three directed rounding attributes. A decimal format implementation of this standard shall provide roundTiesToAway as a user selectable rounding-direction attribute. The rounding attribute roundTiesToAway is not required for a binary format implementation. The roundTiesToEven rounding-direction attribute shall be the default rounding-direction attribute for results in binary formats. The default rounding-direction attribute for results in decimal formats is language-defined but should be roundTiesToEven.<\/p>\n
\"\"<\/a><\/p>\n
ISO 80000-1:2009(E)<\/h1>\n
Quantities and units – Part 1 General<\/h2>\n
Annex B<\/h3>\n
(normative)<\/h3>\n
Rounding of numbers<\/p>\n
\n
B.1 Rounding means replacing the magnitude of a given number by another number called the rounded number, selected from the sequence of integral multiples of a chosen rounding range.<\/h4>\n
EXAMPLE 1<\/p>\n\n\n\n\n
rounding range:<\/td>\n0,1<\/td>\n<\/tr>\n
integral multiple:<\/td>\n2,1; 12,2; 12,3; 12,4; etc.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
EXAMPLE 2<\/p>\n\n\n\n\n
rounding range:<\/td>\n10<\/td>\n<\/tr>\n
integral multiple:<\/td>\n1 210; 1 220; 1 230; 1 240; etc.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
B.2 If there is only one integral multiple nearest the given number, then that is accepted as the rounded number.<\/h4>\n
EXAMPLE 3<\/p>\n\n\n\n\n\n\n\n
rounding range:<\/d><\/p>\n0,1<\/td>\n<\/tr>\n
given number<\/d><\/p>\nrounded number<\/td>\n<\/tr>\n
12,233<\/td>\n12,2<\/td>\n<\/tr>\n
12,251<\/td>\n12,3<\/td>\n<\/tr>\n
12,275<\/td>\n12,3<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
EXAMPLE 4<\/p>\n\n\n\n\n\n\n\n
rounding range:<\/d><\/p>\n10<\/td>\n<\/tr>\n
given number<\/d><\/p>\nrounded number<\/td>\n<\/tr>\n
1 223,3<\/td>\n1 220<\/td>\n<\/tr>\n
1 225,1<\/td>\n1 230<\/td>\n<\/tr>\n
1 227,5<\/td>\n1 230<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
B.3 If there are two successive integral multiples equally near the given number, two different rules are in use.<\/h4>\n
Rule A: The even multiple is selected as the rounded number.
\nEXAMPLE 5<\/p>\n\n\n\n\n\n\n
rounding range:<\/td>\n0,1<\/td>\n<\/tr>\n
given number<\/td>\nrounded number<\/td>\n<\/tr>\n
12,25<\/td>\n12,2<\/td>\n<\/tr>\n
12,35<\/td>\n12,4<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
EXAMPLE 6<\/p>\n\n\n\n\n\n\n
rounding range:<\/td>\n10<\/td>\n<\/tr>\n
given number<\/td>\nrounded number<\/td>\n<\/tr>\n
1 225,0<\/td>\n1 220<\/td>\n<\/tr>\n
1 235,0<\/td>\n1 240<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
Rule B: The greater in multitude is selected as the rounded number.<\/p>\n
EXAMPLE 7<\/p>\n\n\n\n\n\n\n\n\n
rounding range:<\/td>\n0,1<\/td>\n<\/tr>\n
given number<\/td>\nrounded number<\/td>\n<\/tr>\n
12,25<\/td>\n12,3<\/td>\n<\/tr>\n
12,35<\/td>\n12,4<\/td>\n<\/tr>\n
-12,25<\/td>\n-12,3<\/td>\n<\/tr>\n
-12,35<\/td>\n-12,4<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
EXAMPLE 8<\/p>\n\n\n\n\n\n\n\n\n
rounding range:<\/td>\n10<\/td>\n<\/tr>\n
given number<\/td>\nrounded number<\/td>\n<\/tr>\n
1 225,0<\/td>\n1 230<\/td>\n<\/tr>\n
1 235,0<\/td>\n1 240<\/td>\n<\/tr>\n
-1 225,0<\/td>\n-1 230<\/td>\n<\/tr>\n
-1 235,0<\/td>\n-1 240<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
Rule A is generally preferable and of special advantage when treating, for example, series of measurements in such a way that the rounding errors are minimized.
\nRule B is sometimes used in computers.<\/p>\n
B.4 Rounding in more than one stage by the application of the rules given above may lead to errors. Therefore, the rounding shall always be carried out in only one step.<\/h4>\n
EXAMPLE 12,254 should be rounded to 12,3 and not first to 12,25 and then to 12,2.<\/p>\n
B.5 The rules given above should be used only if no special criteria for the selection of the rounded number have to be taken into account. For instance, in case where safety requirements or other limits have to be respected, it is advisable to round only in one direction.<\/h4>\n
B.6 The rounding range should always be indicated.<\/h4>\n","protected":false},"excerpt":{"rendered":"
Views: 103Issues on Spec 2.1 Spec 2.1 is NOT edited sufficiently clear and consistently 21 October 2019 SAMBUI […]<\/p>\n","protected":false},"author":2,"featured_media":3067,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[17],"tags":[],"_links":{"self":[{"href":"https:\/\/www.sambuichi.jp\/index.php?rest_route=\/wp\/v2\/posts\/3079"}],"collection":[{"href":"https:\/\/www.sambuichi.jp\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.sambuichi.jp\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.sambuichi.jp\/index.php?rest_route=\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.sambuichi.jp\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=3079"}],"version-history":[{"count":26,"href":"https:\/\/www.sambuichi.jp\/index.php?rest_route=\/wp\/v2\/posts\/3079\/revisions"}],"predecessor-version":[{"id":3149,"href":"https:\/\/www.sambuichi.jp\/index.php?rest_route=\/wp\/v2\/posts\/3079\/revisions\/3149"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.sambuichi.jp\/index.php?rest_route=\/wp\/v2\/media\/3067"}],"wp:attachment":[{"href":"https:\/\/www.sambuichi.jp\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=3079"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.sambuichi.jp\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=3079"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.sambuichi.jp\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=3079"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}