RXNCOD - Revision history

Jens at 05:58, 23 January 2017

2017-01-23T05:58:47Z

Jens at 05:56, 23 January 2017

2017-01-23T05:56:03Z

Jens at 07:29, 16 May 2012

2012-05-16T07:29:31Z

Rmm at 04:58, 16 May 2012

2012-05-16T04:58:26Z

New page

Attribute: Regulation / restriction / recommendation / nautical information code

Acronym: RXNCOD

Attribute type: Complex

Camel Case: regRestRecNautInfCode

Definition:

A summary of the impact of the most common types of regulation, restriction, recommendation and nautical information on a vessel.

{| style="background:#ccc99; color:black;" border="1" cellpadding="5" cellspacing="0" align="left"
!Sub-attribute!!Camel Code Identifier!!Multiplicity!!Sequential
|-
|[[CATRXN]]||categoryOfRegRestRecNautInf||0..1||n/a
|-
|[[SUBJCT]]||subject||0..1||n/a
|-
|[[ACTION]]||actionOrActivity||0..1||n/a
|-
|[[ACTXEP]]||actionOrActivityException||0..1||n/a
|-
|[[CATREL]]||categoryOfRelationship||1||n/a
|-
|}

Remarks:

No remarks.

Distinction:

No distinctions.

Justification: 
New attribute 

Comments:

The Product Specification should show that this attribute could be repeated if there are a number of regulations affecting the vessel.

Populate [[SUBJCT]] if [[CATRXN]] does not cover the type of regulation sufficiently accurately.

Populate [[ACTXEP]] if [[ACTION]] does not describe the action or activity sufficiently accurately.

----

{| style="background:#ccc99; color:black;" border="1" cellpadding="5" cellspacing="0" align="left"
!David!!Raphael!!Jens
|- style="background:white; color:black"
|Y
|Y
|Y/N
|}

Jens at 05:29, 15 May 2012

2012-05-15T05:29:43Z

New page

Attribute: Regulation / restriction / recommendation / nautical information code

Acronym: RXNCOD

Attribute type: Complex

Camel Case: RegRestRecNautInfCode

Definition:

A summary of the impact of the most common types of regulation, restriction, recommendation and nautical information on a vessel.

{| style="background:#ccc99; color:black;" border="1" cellpadding="5" cellspacing="0" align="left"
!Sub-attribute!!Camel Code Identifier!!Multiplicity!!Sequential
|-
|[[CATRXN]]||categoryOfRegRestRecNautInf||0..1||n/a
|-
|[[SUBJCT]]||subject||0..1||n/a
|-
|[[ACTION]]||action||0..1||n/a
|-
|[[ACTXEP]]||actionOrActivityException||0..1||n/a
|-
|[[CATREL]]||categoryOfRelationship||1||n/a
|-
|}

Remarks:

No remarks.

Distinction:

No distinctions.

Justification: 
New attribute 

Comments:

The Product Specification should show that this attribute could be repeated if there are a number of regulations affecting the vessel.

Populate [[SUBJCT]] if [[CATRXN]] does not cover the type of regulation sufficiently accurately.

Populate [[ACTXEP]] if [[ACTION]] does not describe the action or activity sufficiently accurately.

----

{| style="background:#ccc99; color:black;" border="1" cellpadding="5" cellspacing="0" align="left"
!David!!Raphael!!Jens
|- style="background:white; color:black"
|Y/N
|Y/N
|Y/N
|}

Jens at 08:25, 30 January 2012

2012-01-30T08:25:19Z

Rmm at 23:25, 27 January 2012

2012-01-27T23:25:25Z

New page

Attribute: Regulation / restriction / recommendation / nautical information code

Acronym: RXNCOD

Attribute type: Complex

Camel Case: RegRestRecNautInfCode

Definition:

A summary of the impact of the most common types of regulation, restriction, recommendation and nautical information on a vessel.

{| style="background:#ccc99; color:black;" border="1" cellpadding="5" cellspacing="0" align="left"
!Sub-attribute!!Camel Code Identifier!!Multiplicity!!Sequential
|-
|[[SUBJCT]]||subject||1||n/a
|-
|[[ACTION]]||action||1||n/a
|-
|[[CATREL]]||categoryOfRelationship||1||n/a
|-
|}

Remarks:

No remarks.

Distinction:

No distinctions.

Justification: 
New attribute 

Comments:

The Product Specification should show that this attribute could be repeated if there are a number of regulations affecting the vessel.

----

{| style="background:#ccc99; color:black;" border="1" cellpadding="5" cellspacing="0" align="left"
!David!!Raphael!!Jens
|- style="background:white; color:black"
|Y
|Y
|Y/N
|}

Jens at 11:13, 20 June 2011

2011-06-20T11:13:00Z

New page

Attribute: Regulation / restriction / recommendation / nautical information code

Acronym: RXNCOD

Attribute type: Complex

Camel Case: RegRestRecNautInfCode

Definition:

A summary of the impact of the most common types of regulation, restriction, recommendation and nautical information on a vessel.

sub-attribute CamelCode Identifier cardinality sequential

[[SUBJCT]] SubAttribute subject 1 n/a

[[ACTION]] SubAttribute action 1 n/a

[[CATREL]] SubAttribute limitationType 1 n/a

Remarks:

No remarks.

Distinction:

No distinctions.

