Skip to content

base64 usage in payload values #2

@sake

Description

@sake

The payload fields in the envelope types mention in the description of the payload type that the type is "Base64 encoded json payload". This is also reflected in the examples in the message type. However there is no formal specification in the schema which makes the defined schema incompatible with the examples.

This leads to the situation, that

  1. the schema can not be used to generate an implementation and to validate the correctness of the messages, or
  2. the examples suggest to implement a variant which is not according to the specification.

To be honest I don't see any reason to encode the payload objects as base64. It furthermore complicates the parsing process unnecessarily.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions