Difference between revisions of "RXNCOD"

Revision as of 11:13, 20 June 2011

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.

David	Raphael	others	Jens
DA Y/N	RMM Y/N	others Y/N	JSF Y/N

@@ Line 3: / Line 3: @@
 Acronym: RXNCOD
-Attribute type: Simple
+Attribute type: Complex
 Camel Case: RegRestRecNautInfCode
-Data Type: Enumeration
-Definition: This attribute encodes the most common types of regulations (recommendations, restrictions).
+Definition:
-Values:
+A summary of the impact of the most common types of regulation, restriction, recommendation and nautical information on a vessel.
-	Pilotage compulsory
-	Pilot qualifications
-	Passage prohibited
+sub-attribute       CamelCode Identifier	cardinality	sequential
-	Passage conditionally prohibited
+[[SUBJCT]] SubAttribute	subject	1	n/a
-	Overtaking prohibited
+[[ACTION]] SubAttribute	action	1	n/a
-	Overtaking conditionally permitted
+[[CATREL]] SubAttribute	limitationType	1	n/a
-	Restricted passage
-	Tugs
+Remarks:
-	Quarantine and health
+No remarks.
-	Customs
-	Loading and unloading
+Distinction:
-	Drawbridge operations
-	Navigation prohibited     (((should always be charted)))
-	Right of way
-	Traffic permission required
-	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
+No distinctions.
-Overtaking conditionally permitted
-Overtaking permitted only under certain conditions (stated in INFORM/TXTDSC file)
+Justification:<br>
+<span style="color:red;">to be completed</span><br>
+Comments:
-Restricted passage
+The Product Specification should show that this attribute could be repeated if there are a number of regulations affecting the vessel.
-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.
 ----

Difference between revisions of "RXNCOD"

Revision as of 11:13, 20 June 2011

Navigation menu

Search