Talk:SHPREP
Drafted by SNPWG 7 Date
DA 15 May 07 catrgd added; Set Attributes C added; definition; notice is an information object and we only need the notice time here so notice replaced by ntctim
WEG 22May07 Changed name to general case shprep; added TXTDSC for non standard case; added catrep for categories of report (sailing plan; deviation rep etc); definition and remarks; added UML diagram of possible model. Change to ttxxtt SNPWG8
Jens 05.Nov 2007 changed ttxxtt to frmtxt in remarks section
Jens 12.12. added regdat, imorep deleted catrgd which is not longer reflected in FOA file
DA 9 Feb 08 rgdata deleted as it was replaced by imorep. -regdat is currently meaningless – removed. IMO put back in name. If the report is not i.a.w. IMO standards, catrep 8 applies.
WEG 12 Feb 08 All OK except restvc
jens 11:19, 13 August 2008 (CEST)
something is wrong here. Attribute B makes no longer sense
jens 14:31, 19 August 2008 (CEST) Attribute set B is back in the game, needs for providing any kind of formatted text
jens 19:17, 21 January 2009 (CET)
I am thinking it is correct to not having added OBJNAM/NOBJNM; PEREND; PERSAT; DATEND; DATSTA here. This object has an absolut relationship to her master.
DavidAcland 17:08, 23 January 2009 (CET)
I agree the relationship is strong. However I think that the OBJNAM could be something like "Le Havre entry report" or "Passing Noord Hinder report" - both made up by me but I suspect something like them exists. If that concept is right, then we could have the need for "DATSTA" and "DATEND" and "PERSTA" and "PEREND" as the requirement to report startsand ends; and they may also be seasonal. So I think they should be recommended associations even if they are not always used.
raphael 03:26, 26 August 2009 (UTC): Was leaving INFORM out of the attributes intended? INFORM might be useful for short descriptions if any.
jens 12:18, 7 August 2010 (UTC)replaced CHALIM by APPLIC
jens 08:51, 17 November 2011 (UTC)Do we need OBJNAM and NOBJNM to provide the name of the ship report if appropriate?