RE: [sdo] NEW ISSUE: Mapping of signed and unsigned integer values

["Radu Preotiuc-Pietro" <radu.preotiuc-pietro@oracle.com>]

Hi Bryan,

 

As far as the mapping of XSD byte to SDO Byte, SDO 2.1.1 will fix this and make SDO Byte a signed value.

 

Radu

---

From: Bryan Aupperle [mailto:aupperle@us.ibm.com]
Sent: Thursday, August 21, 2008 10:19 AM
To: sdo@lists.oasis-open.org
Subject: [sdo] NEW ISSUE: Mapping of signed and unsigned integer values

Target: Core specification WD-01 Section 6.1, 7.4, and 8.1
            Java specification WD-02 Section 7.1, and 8.3?
            C++ specification WD-02 Section 8.1

Description:

Currently the SDO type Byte is defined as an 8-bit unsigned integer, while Short, Int, and Long are 16, 32 and 64 bit signed integers respectively
Why are the not any SDO types for unsigned 16, 32, and 64 bit integers (which are valid XSD types)?  Or for that matter an 8-bit signed integer (which is what XSD:byte is)?

A related concern the mapping of XSD:byte to SDO Byte appears to be an error since -123 would be a valid value in the XML document but not in the SDO instance.

Proposal:

Bryan Aupperle, Ph.D.
STSM, WebSphere Enterprise Platform Software Solution Architect

Research Triangle Park,  NC
+1 919-254-7508 (T/L 444-7508)
Internet Address: aupperle@us.ibm.com