X hits on this document

142 views

0 shares

0 downloads

0 comments

19 / 48

London Market Implementation of ACORD DRI Messages and Data

Ancillary

RepositoryCreateFolder

The RepositoryCreateFolder operation allows the consumer to prepare a document placeholder in the target repository using DRI.

A folder is uniquely identified with one of two exclusive methods:

1.

a globally unique id <FolderId>, or

2.

an Owner’s repository reference <FolderReference>

Only the owner of a folder can create a sub-folder within that folder. If a consumer wishes to create a sub-folder within a folder for which they are not the owner, they must go back to the folder owner.

Folder Identifiers

The source should store the reference sent by the owner next to their own reference, as a shared folder identifier. Uniqueness will be qualified by the folder owner/creator.

A Repository Operator should use the owner reference when communicating to other parties for consistency of folder identification.

<FolderReference> naming conventions will be governed by the usage contract of the target repository.

RepositoryChangeAttributes

The ACORD DRI standard allows for modification of the characteristics of a folder or document by parties who have appropriate access to do so.  Within the London Market the RepositoryChangeAttributes operation can add or change folder or document metadata.

Folder or document identifiers cannot be modified using the RepositoryChangeAttributes operation. The ACORD DRI standard utilises the folder or document identifiers (see 3.8 Time Outs) in a

London Market Implementation of ACORD DRI Messages v1.doc

Page 19 of 48

Document info
Document views142
Page views142
Page last viewedTue Jan 17 13:17:43 UTC 2017
Pages48
Paragraphs1101
Words9338

Comments