parid0157 | Mon, 18 Nov 2002 18:47:56
I agree with bernard, it is not clear in the RM how I model symmetrical relationships. Such as his sibling example.
parid0157 | Wed, 20 Nov 2002 08:43:50
> Why, though, is it necessary to define two different
> role types, even though one would do the job?
>
> The answer is that without the rules:
>
>  (1) that all role types must be different, and
This, I feel, is the role that is in error in the current RM.
>  (2) that there can be only one role player per role type,
This is the role that is actually needed.
> ...the Subject Location Uniqueness Objective can't be
> supported.
I cannot agree with this statement. SLUO can be supported more simply by
requiring the pair to be unique.
parid0157 | Mon, 18 Nov 2002 18:47:56
I agree with bernard, it is not clear in the RM how I model symmetrical relationships. Such as his sibling example.
parid0157 | Wed, 20 Nov 2002 08:43:50
> Why, though, is it necessary to define two different
> role types, even though one would do the job?
>
> The answer is that without the rules:
>
>  (1) that all role types must be different, and
This, I feel, is the role that is in error in the current RM.
>  (2) that there can be only one role player per role type,
This is the role that is actually needed.
> ...the Subject Location Uniqueness Objective can't be
> supported.
I cannot agree with this statement. SLUO can be supported more simply by
requiring the pair to be unique.
parid0157 | Mon, 18 Nov 2002 18:47:56
I agree with bernard, it is not clear in the RM how I model symmetrical relationships. Such as his sibling example.
parid0157 | Wed, 20 Nov 2002 08:43:50
> Why, though, is it necessary to define two different
> role types, even though one would do the job?
>
> The answer is that without the rules:
>
>  (1) that all role types must be different, and
This, I feel, is the role that is in error in the current RM.
>  (2) that there can be only one role player per role type,
This is the role that is actually needed.
> ...the Subject Location Uniqueness Objective can't be
> supported.
I cannot agree with this statement. SLUO can be supported more simply by
requiring the pair to be unique.
parid0157 | Mon, 18 Nov 2002 18:47:56
I agree with bernard, it is not clear in the RM how I model symmetrical relationships. Such as his sibling example.
parid0157 | Wed, 20 Nov 2002 08:43:50
> Why, though, is it necessary to define two different
> role types, even though one would do the job?
>
> The answer is that without the rules:
>
>  (1) that all role types must be different, and
This, I feel, is the role that is in error in the current RM.
>  (2) that there can be only one role player per role type,
This is the role that is actually needed.
> ...the Subject Location Uniqueness Objective can't be
> supported.
I cannot agree with this statement. SLUO can be supported more simply by
requiring the pair to be unique.
parid0157 | Mon, 18 Nov 2002 18:47:56
I agree with bernard, it is not clear in the RM how I model symmetrical relationships. Such as his sibling example.
parid0157 | Wed, 20 Nov 2002 08:43:50
> Why, though, is it necessary to define two different
> role types, even though one would do the job?
>
> The answer is that without the rules:
>
>  (1) that all role types must be different, and
This, I feel, is the role that is in error in the current RM.
>  (2) that there can be only one role player per role type,
This is the role that is actually needed.
> ...the Subject Location Uniqueness Objective can't be
> supported.
I cannot agree with this statement. SLUO can be supported more simply by
requiring the pair to be unique.
parid0157 | Mon, 18 Nov 2002 18:47:56
I agree with bernard, it is not clear in the RM how I model symmetrical relationships. Such as his sibling example.
parid0157 | Wed, 20 Nov 2002 08:43:50
> Why, though, is it necessary to define two different
> role types, even though one would do the job?
>
> The answer is that without the rules:
>
>  (1) that all role types must be different, and
This, I feel, is the role that is in error in the current RM.
>  (2) that there can be only one role player per role type,
This is the role that is actually needed.
> ...the Subject Location Uniqueness Objective can't be
> supported.
I cannot agree with this statement. SLUO can be supported more simply by
requiring the pair to be unique.