Justification: 
to be completed 

Comments:

The Product Specification should show that this attribute could be repeated if there are a number of regulations affecting the vessel.

----

{| style="background:#ccc99; color:black;" border="1" cellpadding="5" cellspacing="0" align="left"
!David!!Raphael!!others!!Jens
|- style="background:white; color:black"
|DA Y/N
|RMM Y/N
|others Y/N
|JSF Y/N
|}

Jens at 10:28, 5 January 2010

2010-01-05T10:28:58Z

New page

Attribute: Regulation / restriction / recommendation / nautical information code

Acronym: RXNCOD

Attribute type: Simple

Camel Case: RegRestRecNautInfCode

Data Type: Enumeration

Definition: This attribute encodes the most common types of regulations (recommendations, restrictions).

Values:

1 Pilotage compulsory

2 Pilot qualifications

3 Passage prohibited

4 Passage conditionally prohibited

5 Overtaking prohibited

6 Overtaking conditionally permitted

7 Restricted passage

8 Tugs

9 Quarantine and health

10 Customs

11 Loading and unloading

12 Drawbridge operations

13 Navigation prohibited (((should always be charted)))

14 Right of way

15 Traffic permission required

16 Dimensional

Definitions:

Pilotage compulsory

Pilotage is compulsory

Pilot qualifications

Pertaining to the qualifications of pilot (details described in INFORM attribute or TXTDSC file)

Passage prohibited

Passage prohibited at all times

Passage conditionally prohibited

Passage prohibited under certain weather conditions (details in INFORM or TXTDSC file)

Overtaking prohibited

Overtaking prohibited at all times

Overtaking conditionally permitted

Overtaking permitted only under certain conditions (stated in INFORM/TXTDSC file)

Restricted passage

Pertaining to head-on situations in restricted passages or fairways (details in INFORM or TXTDSC file)

Tugs

Tug assistance compulsory

Quarantine and health

Quarantine and health regulations (details described in INFORM or TXTDSC)

Customs

Customs regulations (details described in INFORM or TXTDSC)

Loading and unloading

Loading and unloading cargo (details in INFORM or TXTDSC)

Drawbridge operations

Drawbridge operations (details in INFORM or TXTDSC)

Navigation prohibited

Navigation prohibited

Right of way

Pertaining to right of way (details in INFORM or TXTDSC)

Traffic permission required

Permission required from an authority for transit (details in INFORM or TXTDSC)

Dimensional

Applicable only to vessels exceeding specified dimensions (associated chalim will specify limits)

Remarks: This attribute encodes the most common types of regulations (recommendations, restrictions) in a form that software (e.g., ECDIS) can use to do at least some subject-specific processing. Since the details are in natural language (i.e., as text in INFORM), this will not be comprehensive, but (a) it should be possible to use this in conjunction with “chalim” in some cases to provide enhancements like automatic indicators in the ECDIS/ECS that passage is forbidden for vessels of certain size; (b) provide hints, such as a hint that pilotage is probably compulsory, etc.

In spite of the similarity in names, they are actually have different functions: CATRXN is intended for "classifying" of 4-brothers instances; RXNCOD is designed to "identify" what the specific regulation, etc., says in a way that can be recognized by software, which allows specific alerts to be raised.

Comments for addition of more codes, refinement or removal of codes 9, 10, 11, 12, 14 invited.

Distinction:

No distinctions.

----

{| style="background:#ccc99; color:black;" border="1" cellpadding="5" cellspacing="0" align="left"
!David!!Raphael!!others!!Jens
|- style="background:white; color:black"
|DA Y/N
|RMM Y/N
|others Y/N
|JSF Y/N
|}

Jens at 13:58, 24 October 2009

2009-10-24T13:58:12Z

← Older revision		Revision as of 13:58, 24 October 2009
Line 143:		Line 143:

	----		----
−
−	~~{\| style="background:#ccc99; color:black;" border="1" cellpadding="5" cellspacing="0" align="left"~~
−	~~!David!!Ricardo!!Rolando!!Jens!!Tom~~
−	~~\|- style="background:white; color:black"~~
−	~~\|Y/N~~
−	~~\|Y/N~~
−	~~\|Y/N~~
−	~~\|Y/N~~
−	~~\|Y/N~~
−	\|}

@@ Line 24: / Line 24: @@
 |-
 |}
@@ Line 45: / Line 51: @@
 The Product Specification should show that this attribute could be repeated if there are a number of regulations affecting the vessel.
@@ Line 59: / Line 58: @@
 {| style="background:#ccc99; color:black;" border="1" cellpadding="5" cellspacing="0" align="left"
-!David!!Raphael!!Jens
+!Raphael!!Jens
 |- style="background:white; color:black"
 |Y
 |Y
 |}

@@ Line 18: / Line 18: @@
 |-
 |[[CATRXN]]||categoryOfRegRestRecNautInf||0..1||n/a
 |-
 |[[ACTION]]||actionOrActivity||0..1||n/a
 |-
-|[[ACTXEP]]||actionOrActivityException||0..1||n/a
+|[[HEADLN]]||Headline||0..1||n/a
 |-
 |}

@@ Line 85: / Line 85: @@
 |Y
 |Y
-|Y/N
+|Y
 |}

@@ Line 67: / Line 67: @@
 |Y
 |Y
-|Y/N
+|Y
 |}