Subject: RE: policyValidityPeriodCondition

From: "Black, David" <[email-masked]>
Date: Fri, 19 Feb 1999 20:40:34 -0500

> Let me try restating your position just to be sure that I got it:
> 
> policyValidityPeriod would be a subclass of policyCondition and MAY be
> included in the DNF/CNF or MAY be specially tied to the policyRule via
> another attribute.  IE, it is in the policyRuleConditionList or in another
> attribute on policyRule.

Yes, and just to strengthen your position :-), I
tend to agree with Glenn that the policyRule attribute
should be multi-valued.

> How is this different than any set of conditions that you want to AND/OR
> together in various combinations?  Are we now able to state that any
> arbitrary set of conditions follow DNF/CNF and another arbitrary set is
then
> DNF'ed with the result? 

The argument is by analogy from policyRuleEnabled -- this
is a fundamental administrative control interface that deals
with when a policyRule is in force or not in force.  This
is sufficiently important that forcing replication of it
in each DNF clause (especially when there are multiple
validity periods) is an invitation to subtle bugs.

--David

---------------------------------------------------
David L. Black, Senior Technologist
EMC Corporation, 42 South St., Hopkinton, MA  01748
+1 (508) 435-1000 x75140, FAX: +1 (508) 497-6909
[email-masked]
---------------------------------------------------