Talk:VSLMSM

From IHO Nautical Information Processing Working Group
Revision as of 04:01, 8 October 2010 by Rmm (talk | contribs)
Jump to navigation Jump to search

DavidAcland 11:10, 5 October 2010 (UTC) I have added a "Units" attribute VSLUNT. I have also changed the multiplicity of the sub-attributes VSLCAR and VSLVAL to make them mandatory.
Multiplicity of VSLUNT is also 1 at the moment but see my post on 5 Oct at Talk:VSLCAR.
I think we can only have a maximum of 2 COMPOPs so I have changed the multiplicity here to 0..2
Does this now work?

raphael 03:28, 8 October 2010 (UTC): I don't see why the number of COMPOPs should be limited to 2, each COMPOP compares the specified characteristic from own ship data to the VSLVAL with which the COMPOP is associated.

Actually the table of sub-attributes on VSLMSM as it is today (07 October 2010) should be changed to have either:

  • multiplicity = 1 and sequential = "n/a" for all rows; and we allow VSLMSM itself to be repeated; or
  • multiplicity = 1..* and sequential = "true" for all rows, and we don't allow VSLMSM to be repeated.

The first means that each instance of VSLMSM describes exactly one condition (so "50m <= vessellength <= 100 m" takes two VSLMSMs). The second puts all conditions under one VSLMSM, but "sequential = true" implies that each VSLCAR+VSLUNT+VSLVAL+COMPOP combination in that VSLMSM specifies one condition (this should be explained in the Remarks or the encoding guide).