Focusing on the generalization of concepts, functionality, and overall processes involved in the creation of a secure 'network of trusted data' , the IDS-RAM resides at a higher abstraction level than common architecture models of concrete software solutions do. The document provides an overview and dedicated architecture specifications.
When reading the IDS RAM, one can not be sure which kind of broker is meant. It doesn't help the reader to form an understanding of the metadata broker. If the broker is a metadata broker, it should be called so (NOT broker, or data broker).
Chapter 3.1.1 Roles in the IDS introduces the app broker, service broker and data broker. Rename data broker to metadata broker and refer to the broker services accordingly.
BTW other brokers are not explained overall. App broker = App Store, service broker = mentioned once.
When reading the IDS RAM, one can not be sure which kind of broker is meant. It doesn't help the reader to form an understanding of the metadata broker. If the broker is a metadata broker, it should be called so (NOT broker, or data broker).
Chapter 3.1.1 Roles in the IDS introduces the app broker, service broker and data broker. Rename data broker to metadata broker and refer to the broker services accordingly. BTW other brokers are not explained overall. App broker = App Store, service broker = mentioned once.