Outbound Access Control Lists (ACLs)
Outbound ACLs are what provide data record visibility between zones & and adaptors. ACLs are a key component of MDM and are part of what is often referred to as the router. Outbound ACLs can be thought of as permissions on out-bound data. Access
Out-bound data permission is controlled at various levels:. See an example of the data access , below.
| Source of Data | Destination | Priority |
|---|---|---|
| Zone[1] | Zone[2] | 1 |
| Zone[1].Adaptor[x] | Zone[2] | 2 |
| Zone[1].DR[i] | Zone[2] | 3 |
| Zone[1].DR[i].DRproperty[X] | Zone[2] | 4 |
| Zone[1].Adaptor[x].DRproperty[X] | Zone[2] | 5 |
...
- At the
...
- highest prioirty level (Priority 1), Zone[1] can
...
- shut off all outbound data record changes to Zone[2]
...
- . At the lowest priority level (Prioirty 5), Zone[1] can
...
- shut off sharing a single attribute on a single adaptor (that it owns) to Zone[2]
...
- .
...
- Sharing precedence is based on the priority e.g. If Zone[1] has turned off access to Zone[2] (Priority 1), then all other sharing actions are null.
...
- Permissions for each element are based on REST operations GET, PATCH, POST and DELETE. An additional operation is added for PUSH
...
- , where a zone allows another zone to receive real-time changes
...
- . However, it may be determined that GET will scope will include PUSH.
Inbound ACLs
Background
Generally speaking, metadata is mostly to do considerations revolve around (but are not limited to) considerations regarding inbound data in a federated data domain.
Types of Metadata
Metadata includes granular settings for the following :items.
Incoming Filters
A zone or adaptor has the capability of filtering out changes it has scope to.
- "forbid" zone - : Don't GET or accept any updates from a zone
- "forbid" adaptor - : Don't GET or accept any updates from an adaptor
Classes
Adaptor classes
...
(1, 2, 3):
...
Allows a zone or an adaptor in a zone to set a class level on adaptors that are sharing data with them
...
, where 1 is the highest class level and 3 is the lowest class level. For example, if a GET yields three adaptors with the same domain property, and one adaptor is a class 1 and the
...
others are class 2, then the data from the class 1 adaptor is returned in the GET.
Timestamps
Timestamps: Allows a zone or an adaptor to use a key/map of change timestamps and hashes
...
. For example, if a GET yields two adaptors with the same property and both are the same level, we can take the one with the latest timestamp.
Latency (post pilot)
Latency: Allows a zone or an adaptor to use latency times for changes. If a GET request is issued with a reduced-latency parameter, the request will query only the adaptors that are in PLAY or PLAY_RO (play read only) with the lowest latency times.
