Message Types
Last updated
IDS-G
Last updated
There are three Subclasses of the abstract class. Namely the , and . Each subclass itself has subclasses that fulfill a specific purpose in the communication process.
For communication in the IDS, usually the more specific subclasses of the three mentioned ones are used. The message classes relevant for the Connector to Connector communication are listed below. The entire Collection of Messages available in the Information Model can be found .
Client-generated message initiating a communication, motivated by a certain reason and with an answer expected.
Message requesting metadata. If no URI is supplied via the ids:requestedElement field, this messages is treated like a self-description request and the recipient should return its self-description via an ids:DescriptionResponseMessage. However, if a URI is supplied, the Connector should either return metadata about the requested element via an ids:DescriptionResponseMessage, or send an ids:RejectionMessage, e.g., because the element was not found
Parent:
Additional Message Properties:
requestedElement
The element whose metadata is requested.
Implementations:
Message asking for retrieving the specified Artifact inside an ArtifactResponse message.
Additional Message Properties:
requestedArtifact*
References an ids:Artifact.
Implementations:
Message containing a suggested content contract (as offered by the data consumer to the data provider)(which is an instance of ids:ContractRequest).
Additional Message Properties: None
Implementations:
Response messages hold information about the reaction of a recipient to a formerly sent command or event. They must be correlated to this message.
Message containing the metadata, which a Connector previously requested via the ids:DescriptionRequestMessage.
Additional Message Properties: None
Implementations:
Message that follows up a ArtifactRequestMessage and contains the Artifact's data.
Additional Message Properties: None
Implementations:
Message containing a contract, as an instance of ids:ContractAgreement, with resource access modalities on which two parties have agreed.
Additional Message Properties: None
Implementations:
Rejection messages are specialized response messages that notify the sender of a message that processing of this message has failed.
Additional Message Properties:
RejectionReason
Code describing the Rejection Reason, e.g., idsc:NOT_FOUND. (see ids:RejectionReason class)
Implementations:
Message indicating rejection of a contract.
Additional Message Properties:
contractRejectionReason
Human-readable text describing the reason for contract rejection
Implementations:
Event messages are informative and no response is expected by the sender.
Message containing a offered content contract in the associated payload (which is an instance of ContractOffer).
Additional Message Properties: None
Implementations:
Notification that a message has been successfully processed (i.e., not ignored or rejected).
Additional Message Properties: None
Implementations:
Will be added in the future (TODO).
Parent:
Parent:
Parent:
Parent:
Parent:
Parent:
Parent:
Parent:
Parent:
See for information how to work with the Metadata Broker.