X hits on this document

107 views

0 shares

0 downloads

0 comments

29 / 48

London Market Implementation of ACORD DRI Messages and Data

200

1.0

300

1.1

As before, but Version 1.1 would refer back to Version 1.0

400

2.0

As before, but Version 2.0 would refer back to Version 1.1

<DocumentReference> & <DocumentVersion> Method

500

1

500

2

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

500

3

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

To cover all possibilities, all three data elements however populated must be preserved by the receiver as the unique identity of the document.  It is acknowledged that in the first two cases, <DocumentVersion> is informational rather than part of the unique identity of the document.

When presenting the identity back to the "Owner" of the document, e.g. in a RepositoryDownloadRq, the requester can define a generic process by passing all three data elements as populated.  Upon receipt, the Owner will “know” how to process them, according to the needs of his own repository.

Time Outs

SOAP messaging framework time-out (t1) and file sizes

London Market Implementation of ACORD DRI Messages v1.doc

Page 29 of 48

Document info
Document views107
Page views107
Page last viewedSun Dec 04 15:32:14 UTC 2016
Pages48
Paragraphs1101
Words9338

Comments