taler-docs

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

commit 27fad4449371fdec5d64fde0bb52176bd6f99810
parent 14938897502bff6b5946bb7e210cd403e0da9eb8
Author: Christian Grothoff <grothoff@gnunet.org>
Date:   Sun, 21 May 2023 19:57:29 +0200

restructure documentation some more

Diffstat:
Mcore/api-common.rst | 9+++++----
1 file changed, 5 insertions(+), 4 deletions(-)

diff --git a/core/api-common.rst b/core/api-common.rst @@ -19,8 +19,8 @@ .. _http-common: ================================= -Common Taler HTTP API Conventions -================================= +Conventions for Taler RESTful APIs +================================== ------------------------- @@ -206,7 +206,7 @@ In C, the respective enumeration is the ``enum TALER_ErrorCode``. Developers may have to re-run ``bootstrap`` and/or update their Git submodules to ensure that they have the lastest GANA registry. - + .. _encodings-ref: ---------------- @@ -233,6 +233,7 @@ resulting encoding. Hash codes ^^^^^^^^^^ + Hash codes are strings representing base32 encoding of the respective hashed data. See `base32`_. @@ -466,7 +467,6 @@ Fetch params }; - Keys ^^^^ @@ -942,6 +942,7 @@ uses 512-bit hash codes (64 bytes). Signatures ^^^^^^^^^^ + Any piece of signed data, complies to the abstract data structure given below. .. sourcecode:: c