| Table of Contents |
|---|
<title>
<Narrative>
<Swagger - API reference>
<temporary - document any differences needing implementation in swagger>
<Specific rules / expectations>
6.1 Embedded Meta block
The additional meta-information "blocks" are added to ensure the receiving registry is aware of:
- What registry sent the information (sender)
- What type of information is contained
- A message identifier
- A timestamp
- Any failed validations detected by the Match Connect system
metaInformation{
| Field name | format | Description |
|---|---|---|
| messageId | string($uuid) | ID of the originally sent message |
| sentAtUtc | string($date-time) | Server-supplied timestamp showing UTC time of Message delivery to recipient's inbox queue. |
| sender | string maximum: 9999 minimum: 0 maxLength: 4 minLength: 4 example: 5678 | 4 digit ION of the sender |
| messageType | string | To be designed and described. The idea is to help registry's MC admin to analyze possible issues reported in validationDetails field. AM: I think this is an excessive information, as messageId should be sufficient. |
| validationDetails | To be designed and described. The idea is to supply the concerns of the central hub validation system that are acceptable but require attention of the receiving registry. |
}
6.2 Embedded Address block
...