X hits on this document

128 views

0 shares

0 downloads

0 comments

28 / 48

London Market Implementation of ACORD DRI Messages and Data

For an accidental re-send, the ACORD DRI message should be rejected at the Repository[Operation]Rs level.

For a deliberate re-send, if the UUID of the ACORD DRI message matches that of a previous ACORD DRI message, the recipient must ensure that the content is identical. If the content is identical, the recipient should reply with the same Repository[Operation]Rs as sent originally. Non identical ACORD DRI message content will be handled out of band.

4.

Recovery procedures

As per trading party interchange agreement.

Document Identification

There are three methods of identifying a document, which reflect the methods within the repository types. These are shown across three versions of a document. Note that some repositories support major and minor releases of a document:-

<DocumentId> Method

GUID format (8-4-4-4-12)

1

GUID format (8-4-4-4-12)

2

Within DRI, the link between versions is defined by using <ParentDocument> with <DocumentRelationTypeCd> set to "Version".  Version 2 would refer back to Version 1

GUID format (8-4-4-4-12)

3

As before, but Version 3 would refer back to Version 2

<DocumentReference> Method

London Market Implementation of ACORD DRI Messages v1.doc

Page 28 of 48

Document info
Document views128
Page views128
Page last viewedSat Dec 10 00:42:07 UTC 2016
Pages48
Paragraphs1101
Words9338

Comments