Channels
Last updated
Last updated
Messages between participating gateways are structured and organized in distinct channels corresponding to specific use cases or business processes.
Channels are created and managed in the Client Gateway by Admin Users, and defined by the following properties:
Format: Messaging (individual messages with payload structured as JSON objects) or File Transfer (bulk data transfer via .csv or .xml files)
Type: Publish (send) or Subscribe (receive)
Namespace: A unique, non-numeric name to identify the channel
Settings: The following settings can be enable/disabled when creating a channel:
Use Anonymous Channel: Anonymizes the identities of recipients (for Publish channels) or senders (for Subscribe channels)
Payload Encryption: Encrypts the payload of messages using the public key of the Sender's client gateway and private key of the recipient's gateway.
Form Builder: Provides a dynamic form based on the topic schema for users to manually send messages in the gateway UI.
Restrictions: A list of specific identities or roles who are authorized to receive messages (for Publish channels) or send messages (for Subscribe channels); restrictions can be defined by specific identities, or by role.
Topics: One or more standardized data schemas.
In order to access certain channels and gain permissions to send and/or receive specific message types, participants must that reflect their role within the market (or use case), using credentials attached to their self-sovereign identity. Credentials are granted by a platform governing body and determine the ability to send messages to other participants using channels (what messages are sent and received) and topics (data schemas that define the payload of a message).