Skip to content
This repository has been archived by the owner on Dec 6, 2022. It is now read-only.

How to construct valid messages according to a protocol version? #14

Open
OR13 opened this issue Aug 16, 2019 · 1 comment
Open

How to construct valid messages according to a protocol version? #14

OR13 opened this issue Aug 16, 2019 · 1 comment

Comments

@OR13
Copy link

OR13 commented Aug 16, 2019

The readme shows:

  const message = JSON.stringify({
        "@type": "did:example:1234567890;spec/test",
        data: "I AM A SIGNED MESSAGE"
    })

I would expect this library to assist implementers in crafting messages that are formatted correctly, in addition to packing / unpacking.

The code used to construct a valid message, is undoubtably in other repo, can establish a clearer understanding of the message format this library should be used with?

@OR13 OR13 changed the title Message Validation How to construct valid messages according to a protocol version? Aug 16, 2019
@kdenhartog
Copy link
Contributor

The message format isn't a concern of this layer. As long as it's a string, this library can be used to encrypt the message.

However, with that said, "DIDComm semantic messages" are assumed to be the common messages used in this format. This is the reason that I included some with the format of DIDComm semantic messages and some without.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants