...
- No data of Match-Connect participants is kept after retrieval by the receiving hub
- No data (payload) of Match-Connect messages is changed
- Ensure integrity and traceability of the messages exchanged (for details see Chapter 6.0).
The Match-Connect system acts as a central broker of information exchange between registries participating in the Match-Connect ecosystem, also called the central hub from here on. The central hub bears the responsibility to:
...
In performing these duties, the Match-Connect system will inspect the contents of messages to determine who to route messages to and to perform basic validation. This content is not intended to be reviewed by administrators of the system except in cases where this is required to analyze message failures or data synchronization problems. The central system will never modify original message contents but additional meta information "blocks" will be added to ensure the receiving registry is aware of:
- Which registry sent the information
- What type of information is contained
- A message identifier
- A timestamp
- Any failed validations detected by the Match-Connect system
- A sequence number to know if any message is missing.
...
| Anchor | ||||
|---|---|---|---|---|
|
| Term | Definition | Aliases / Abbreviations |
|---|---|---|
| Match-Connect | The APIs and central system of the WMDA used for facilitation of the search and procurement process amongst registries. This includes the infrastructure for routing of information between participating registries and associated business logic as defined in the Match-Connect Semantics. APIs contained within Match-Connect are:
| Central Hub MC |
| Search & Match Service |