VSLMSM

EATURE OBJECT ATTRIBUTES

Attribute: vessel's measurements

Acronym: VSLMSM Code:

Camel case: vesselsMeasurements

Attribute type: Complex

Definition:

Multitude of terms and definitions specifically related to ships. (http://en.wikipedia.org; 24 July 2010)

Sub-attribute	Camel Code Identifier	Multiplicity	Sequential
VSLCAR	vesselsCharacteristics	0..*	True
VSLVAL	vesselsCharacteristicsValue	0..*	True
COMPOP	ComparisonOperator	0..*	True

VSLCAR (length, beam, draught, air draught, GT, NT, DWT, DPL ) is just an idea, depending on the result of the discussion, we can keep or bin it.
COMPOP has to be to developed and should provide various comparison operators; see http://de.wikipedia.org/wiki/Logische_Operatoren or the English version http://en.wikipedia.org/wiki/Logical_connective
However, the German version provides the better symbols :)
The definition of LOGCOM must provide the relation between the value given in the model and the real ship's value.

That would give the result:
1. VSLCAR=draught; value=10.5; COMPOP=(>=) the regulation applies for vsl of 10.5 m draught and above
2. VSLCAR=DWT; Value=2000; COMPOP=(=) the regulation applies for vsl of exactly 2000 DWT
3. VSLCAR=length; value=150; COMPOP=(<) the regulation applies for vsl of less than 150 m length

Using your first example
[complex attribute [VSLCAR=length; value=50.0; COMPOP=(>)]], CATVSL=3 (tanker), LOGCON=1 (and), LIMTYP=2 (required); associated to a PILBOP object: tankers with LOA > 50.0 m must use the PILBOP

If the example should work for tanker between 50 and 100 m length the coding is like this
[complex attribute [VSLCAR=length; value=50.0; COMPOP=(>)], [VSLCAR=length; value=100.0; COMPOP=(<)]], CATVSL=3 (tanker), LOGCON=1 (and), LIMTYP=2 (required); associated to a PILBOP object: tankers with LOA > 50.0 m and < 100.0 m must use the PILBOP

---

David	Raphael	others	Jens
DA Y/N	RMM Y/N	others Y/N	JSF Y/N