taler-docs

Documentation for GNU Taler components, APIs and protocols
Log | Files | Refs | README | LICENSE

commit ca6c47313cb010448a6881a94d183cad1ed94337
parent 2acbc5fa16efecfe0f7136be8d877f03baf0384e
Author: Florian Dold <florian@dold.me>
Date:   Mon, 19 Apr 2021 11:51:37 +0200

fix regex

Diffstat:
Mdesign-documents/018-contract-json.rst | 2+-
1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/design-documents/018-contract-json.rst b/design-documents/018-contract-json.rst @@ -46,7 +46,7 @@ In order to make it easy to get a canonical representation for JSON contract terms, the following restrictions apply: * Member names are restricted: Only strings matching the regular expression - ``0-9A-Z_a-z`` or the literal names ``$forgettable`` or ``$forgotten`` are + ``^[0-9A-Z_a-z]+$`` or the literal names ``$forgettable`` or ``$forgotten`` are allowed. This makes the sorting of object members easier, as RFC8785 requires sorting by UTF-16 code points. * Floating point numbers are forbidden. Numbers must be integers in the range