Open points

jens 08:13, 1 August 2008 (CEST)

1. Unit: defined in the wunits attribute of the M_UNIT meta object class, e.g. metric tons (t) (TSMAD?)

2. time schedule - need use case validation

3. Schtim Deleted and worked on tmstrm

4. sigves Deleted I am still waiting for an explanation why? How should we present those signals; e.g. visual and acoustic lock open request

5. Nfmtxt David come to this.

6. SLCONS Action to be completed. The question was here to add avlblg to SLCONS instead of BERTHS were it is probably wrong.

7. further thought: we still have the problem of general nautical advices/instructions/information or whatever open. This inf. object should be used in the same composition like our three brothers

8. developing first proposals for natural conditions (Jens' job)

jens 19:06, 28 September 2008 (CEST)did somework, placed at associated files entry, ready for discussion

jens 19:19, 8 August 2008 (CEST)

9. Check whether frmtxt is handled as type of attribute like list or enumerated; important to come to decision for coupe of information objects

10. By DA 12 Aug 08 worked on frmtxt. Concluded that there will not be an attribute type "formatted text" or anything like it in S-100. Discussed way ahead with Barry and Jens. Drafted txtdad and ntxtda. This construct is novel but intended to stimulate discussion on the acceptability or otherwise of using XHTML, XML or GML to circulate information to customers to be read by ECDIS or ECS.