Engine API: fix wording around DATA and QUANTITY
This commit is contained in:
parent
237689dd29
commit
eb64437ea6
|
@ -134,9 +134,9 @@ $ curl https://localhost:8550 \
|
|||
|
||||
## Structures
|
||||
|
||||
Encoding of values which have `DATA` type **MUST** be encoded as a hexadecimal string with a `0x` prefix matching the regular expression `^0x(?:[a-fA-F0-9]{2})*$`.
|
||||
Values of a field of `DATA` type **MUST** be encoded as a hexadecimal string with a `0x` prefix matching the regular expression `^0x(?:[a-fA-F0-9]{2})*$`.
|
||||
|
||||
Encoding of values which have `QUANTITY` type **MUST** be encoded as a hexadecimal string with a `0x` prefix and the leading 0s stripped (except for the case of encoding the value `0`) matching the regular expression `^0x(?:0|(?:[a-fA-F1-9][a-fA-F0-9]*))$`.
|
||||
Values of a field of `QUANTITY` type **MUST** be encoded as a hexadecimal string with a `0x` prefix and the leading 0s stripped (except for the case of encoding the value `0`) matching the regular expression `^0x(?:0|(?:[a-fA-F1-9][a-fA-F0-9]*))$`.
|
||||
|
||||
*Note:* Byte order of encoded value having `QUANTITY` type is big-endian.
|
||||
|
||||
|
|
Loading…
Reference in New Issue