The current text for the attachments attribute reads:
attachments - REQUIRED for OOB usage. An array of attachments that will contain the invitation messages in order of preference that the receiver can use in responding to the message...
After some discussion with Sam, it seems the intent for OOB invitations is that instead of always having an attachment with an explicit message or set of messages, it should be possible to just specify a goal code that initiates some flow of messages. To support that use case, attachments should be marked as "OPTIONAL" rather than "REQUIRED."
The current text for the
attachments
attribute reads:After some discussion with Sam, it seems the intent for OOB invitations is that instead of always having an attachment with an explicit message or set of messages, it should be possible to just specify a goal code that initiates some flow of messages. To support that use case, attachments should be marked as "OPTIONAL" rather than "REQUIRED."
cc @TelegramSam