Issue 1653: CDR encoding for fixed (interop) Source: (, ) Nature: Uncategorized Issue Severity: Summary: Summary: The CDR encoding rules for fixed-point types are incomplete. In particular, it is not stated which value encodes what digit in each nibble of an octet. It seems sensible to use 0x0 -> "0", 0x1 -> "1", ..., 0x9 -> "9". However, this isn"t stated (but should be). The same comment applies to page 7-10 for DynFixed. I would suggest that rather than repeat the same explanations in the CDR section and the DynFixed section, the spec should use a cross-reference in the DynFixed section that points at the CDR rules. Resolution: Interop RTF has recommended adoption of this resolution. Revised Text: : add to the CDR encoding rules 15.3.2.8 for the fixed type following the last paragraph: " Decimal digits are encoded as hexadecimal values in each half-octet as follows: Decimal digit Half-Octet Value ---------------------------------------- 0 0x0 1 0x1 2 0x2 ... ... 9 0x9 Actions taken: July 9, 1998: received issue February 12, 1999: moved from port rtf to interop August 19, 1999: closed issue Discussion: State the rules in Chapter 15 This issue also asks for a cross-reference from the DynFixed section to page 15-12. However, the DynFixed interface is likely to undergo changes so I'd like to wait until we know where DynFixed is headed before adding a cross-reference. Since Chapter 15 is under control of the Interop RTF recommend the resolution to that RTF. Revised Text: Page 15-12: Add text below following the last para on page 15-12: Decimal digits are encoded as hexadecimal values in each half-octet as follows: Decimal digit Half-Octet Value ---------------------------------------- 0 0x0 1 0x1 2 0x2 ... ... 9 0x9 End of Annotations:===== Return-Path: X-Authentication-Warning: tigger.dstc.edu.au: michi owned process doing -bs Date: Thu, 9 Jul 1998 13:30:36 +1000 (EST) From: Michi Henning To: issues@omg.org, port-rtf@omg.org Subject: CDR encoding for fixed The CDR encoding rules for fixed-point types are incomplete. In particular, it is not stated which value encodes what digit in each nibble of an octet. It seems sensible to use 0x0 -> '0', 0x1 -> '1', ..., 0x9 -> '9'. However, this isn't stated (but should be). The same comment applies to page 7-10 for DynFixed. I would suggest that rather than repeat the same explanations in the CDR section and the DynFixed section, the spec should use a cross-reference in the DynFixed section that points at the CDR rules. Cheers, Michi. Copyright 1998 Michi Henning. All rights reserved. -- Michi Henning +61 7 33654310 DSTC Pty Ltd +61 7 33654311 (fax) University of Qld 4072 michi@dstc.edu.au AUSTRALIA http://www.dstc.edu.au/BDU/staff/michi-henning.html Date: Mon, 1 Feb 1999 08:59:33 +1000 (EST) From: Michi Henning To: orb_revision@omg.org Subject: Proposal for issue 1653 Organization: Triodia Technologies Page 15-12: Add text below following the last para on page 15-12: Decimal digits are encoded as hexadecimal values in each half-octet as follows: Decimal digit Half-Octet Value ---------------------------------------- 0 0x0 1 0x1 2 0x2 ... ... 9 0x9 Issue 1653 also asks for a cross-reference from the DynFixed section to page 15-12. However, the DynFixed interface is likely to undergo changes so I'd like to wait until we know where DynFixed is headed before adding a cross-reference. Cheers, Michi. -- Michi Henning +61 7 3236 1633 Triodia Technologies +61 4 1118 2700 (mobile) PO Box 372 +61 7 3211 0047 (fax) Annerley 4103 michi@triodia.com AUSTRALIA http://www.triodia.com/staff/michi-henning.html