On Wed, Nov 17, 2004 at 02:47:41PM -0700, Andy Carver wrote:


> >> Yes, that's about right, although for F1 I'd probably say
> "ConfigurationOption has global- OptionSetting" to be clear that it is
> the global setting (the hyphen is necessary for correct verbalization by
> Visio, to attach the adjective to its noun (object type name)).

Boy, this is where ORM really begins to shine and where it's important
to be precise. By global setting I mean that some of the settings can
only be set globally. It's possible that some settings will also only be
settable for an individual.

Perhaps these are constraints but they are specific to a particular
group of settings. Ahh, there's the word I needed. I need to group my
settings into categories so that I can apply constraints to the
categories.

Given this explanation, would you still advise to use the global-
adjective in F1 ConfigurationOption has OptionSetting?





> >> I'm not quite clear on what you mean by "setting", in "OptionSetting
> has setting" -- I had been conceiving of OptionSetting itself as being
> the setting(s) given to some ConfigurationOption.

This is where I'm getting a bit confused. Let me use some examples
(which I should have put with the reference schemes):

"Print Statement Heading" for System is true
"Print Statement Heading" for Person(William) is false
"Max Days to Bump Rev" for System is 30

-- ERROR: This option cannot be set globally --
"Assign Debtor Number" for System is true
-- ERROR: Cannot set this option locally --
"Max Days to Bump Rev" for Person(William) is 15

In these examples are the options in quotes an OptionSetting? I guess
they would be. I've therefore used your input and my revised reference
schemes would be as follows:

Reference schemes: ConfigurationOption(Code), OptionSetting(Code),
Person(Id), OptionLevel(Code)
Base fact types: F1 ConfigurationOption for OptionLevel has OptionSetting
Constraints: C1 ConfigurationOption and OptionSetting must belong to
the same group
Derivation Rules: none

Reference schemes: OptionSetting(Code), OptionLevel(Code)
Base fact types: F1 OptionSetting belongs to group OptionLevel
Constraints: C1
Derivation Rules: none

Reference schemes: OptionLevel(Code)
Base fact types: F1
Constraints: C1
Derivation Rules: none
Examples: 'system', 'agency', 'client', 'collector'

In the reference scheme for OptionLevel, I'm not sure that anything more
is needed.


> >> Oh yes. In fact, the first part of step 3 is to make you think about
> what generalizations like this you might need.

Ahh, good to know what's coming up.


Thanks,
William

--
Knowmad Services Inc.
http://www.knowmad.com