Talk:SHPREP - Revision history

Rmm at 06:25, 4 July 2013

2013-07-04T06:25:45Z

Jens at 08:56, 17 November 2011

2011-11-17T08:56:49Z

Jens at 08:53, 17 November 2011

2011-11-17T08:53:49Z

Jens at 08:51, 17 November 2011

2011-11-17T08:51:38Z

Jens at 12:18, 7 August 2010

2010-08-07T12:18:05Z

Rmm at 03:26, 26 August 2009

2009-08-26T03:26:45Z

New page

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

[[User:Jens|jens]] 11:19, 13 August 2008 (CEST)

something is wrong here. Attribute B makes no longer sense

[[User:Jens|jens]] 14:31, 19 August 2008 (CEST)
Attribute set B is back in the game, needs for providing any kind of formatted text

[[User:Jens|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.

[[User:DavidAcland|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.

[[User:Rmm|raphael]] 03:26, 26 August 2009 (UTC): Was leaving INFORM out of the attributes intended? INFORM might be useful for short descriptions if any.

Submitted to Hydro register manager Date

Submitted to Nav register manager Date

Jens at 18:17, 21 January 2009

2009-01-21T18:17:14Z

Jens at 12:33, 19 August 2008

2008-08-19T12:33:16Z

Jens at 12:31, 19 August 2008

2008-08-19T12:31:53Z

Jens at 09:19, 13 August 2008

2008-08-13T09:19:03Z

New page

← Older revision		Revision as of 06:25, 4 July 2013
Line 34:		Line 34:

	[[User:Jens\|jens]] 12:18, 7 August 2010 (UTC)replaced [[CHALIM]] by [[APPLIC]]		[[User:Jens\|jens]] 12:18, 7 August 2010 (UTC)replaced [[CHALIM]] by [[APPLIC]]
		+
		+	[[User:Rmm\|raphael]] 06:25, 4 July 2013 (UTC): In the MPA mapping for the Hawaii MPA there are cases where the complex attribute [[TXTCON]] is also bound to SHPREP, [[TXTCON]] should be added as an attribute of [[SHPREP]] on the main page.

← Older revision		Revision as of 08:56, 17 November 2011
Line 34:		Line 34:

	[[User:Jens\|jens]] 12:18, 7 August 2010 (UTC)replaced [[CHALIM]] by [[APPLIC]]		[[User:Jens\|jens]] 12:18, 7 August 2010 (UTC)replaced [[CHALIM]] by [[APPLIC]]
−
−	~~[[User:Jens\|jens]] 08:51, 17 November 2011 (UTC)Controversy to my argument 21 Jan 2009, do we need OBJNAM and NOBJNM to provide the name of the ship report if appropriate?~~

← Older revision		Revision as of 08:53, 17 November 2011
Line 35:		Line 35:
	[[User:Jens\|jens]] 12:18, 7 August 2010 (UTC)replaced [[CHALIM]] by [[APPLIC]]		[[User:Jens\|jens]] 12:18, 7 August 2010 (UTC)replaced [[CHALIM]] by [[APPLIC]]

−	[[User:Jens\|jens]] 08:51, 17 November 2011 (UTC)Do we need OBJNAM and NOBJNM to provide the name of the ship report if appropriate?	+	[[User:Jens\|jens]] 08:51, 17 November 2011 (UTC)Controversy to my argument 21 Jan 2009, do we need OBJNAM and NOBJNM to provide the name of the ship report if appropriate?

← Older revision		Revision as of 08:51, 17 November 2011
Line 34:		Line 34:

	[[User:Jens\|jens]] 12:18, 7 August 2010 (UTC)replaced [[CHALIM]] by [[APPLIC]]		[[User:Jens\|jens]] 12:18, 7 August 2010 (UTC)replaced [[CHALIM]] by [[APPLIC]]
		+
		+	[[User:Jens\|jens]] 08:51, 17 November 2011 (UTC)Do we need OBJNAM and NOBJNM to provide the name of the ship report if appropriate?

← Older revision		Revision as of 12:18, 7 August 2010
Line 33:		Line 33:
	[[User:Rmm\|raphael]] 03:26, 26 August 2009 (UTC): Was leaving INFORM out of the attributes intended? INFORM might be useful for short descriptions if any.		[[User:Rmm\|raphael]] 03:26, 26 August 2009 (UTC): Was leaving INFORM out of the attributes intended? INFORM might be useful for short descriptions if any.

−	~~Submitted to Hydro register manager Date~~	+	[[User:Jens\|jens]] 12:18, 7 August 2010 (UTC)replaced [[CHALIM]] by [[APPLIC]]
−
−	~~Submitted to Nav register manager Date~~

← Older revision		Revision as of 18:17, 21 January 2009
Line 21:		Line 21:
	[[User:Jens\|jens]] 14:31, 19 August 2008 (CEST)		[[User:Jens\|jens]] 14:31, 19 August 2008 (CEST)
	Attribute set B is back in the game, needs for providing any kind of formatted text		Attribute set B is back in the game, needs for providing any kind of formatted text
		+
		+
		+	[[User:Jens\|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.

@@ Line 21: / Line 21: @@
 [[User:Jens|jens]] 14:31, 19 August 2008 (CEST)
 Attribute set B is back in the game, needs for providing any kind of formatted text
-−
 Submitted to Hydro register manager	Date
 Submitted  to Nav register manager	Date

← Older revision		Revision as of 12:31, 19 August 2008
Line 18:		Line 18:

	something is wrong here. Attribute B makes no longer sense		something is wrong here. Attribute B makes no longer sense
		+
		+	[[User:Jens\|jens]] 14:31, 19 August 2008 (CEST)
		+	Attribute set B is back in the game, needs for providing any kind of formatted text