Given the following document,

<?xml version=”1.0” encoding=”UTF-8” ?>
<local-club-treasurer-report>
 <report-submission-trigger>
  <date-trigger>
   <date>2009-05-15</date>
  </date-trigger>
 </report-submission-trigger>
 <treasury-data>
  <club-treasurer>
   <full-name>Race Bannon</full-name>
  </club-treasurer>
  <bank-account-information>
   <statement-date>2009-04-30</statement-date>
   <header>The club's bank account:</header>
   <starting-balance>
    <amount>$700.00</amount>
   </starting-balance>
   <ending-balance>
    <amount>$1600.00</amount>
   </ending-balance>
  </bank-account-information>
 </treasury-data>
</local-club-treasurer-report>

...one can use CDCL Authoring Form to express this disclosure control policy: “Disclose and don't quote anything out of context concerning treasury information either when the business purpose is a tax audit or a tax return preparation or a justice proceeding or when the user's role is treasurer or president, as long as the user knows not to quote anything out of context.”
[This rulesheet could be identified by a composite key that included a problem space of “http://mybogusclub.com/document/club/treasurer/report” or a primary custodian of “http://stakeholders/mybogusclub.com” or both.]

default-rule
	id:
		1
	apply-outcomes:
		mask

rule
	id:
		2
	apply-outcomes:
		disclose-and-don't-quote-out-of-context
		obligation-of-disclosure
			text:
				You are obliged to refrain from quoting any of this out of context. If you disclose, you must disclose in full.
	for-content:
		* present-item has-caption “/local-club-treasurer-report/treasury-data”
	for-conditions:
		* any-true
			* all-true
				* all-users
				* any-true
					* business-purpose means tax-audit
					* business-purpose means tax-preparation
					* business-purpose means justice
			* any-true
				* user's-roles contain-something-that-means treasurer
				* user's-roles contain-something-that-means president

rule
	id:
		3
	apply-outcomes:
		disclose
	for-content:
		* present-item has-caption “/local-club-treasurer-report”
	for-conditions:
		* any-true
			* business-purpose means tax-audit
			* business-purpose means tax-preparation
			* business-purpose means justice
			* user's-roles contain-something-that-means treasurer
			* user's-roles contain-something-that-means president

Anything not appearing within quotation marks (anything not a literal string) in the rulesheet example above will eventually need to be interpreted by the CDCL system responsible for evaluating policy. Each of these items will either be understood natively by the system (because the item either is a keyword or is a synonym for a keyword) or be understood as a result of a rule author's use of the alias mechanism. Below are the alias declarations for the example rulesheet above, and these alias declarations are permitted to appear mostly anywhere within the rulesheet, for example at the bottom.
alias
	replace:
		tax-audit
	with:
		“http://registry/semantics/finance/taxation/audit”

alias
	replace:
		tax-preparation
	with:
		“http://registry/semantics/finance/taxation/return/preparation”

alias
	replace:
		justice
	with:
		“http://registry/semantics/government/justice”

alias
	replace:
		treasurer
	with:
		“http://registry/semantics/treasurer”

alias
	replace:
		president
	with:
		“http://registry/semantics/president”


In this example above, the outcome's prohibition on piecemeal redaction of elements within the 'treasury data' will prevent some stakeholder from having “redact ending-balance” policy enforced that would otherwise result in an output document like:

<?xml version=”1.0” encoding=”UTF-8” ?>
<local-club-treasurer-report>
 <report-submission-trigger>
  <date-trigger>
   <date>2009-05-15</date>
  </date-trigger>
 </report-submission-trigger>
 <treasury-data>
  <club-treasurer>
   <full-name>Race Bannon</full-name>
  </club-treasurer>
  <bank-account-information>
   <statement-date>2009-04-30</statement-date>
   <header>The club's bank account:</header>
   <starting-balance>
    <amount>$700.00</amount>
   </starting-balance>
   <ending-balance>
   </ending-balance>
  </bank-account-information>
 </treasury-data>
</local-club-treasurer-report>

...or in an equally undesirable case where some stakeholder's policy involved more elaborate redactions, an output document like:

<?xml version=”1.0” encoding=”UTF-8” ?>
<local-club-treasurer-report>
 <report-submission-trigger>
  <date-trigger>
   <date>2009-05-15</date>
  </date-trigger>
 </report-submission-trigger>
 <treasury-data>
  <club-treasurer>
   <full-name>Race Bannon</full-name>
  </club-treasurer>
  <bank-account-information>
   <statement-date>2009-04-30</statement-date>
   <header>The club's bank account:</header>
    <amount>$700.00</amount>
  </bank-account-information>
 </treasury-data>
</local-club-treasurer-report>

Both of the output forms above, were they to be permitted to exist, would in many cases be interpreted incorrectly to mean that the club's balance on 4/30 was something other than $1600. Instead, the prohibition due to the don't-quote-out-of-context outcome would interact with a stipulated redaction outcome on any included element, such as on ending-balance, resulting in a proper output document like:

<?xml version=”1.0” encoding=”UTF-8” ?>
<local-club-treasurer-report>
 <report-submission-trigger>
  <date-trigger>
   <date>2009-05-15</date>
  </date-trigger>
 </report-submission-trigger>
</local-club-treasurer-report>