This scenario details the request of reference data from an Enterprise RDL to an Enterprise RDL in order to determine updates.

Actors

Enterprise RDL Requests reference data set
External RDL Industry or supplier RDL that responds to requests for reference data

Data Content

The request data sent from the Enterprise RDL may be composed of:

  • UUID of reference data set (if known)
  • Version of reference data set
  • Timestamp from which updates have occurred (for incremental responses)

The response data sent from the External RDL is, at a minimum, composed of:

  • UUID, name, and version of the reference data set
  • List of associated taxonomies and types/classes

Data Formats

The data requested by the Enterprise RDL and responded by the External RDL must conform to MIMOSA CCOM BODs.

MIMOSA CCOM Business Object Documents

The following MIMOSA CCOM BODs should be supported:

  • GetTaxonomySet
  • ShowTaxonomySet

Infrastructural Components

ISBM

The communication between all systems occurs via the ISBM using publish-subscribe services.

Implementation Requirements

The Enterprise RDL must implement a client for the ISBM Consumer Request and Channel Management Services. The Enterprise RDL may implement the ISBM Notify Listener Service for message notification.

The External RDL must implement a client for the ISBM Provider Request and Channel Management Services. The External RDL may implement the ISBM Notify Listener Service for message notification.

Suggested Channel/Topic Configuration

A channel should be created for install requests and should conform to the following format:

\Enterprise\Enterprise Subdivision\...

For example:

\Enterprise\TaxonomySet\Get

As outlined in the document ISBM Guidelines, topics should match the message content. Correspondingly, the following topic format should be used:

OIIE:S34:V1.0/StandardXMLSchemaName{:Version}

For example:

OIIE:S34:V1.0/CCOM:GetTaxonomySet:R1.0