X hits on this document

138 views

0 shares

0 downloads

0 comments

9 / 48

London Market Implementation of ACORD DRI Messages and Data

the London Market baseline standards. Note it is possible, on either a bi-lateral party agreement basis or as a whole market, to move Code Set versions without moving to the related ACORD RLC XML standard, i.e. the Code List version and the ACORD RLC standard do not have to be paired.

Terminology

The following is a glossary of terms and phrases commonly used in this document.

Term

Usage

Source

Also known as “Sender”.

Used in UML sequence diagrams. Denotes the repository issuing the document.

Consumer

Also known as “Receiver”.

Used in UML sequence diagrams. Denotes the organisation which receives a document transferred using DRI from a source repository.

Firm

A firm is identified using the ACORD party aggregate, e.g.:

Dun and Bradstreet example

<Party>

<PartyId>urn:duns:123456789</PartyId>

<PartyRole>Cedant</PartyRole>

<PartyName>CedantName</PartyName>

</Party>

Lloyd’s example

<Party>

<PartyId>urn:lloyds:5555</PartyId>

<PartyRole>Insurer</PartyRole>

<PartyName>InsurerName</PartyName>

</Party>

The term ‘organisation’ or ‘trading party’ is also used in place of ‘firm’ in some parts of this document.

Owner

The party responsible for publishing the document in a repository. Also known as the document ‘publisher’.  

Sample ACORD owner party aggregate:

London Market Implementation of ACORD DRI Messages v1.doc

Page 9 of 48

Document info
Document views138
Page views138
Page last viewedMon Jan 16 11:25:59 UTC 2017
Pages48
Paragraphs1101
Words9338

Comments