X hits on this document

133 views

0 shares

0 downloads

0 comments

23 / 48

London Market Implementation of ACORD DRI Messages and Data

7.

Where an ACL is attached to a document, that ACL must be made available to all parties who are able to view the document, i.e. the ACL is ‘passed on’ as received with the document.

8.

Where a member of the ACL for a document, who does not have change rights, requires that a third party (not on the ACL for the document) be granted access to the document, the ACL member can:

Make an out of band request to a member of the ACL with change rights to add, using a RepositoryChangeAttributesRq message, the new party to the ACL for the relevant document, or

Take a copy of the document and become the publisher of the new copy which should then include the third party in the new ACL for the copy.

9.

The operator of any supporting infrastructure will not be able to alter the ACL or other metadata associated with a document unless under instruction from the document owner. Repository operators must maintain a full audit trial.

10.

ACL are not included in a RepositoryCreateFolderRq message. The consumer must grant the owner/creator of a folder access rights to that folder as if they were on the ACL of that folder.

11.

Documents cannot be removed from repositories. Out of band rules will need to be defined by trading partners to cover situations where a document has been loaded in error.

Implementation specific interim requirements

There are two London Market wide initiatives intending to employ ACORD DRI capability using the Insurers’ Market Repository supplied by Xchanging:

THE ACCOUNTING & SETTLEMENT PROJECT

London Market Implementation of ACORD DRI Messages v1.doc

Page 23 of 48

Document info
Document views133
Page views133
Page last viewedSun Dec 11 06:50:40 UTC 2016
Pages48
Paragraphs1101
Words9338

Comments