|home||specifications||WIJIS URIs||gateway||CDCL||GJXDM example||warrants/po exchange||wijis articles|
A CDCL goal is to respect a separation of duties (aka division of responsibility), which promotes optimizing security. Of course, security is critical in ensuring the entire CDCL landscape of components works accurately and is vulnerable to as few risks as possible. As such, CDCL defines a small quantity of "communities", each one surrounding a major component in the landscape. Certainly, nothing within CDCL's technical design prohibits an individual from membership in more than one community, if that were deemed necessary.
See a sequence diagram of the interactive steps between and among communities.
Rulesheet authors write disclosure control policy in CDCL Authoring Form.
Rulesheet authors and the operators of Rulesheet Repositories must cooperate with each other and with the operators of Gatepoints and of Stakeholder Directories in order to achieve a fully inter-operable landscape of CDCL components. Rulesheet authors and the operators of Rulesheet Repositories are responsible for the controlled management of rulesheet revisions and the publication of rulesheets for potential run-time evaluation and enforcement.
Stakeholder custodians and primary custodians have legitimate interest in the policy-compliant disclosure of information.
Stakeholder custodians and primary custodians, along with stakeholder directory operators, cooperate with Gatepoint operators to ensure the appropriate Gatepoints are configured to reference appropriate stakeholder directories. Each stakeholder directory is, in itself, a community distinct from other directories. This is the foremost starting point by which a Gatepoint begins its policy-gathering process called rulesheet collation. Everything hinges on this point. Therefore, it is imperative that the community of custodians (called stakeholder community throughout this website) exercise due diligence in govering community membership.
A CDCL Gatepoint is responsible for the automated run-time evaluation and enforcement of disclosure control policy.
Gatepoint operators have sole control over configuring behavior of their Gatepoints. However, some authors may draft policy containing dependencies on third party services for purposes of delegated decision making. Additionally, some entities engaged in information exchanges, who become Gatepoint clients, may have expectations on involving certain stakeholder communities during disclosure control for documents they submit to Gatepoints. In all these cases, the Gatepoint operators will need to cooperate with these parties in order to achieve a mutually-agreeable situation between their expectations/dependencies and the Gatepoint's configuration.
Registries house ancillary data needed by members of other communities in order to make citations or references to data inspected at run-time and to do so using some sort of lingua franca. Rulesheet authors are permitted to write rules with dependencies on this ancillary data, such as rules with dependencies on the type of information subject to disclosure control or even on the information's semantics. Likewise, the provider of information (whoever generates the document) may characterize or "mark up" that informatiuon with this ancillary data.
Operators of and contributors to semantic registries are responsible for maintaining glossaries of semantics for use by anyone, especially in this context by rulesheet authors, by primary custodians and their agents (such as entities engaged in information exchanges), and by Gatepoints for machine interpretation.
Operators of and contributors to type definition registries are responsible for maintaining listings of data type definitions for use by anyone, especially in this context by rulesheet authors, by primary custodians and their agents (such as entities engaged in information exchanges), and by Gatepoints for machine interpretation.
There are other registries, too, such as a special-purpose variant of a semantic registry called the thesaurus.
Persons responsible for oversight or compliance will often ask independent auditors to verify correctness of behavior of CDCL components and to verify correctness of policy expressed in Authoring Form. Such persons will need to cooperate with CDCL community members in order to access information required to perform their function.
In addition, the parties involved in information exchanges will need to cooperate with CDCL community members in order to integrate their exchange systems with CDCL Gatepoints and achieve an operable status with proper creation, management, and collation of stakeholders' rulesheets.