diff --git a/groups/bal/baljsn/doc/baljsn.txt b/groups/bal/baljsn/doc/baljsn.txt index 2fe8f50356..c6e4fadebd 100644 --- a/groups/bal/baljsn/doc/baljsn.txt +++ b/groups/bal/baljsn/doc/baljsn.txt @@ -95,23 +95,23 @@ BDEM_VOID N/A N/A null Encoding error BDEM_BOOL boolean bool true/false -BDEM_CHAR byte char number +BDEM_CHAR byte char number/string -BDEM_SHORT short short number +BDEM_SHORT short short number/string - unsignedByte unsigned char number + unsignedByte unsigned char number/string -BDEM_INT int int number +BDEM_INT int int number/string - unsignedShort unsigned short number + unsignedShort unsigned short number/string -BDEM_INT64 integer Int64 number +BDEM_INT64 integer Int64 number/string - long Int64 number + long Int64 number/string - unsignedInt unsigned int number + unsignedInt unsigned int number/string - unsignedLong unsigned Uint64 number + unsignedLong unsigned Uint64 number/string BDEM_FLOAT float float number/string @@ -147,7 +147,9 @@ BDEM_CHOICE choice bcem_Aggregate object BDEM_CHOICE_ARRAY maxOccurs > 1 bcem_Aggregate array of objs -BDEM_INT/STRING enumeration C++ enumeration string +BDEM_INT enumeration C++ enumeration string/number "" + +BDEM_STRING enumeration C++ enumeration string BDEM_* minOccurs = 0 NullableValue null .. @@ -161,6 +163,12 @@ nullable scalar types (specified via the 'xs:nillable' attribute) are encoded similar to their vector of non-nullable scalar types except that their elements could also be specified as 'null'. +* Integral types are always encoded in the format and int-valued +enumerations are always encoded in the "" format, but during decoding +both of these formats are supported for both of these categories of types. +This flexibility applies to all integral types, including ones that do not +support an enumeration constraint. + The format grammar specified below uses the Extended BNF notation (except that ',' is not used for concatenation to enhance readability). A quick reference of EBNF is provided below (refer here for more details):