# Functions
CreateProposal creates a DIDCommMsgMap proposal.
New returns introduce service.
WithOOBInvitation is used when introducee wants to provide an out-of-band request.
WithPublicOOBInvitation is used when introducer wants to provide public an out-of-band request.
WithRecipients is used when the introducer does not have a public invitation but he is willing to introduce agents to each other.
WrapWithMetadataPIID wraps message with metadata.
WrapWithMetadataPublicOOBInvitation wraps message with metadata.
# Constants
AckMsgType defines the introduce ack message type.
Introduce protocol name.
IntroduceSpec defines the introduce spec.
ProblemReportMsgType defines the introduce problem-report message type.
ProposalMsgType defines the introduce proposal message type.
RequestMsgType defines the introduce request message type.
ResponseMsgType defines the introduce response message type.
# Structs
Action contains helpful information about action.
Content keeps image data.
ImgAttach represent information about the image.
PleaseIntroduceTo includes all field from To structure also it has Discovered the field which should be provided by help-me-discover protocol.
Proposal defines proposal request.
Recipient keeps information needed for the service 'To' field is needed for the proposal message 'MyDID' and 'TheirDID' fields are needed for sending messages e.g report-problem, proposal, ack etc.
Request is not part of any state machine, it can be sent at any time, and when it is received, the recipient can choose whether or not to honor it in their own way TODO: need to clarify about decorator ~please_ack and problem_report should Request contain those fields? What type it should be for each field?.
Response message that introducee usually sends in response to an introduction proposal.
Service for introduce protocol.
To introducee descriptor keeps information about the introduction e.g introducer wants to introduce Bot to introducee { "name": "Bob" }.
# Interfaces
Provider contains dependencies for the DID exchange protocol and is typically created by using aries.Context().
# Type aliases
DescriptionL10N may contain locale field and key->val pair for translation e.g { "locale": "en", "es": "Donde se toma el MRI; no en el centro"}, where locale field tells that field Description form To struct has en translation.
Opt describes option signature for the Continue function.