NSD’s trade repository messages specifications

Current specification

ResponseMessage

A type refining the generic message content model to make it specific to response messages.

FieldTypeDescriptionPrint form titleFFSM titlePropertiesConditions
headerResponseMessag​eHeaderA type refining the generic message header to make it specific to response messages.0-1, mre, nfr
validationValidationA list of validation sets the sender asserts the document is valid with respect to. This field is never filled for NSD messages. 0-∞, ncf
parentCorrelat​ionIdCorrelationIdA reference to message which register a master agreement. Should be filled in messages for trade registration when they are being send together with master agreement registration message. Related document form identifier0-1, nfr
correlationIdCorrelationIdA qualified identifier used to correlate between messages. For NSD messages the format is [Sender identifier]-[Year]-[Message ID]. Messages chain identifier0-2, mre, nfrIn NSD repository messages only one correlationId element must be filled.
sequenceNumberxsd:positiveIn​tegerA numeric value that can be used to order messages with the same correlation identifier from the same sender. 0-1, ncfThis is not used in messages to the repository.
onBehalfOfOnBehalfOfIndicates which party (or parties) (and accounts) a trade or event is being processed for. Normally there will only be a maximum of 2 parties, but in the case of a novation there could be a transferor, transferee, remaining party, and other remaining party. Except for this case, there should be no more than two onABehalfOf references in a message. Message on behalf of.0-4, ncfThis model is used in messages sent for registration by the repository only.
ResponseMessage