Difference between revisions of "Talk:OPERAT"

From IHO Nautical Information Processing Working Group
Jump to navigation Jump to search
m
Line 13: Line 13:
  
 
[[User:Jens|jens]] 06:16, 28 October 2009 (UTC) I agree. The remarks are useful.
 
[[User:Jens|jens]] 06:16, 28 October 2009 (UTC) I agree. The remarks are useful.
 +
 +
== Draft extension for logical connectives ==
 +
 +
[[User:Rmm|raphael]] 00:15, 16 February 2010 (UTC): Here is a draft of the extension discussed on [[Talk:CHALIM]].
 +
 +
Definition: A process or action, such as addition, substitution, transposition, or differentiation, logical conjunction or disjunction, performed in a specified sequence and in accordance with specific rules.
 +
 +
Attribute values: add
 +
<br>3 logical conjunction
 +
<br>4 logical disjunction
 +
 +
logical conjunction
 +
 +
all the conditions described by the other attributes of the object, or sub-attributes of the same complex attribute, are true
 +
 +
logical disjunction
 +
 +
at least one of the conditions described by the other attributes of the object, or sub-attributes of the same complex attributes, is true
 +
 +
Remarks: Add:
 +
<br>When bound to the object [[CHALIM]], OPERAT can take only the values 3 or 4.
 +
 +
CHALIM/MAXLOA = 50.0, CHALIM/MAXDRF=10.0, CHALIM/OPERAT=3
 +
 +
implies the limitation applies only when LOA > 50.0 and draught > 10.0
 +
 +
I have drafted it as an extension to OPERAT so we can discuss it, but am a little reluctant to make the concept of "logical connection" an extension of OPERAT instead of a different attribute. As drafted, the combination looks a little awkward to me, even if it is not mixing apples and oranges, it looks like to different varieties of apples...

Revision as of 00:15, 16 February 2010

raphael 20:33, 27 October 2009 (UTC): Ideas for a better name than OPERAT are welcome. The rationale for this variable and the reasons for not using "function" are at Talk:UKCVAR.

I suggest the following addition to the definition:

Remarks:

OPERAT is intended to be used in conjunction with other sub-attributes of a complex attribute to indicate how their values must be combined in order to describe a condition. Example: The combination

UKCLRN (complex attribute)
UKCFIX=2.5, UKCVAR=10.00, OPERAT=1 (sub-attributes)

indicates that the under-keel clearance required is the greater of 2.5 metres or 10% of the ship's draught.

jens 06:16, 28 October 2009 (UTC) I agree. The remarks are useful.

Draft extension for logical connectives

raphael 00:15, 16 February 2010 (UTC): Here is a draft of the extension discussed on Talk:CHALIM.

Definition: A process or action, such as addition, substitution, transposition, or differentiation, logical conjunction or disjunction, performed in a specified sequence and in accordance with specific rules.

Attribute values: add
3 logical conjunction
4 logical disjunction

logical conjunction

all the conditions described by the other attributes of the object, or sub-attributes of the same complex attribute, are true

logical disjunction

at least one of the conditions described by the other attributes of the object, or sub-attributes of the same complex attributes, is true

Remarks: Add:
When bound to the object CHALIM, OPERAT can take only the values 3 or 4.

CHALIM/MAXLOA = 50.0, CHALIM/MAXDRF=10.0, CHALIM/OPERAT=3

implies the limitation applies only when LOA > 50.0 and draught > 10.0

I have drafted it as an extension to OPERAT so we can discuss it, but am a little reluctant to make the concept of "logical connection" an extension of OPERAT instead of a different attribute. As drafted, the combination looks a little awkward to me, even if it is not mixing apples and oranges, it looks like to different varieties of apples...