€¦ · Web viewReplace “TRF” with MTM. Accept . okay. ... Word comment with adapted revised...

S-127 0.1 Combined comments and editorial observations (Please send all comments to Carlo Marchi (elena_armanino[at]marina.difesa.it)

Date: Document: Various Proposals

1 2 (3) 4 5 (6) (7)

Com

ponent

CO1 Clause No./Subclause

No./Annex

(e.g. 3.1)

Paragraph/Figure/Table/

Note(e.g. Table 1)

Type of

com-ment2

Comment (justification for change) by the CO3 Proposed change by the CO Secretariat observations

on each comment submitted

PS NGA 3.1, 4.1, 4.2, 5 (two items),6.2.1.3, and 8.1.5

ed Use of the term “clause” when referring to other parts of this document. Highlighted in red in original document.

What is the proper term?Clause/Chapter/Paragraph/Sector/Section?Pick one term for consistency.

Accept.Will use “clause”okay

PS NGA 6.2.1.4 and 10.2 (both in comment bubbles)

er Use of the term “paragraph” when referring to other parts of this document. Highlighted in red in original document.


Reject.Only one place where “paragraph” is used in original, and that is a general statement about other documents such as regulations. okay

PS NGA 5, 6.1 (two items), 6.2, 6.2.1.3 (in comment bubble) , and 11.8

ed Use of the term “section” when referring to other parts of this document. Highlighted in red in original document.


Accept.Will use “clause”okay

PS NGA 1.1 Line 9 ed Add comma Change to read: …services offered, and instructions…

Accept.

PS NGA 3.1 Line 21 ed On page 8--Add comma Change to read: …supplied to, and used by… AcceptPS NGA 3.1 Line 24 ed On page 8--Add comma Change to read: …end use, or other… AcceptPS NGA 3.2 Line 8 teed Add acronym for Marine Traffic Management Add: MTM Marine Traffic Management Accept

1 CO = Contributing Organisation (HOs should use 2 character codes e.g. FR AU etc.)2 Type of comment: ge = general te = technical ed = editorial3 Whilst not compulsory, comments are more likely to be accepted if accompanied by a proposed change. NOTE Columns 1, 2, 4, 5 are compulsory.

page 1 of 31



1 2 (3) 4 5 (6) (7)

Com

ponent


No./Annex

(e.g. 3.1)


Note(e.g. Table 1)

Type of

com-ment2



PS NGA 4.1 Abstract—Line 4

ed Add comma Change to read: …offered, and instructions Accept

PS NGA 4.1 Content—Lines 1-2

ed Use acronym Change from marine traffic management to MTM Accept

PS NGA 4.1 Content—Line 4

ed Add comma Change to read: …sources, and publication Accept

PS NGA 4.1 Specific Purpose—Line 2

teed Should reflect MTM information Change radio services to read marine traffic management

Accept

PS NGA 4.3.3 Para 1—Line 2

ed Fixes awkward grammar Change to read: …errors or to introduce… Accept

PS NGA 4.3.4 Para 1—Lines 1-2

ed Change to read: …correct spelling, punctuation, or grammar errors;

Accept/modify.Will also remove “in spelling, punctuation, and grammar” at end of the sentence.okay

PS NGA 5 Table—Row 2

ed Capitalization Capitalize Marine Traffic Management Accept


ed Change to read: …offered, and instructions… Accept


ed Should reflect MTM information Change radio services to read Marine Traffic Management

Accept


page 2 of 31



1 2 (3) 4 5 (6) (7)

Com

ponent


No./Annex

(e.g. 3.1)


Note(e.g. Table 1)

Type of

com-ment2



PS NGA 6.1 Page 15—Para 1—Line 3

ed Add comma Change to read: …values, and relationships… Accept

PS NGA 6.1 Page 15—Figure 2

edFigure in awkward location Move figure 2 to after Para 1on Page 15, if

possible

Accept

PS ntou 6.1 Paragraph 2 ed The statement " The distance between two consecutive control points must not exceed 0.3 mm at a display scale of 1:10000." is incorrect.0.3mm should be the minimum distance.

S-127 DCEG Clause 2.3.2 states that " The capture density will follow the recommendation of the S-101 (ENC) DCEG, that states curves and surface boundaries should not be encoded at a point density greater than 0.3 mm at permitted display scale."

Some changes in the ordering and phrasing might improve the clarity.

S-127 further constrains Level 3a with the following:• Coincident linear geometry must be avoided

when there is a dependency between features.

• Linear geometry is defined by curves which are made of curve segments. Each curve segment contains the geographic coordinates as control points and defines an interpolation method between them. The distance between two consecutive control points must not be less than 0.3 mm at the maximum display scale.

• The interpolation of S100_ArcByCenterPoint and S100_CircleByCenterPoint curve segments must be circular arc with centre and radius, as described in S-100 §§ 7-4.2.1, 7-4.2.20, and 7-4.2.21.

• The interpolation of other GM_CurveSegment must be loxodromic.

AcceptS-127 will use the same language but change “maximum display scale” to 10000 since S-127 is scale independent.


page 3 of 31



1 2 (3) 4 5 (6) (7)

Com

ponent


No./Annex

(e.g. 3.1)


Note(e.g. Table 1)

Type of

com-ment2



PS NGA 6.2 Para 1—Line 1

edWhat does the phrase “UML models shown below” refer to?

Accept.“shown below” -> “in this clause” – given that the PS will use “clause”okay

PS NGA6.2.1.1 All te There is no reference to Ship Reporting Systems

(SRS) in the “Overview of domain features and information types.” It appears that SRS is included as a subset of VTS.

An SRS normally cover a larger area than a VTS (entire country/ocean basin vs port area). The modelling for SRS needs to be expanded by creating its own information.

Two new featuresSRSLocal port serviceMultiplicity of category attribute in VTSArea made 0..*.Listed values for SRS and LPS removed from category attribute..

PS ntou 6.2.1.1 Paragraph 1Fig.4 & 5

te Marine farms, fixed fishing net , fish traps, and fish havens may be well offshore and affect navigation.Their location may be temporary.Concentration of fishing vessels may be expected in the vicinity of fish havens.

Add another S-127 feature type( sub-type) to encode areas where these may be encountered and the restrictions.

Accept.CONSHA should be used to encode concentrations of fishing vessel. Add CautionArea to the model to encode other hazards.okay


page 4 of 31



1 2 (3) 4 5 (6) (7)

Com

ponent


No./Annex

(e.g. 3.1)


Note(e.g. Table 1)

Type of

com-ment2



PS NGA 6.2.1.2 Figure 7te

ed

Does Figure 7 refer to the fours levels in the abstract hierarchy of feature classes listed below the figure?

If yes, then change the introduction paragraph before the list to read:

The four levels in the abstract hierarchy of feature classes depicted in Figure 7 correspond to:

Acceptokay

PS NGA 6.2.1.2 Page 23—Para 3, line 4

ed Does the phrase “this figure shows” refer to Figure 7?

If yes, change to read: Figure 7 showsAcceptokay

PS NGA 6.2.1.3 Pare 1—Line 2 ed Add comma Change to read: …recommendations, respectively,

Acceptokay

PS NGA 6.2.1.3 Figure 8ed Is Figure 8 part of 6.2.1.3?

Yes.Add a sentence in 6.2.1.3 referencing Figure 8.okay

PS ntou 6.2.1.4 Fig.9 te The attributes categoryOfMaritimeBroadcast and categoryOfradioMethods may be used to provide information required for S-127 dataset to facilitate contacting or utilizing MTM services via radio communications.It will be great if MTM services which utilize AIS SRM (safety-related message) and/or Application-Specific Messages(international as listed in IMO SN.1/Circ. 289 or regional ones ) can be encoded in the ContactDetails of S-127 dataset.

Instead of simply removing those two attributes, improve the contents of these two attributes and even the complex attribute 'radiocommunications'

The differentiation of frequency bands ( LF, MF, HF, VHF) as well as traffic types(voice, digital, telegraph, DSC) in categoryOfradioMethods may be unnecessary, since attributes such as communicationChannel, contactInstructions, and signalFrequency should be sufficient .

categoryOfMaritimeBroadcast already includes “AIS information”.okayNo change to differentiation of frequency bands – it is used in S-123.


page 5 of 31



1 2 (3) 4 5 (6) (7)

Com

ponent


No./Annex

(e.g. 3.1)


Note(e.g. Table 1)

Type of

com-ment2



In this case, the categoryOf RadioMethods should include AIS SRM and AIS ASM.

okayEnd result – no change.

PS NGA 62..1.7 Page 29—Line 1

ed Add: See Figure 12. Acceptokay

PS NGA 6.2.1.8 Page 30—Para 2

ed Add: See Figure 13. Accept/modify. Will add reference to the figure, but not in that paragraph – the figure does not show how to encode complex conditions using multiple Applicability objects.okay

PS NGA 6.2.1.8 Page 31—Para 5

ed Add: See Figure 14. Accept/modify. Will add a reference to Figure 14, but not there – that paragraph is about the itemized list that precedes it.okay

PS NGA 6.2.1.10 Para 1—Line 1

ed Change to read: Figure 16 depicts… Acceptokay


page 6 of 31



1 2 (3) 4 5 (6) (7)

Com

ponent


No./Annex

(e.g. 3.1)


Note(e.g. Table 1)

Type of

com-ment2




ed Change “Figure 18” to read “Figure 17” Acceptokay


ed Change to read: …management and is depicted in Figure 20.

Acceptokay

PS ntou 6.2.1.14 Fig.23 te The source may be from the Department of Land Administration under the Ministry of Interior or the Bureau of Energy under the Ministry of Economy

Add 'land administration' and 'energy' to the enumeration of categoryOfAuthority.

Reject.CATAUT values ‘environmental’ and ‘finance’ would appear to cover the case. The name of the agency and ministry should be encoded in attribute sourceIndication.featureName.More details on the Wiki CATAUT discussion page.Okay, the more generic we keep this list the less confusion of the end user we make. The name of the organisation can be encoded by “featureName”


page 7 of 31



1 2 (3) 4 5 (6) (7)

Com

ponent


No./Annex

(e.g. 3.1)


Note(e.g. Table 1)

Type of

com-ment2



PS NGA 6.2.1.15 Page 42—Line 3


PS JP 6.2.156.2.1.5

3rd paragraph

TE Practice time is explained in Fixed date range or Periodic date range attribute, and if the time is known, the attribute is the time, if 24hours, the attribute is blank.But in some case, the practice time is not known. What attribute value should be filled?

24h time can be explicitly encoded.Special cases such as unknown can be explained in the textContent or information attribute of MIPARE or SRVHRS.Add to encoding instructions in DCEG if agreed and modify 6.2.1.5 accordingly.Okay, appreciate the improvements of the encoding instructions








page 8 of 31



1 2 (3) 4 5 (6) (7)

Com

ponent


No./Annex

(e.g. 3.1)


Note(e.g. Table 1)

Type of

com-ment2



PS NGA 7.1.1 Table 7.1 ed Adding a comma and proper capitalization Change Scope to read: Ocean, Coastal, Ports, Harbors, and Inland Waters

Acceptokay

PS NGA 7.2.1 Para 1 Ed Grammar correction Change “carries” to read “carry” Accept/modify.“A geographic feature type carries…” because “a real world entity” is singular.okay


ed Change “in the following table.” To read “in Table 10.”

Acceptokay


ed Change “…in the table.” to read “…in Table 9.1.” Acceptokay


ed Change .”…in the table below.” to read “…in Table 9.2.”

Acceptokay


ed Change to read: “Table 10.2 lists the types of MTM datasets which may “

Acceptokay

PS NGA Table 10.2 Column 1—Row 1

ed Delete the period Accept (delete colon)okay

PS NGA Table 10.2 Column 1—row 2

ed Delete the period Accept (delete colon)okay

PS NGA Table 10.2 Column 2—Row 3—

ed Change “…are…” to “…is…” Accept


page 9 of 31



1 2 (3) 4 5 (6) (7)

Com

ponent


No./Annex

(e.g. 3.1)


Note(e.g. Table 1)

Type of

com-ment2



Line 1 okayPS JP 10.1.2

10.1010.11Etc.

ED "Shall" is used in a plain text. These should be “must”.Although this should be checked at final stage.

Check “shall”s. OK. No changes to the copyright statement, IHO front matter, or ISO definitions, though.Okay, we shouldn’t touch their domain or introduce modifications without their agreement


ed Adding a comma Change to read “…deletions, and additions…” Acceptokay


ed Change …described below.” To read described in paragraph 10.2.1.”

Accept/modify.“clause 10.2.1”okay


ed Period goes inside the closing quotation mark Changes to “…nilled.” Acceptokay

PS NGA 10.7.1 Lines 2, 3, and 4

ed Indent Lines 2, 3, and 4 Accept/modify.Indent whole list.okay

PS NGA 10.7.1 Lines 10 and 11

ed Indent Lines 10 and 11 Accept/modify.Indent whole list.


page 10 of 31



1 2 (3) 4 5 (6) (7)

Com

ponent


No./Annex

(e.g. 3.1)


Note(e.g. Table 1)

Type of

com-ment2



okayPS NGA 11.1 Para 1—

Line 2ed Change “…is described by the following…” to read

“…is described in Table 11.1 by the following…”Acceptokay

PS NGA 11.3 Para 2 ed Q: “attributes described below” - Does this refer to Figure 30?

Accept/modify.The attributes are defined in the application schema, e.g., fileReference. Will rephrase.okay


ed Delete comma Delete comma after the word “standard” Acceptokay


ed Add comma Change to read “…images, and text…” Acceptokay


ed Add comma Change to read “…replacement, and deletion).” Acceptokay


ed Add: See Table 12. Accept (12.1).okay


ed Add comma Change to read: “…picture, or application…” Acceptokay


ed Delete comma Change to read: “…file before…” Accept


page 11 of 31



1 2 (3) 4 5 (6) (7)

Com

ponent


No./Annex

(e.g. 3.1)


Note(e.g. Table 1)

Type of

com-ment2




Line 2ed Add comma Change to read “…fileReference, and…” Accept


Line 3ed Capitalization Change to read: “…S-127 Product Specification.” Accept


Line 4ed Add comma Change to read: “…definitions, and extension Accept


Line 2ed Add: “See Figure 31.” Accept


Line 7ed Add: “See Table 14.1.” Accept

okayModify. The original text has been replaced.

PS NGA Table 14.1 Header row ed Left-justify all header text Acceptokay


ed Add: “See Table 14.2.” Acceptokay

PS NGA Table 14.3 Header row ed Make all header text bold-faced Acceptokay

PS NGA 14.4 Para 1— ed Add: “See Table 14.3.” Accept


page 12 of 31



1 2 (3) 4 5 (6) (7)

Com

ponent


No./Annex

(e.g. 3.1)


Note(e.g. Table 1)

Type of

com-ment2



Line 3 okayPS NGA 14.5 Para 1—

Line 5ed Add: “See Figure 32.” Accept

okayNo longer applicable. Text has been replaced in 0.2.


ed Change to read: “…elements listed in Table 14.4. No longer applicable. Text has been replaced in 0.2.

PS NGA 15 Para 1—Line 10

ed Change: “The figure below show the…” to “Figure 33 shows the…”

Acceptokay

PS NGA 15 Para 3—Line 3

ed Change: “…feature and information instances…” to read “…feature (Figure 34) and information (Figure 35) instances…”

Acceptokay

PS NGA 15 Page 71—Para 2—Line 1

ed Change “…in the figure that follows.” To read “…in Figure 36.”

Acceptokay

PS NGA Figure 36 Caption ed Should the caption make reference to Marine Traffic Management instead of Radio Service Area?

AcceptYesokay

PS NGA 15 Page 72—Para 2—Line 1

Ed Change “The figure below shows an…” to read “figure 37 shows an…”

Acceptokay


page 13 of 31



1 2 (3) 4 5 (6) (7)

Com

ponent


No./Annex

(e.g. 3.1)


Note(e.g. Table 1)

Type of

com-ment2



DCEG

NGA 1.6, 1.7, 2.1, 2.4, 2.6.3, 2.6.5, 2.7.1, 2.9.1, 3 (multiple locations), 4.1, 4.3 (three items), 5.5 (three items), 5.6, 5.7, 5.8, 5.9, 5.10 (two items) 5.11 (three items), and 5.12

ed Use of the term “clause” when referring to other parts of this document. Highlighted in red in original document.


Accept.Will use “clause.”okay

DCEG

NGA 1.4 Table 1.3 ed Replace “TRF” with MTM Acceptokay

DCEG

NGA 2.4.3 and 2.4.13 (three items)

ed Use of the term “chapter” when referring to other parts of this document. Highlighted in red in original document.


“clause”okay

DCEG

NGA 2.5.5 edf Use of the term “sector” when referring to other parts of this document. Highlighted in red in original document.


“clause”okay

DCE NGA 2.4.8, 2.4.9, ed Use of the term “section” when referring to other What is the proper term? “clause”


page 14 of 31



1 2 (3) 4 5 (6) (7)

Com

ponent


No./Annex

(e.g. 3.1)


Note(e.g. Table 1)

Type of

com-ment2



G and 2.4.10.4 (two items)

parts of this document. Highlighted in red in original document.

Clause/Chapter/Paragraph/Sector/Section?Pick one term for consistency.

okay

DCEG

NGA 2.1 Paragraph 5—line 1

ed Add comma after “associations” Acceptokay

DCEG


ed Add comma after “curve” Acceptokay

DCEG

NGA 2.3.2 Para 1—line 1

ed Change “DCEG, that state” to read “DCEG which states”

Acceptokay

DCEG

NGA 2.4.1 Table 2.4.1 on page 11

ed Description of Abbreviation “TI” Add camma after “minute”Add period at end of sentence after “local time”

Acceptokay

DCEG

NGA 2.4.2 Line above Table 2-3 on page 12

ed Delete the word “the” Acceptokay

DCEG

NGA 2.4.3 Paragraph 2—line 3


DCEG


ed Change lowercasr “chapter” to uppercase “Chapter”

Acceptokay

DCEG


ed Add comma after “significant” Acceptokay

DCEG




page 15 of 31



1 2 (3) 4 5 (6) (7)

Com

ponent


No./Annex

(e.g. 3.1)


Note(e.g. Table 1)

Type of

com-ment2



DCEG


ed Change “Traffic Management” to read “Marine Traffic Management”

Acceptokay

DCEG



Acceptokay

DCEG

NGA 2.4.8.1 Paragraph 1—Line 1

ed Add the word “or” after Regulations Acceptokay

DCEG

NGA 2.4.8.1 Paragraph 2—line 2

ed Add the word “or” after Recommendations Acceptokay

DCEG


ed Add comma after “NonStandardWorkingDay” Acceptokay

DCEG


ed Add comma after the word “month” Acceptokay

DCEG



DCEG


ed Change “define” to read “defines”Change “allow” to read “allows”

Acceptokay

DCEG



DCEG

NGA 2.4.10.4 NGA ge Q: assume we added a third time length from 7 p.m. to 9 p.m. Am I correct in assuming the coding would be:

Yes.No action needed.


page 16 of 31



1 2 (3) 4 5 (6) (7)

Com

ponent


No./Annex

(e.g. 3.1)


Note(e.g. Table 1)

Type of

com-ment2



timeofDayStart = 080000timeofDayStart = 130000timeofDayStart - 190000timeofDayEnd = 120000timeofDayEnd = 170000timeofDayEnd = 210000

DCEG


ed Change “In the figure” to read (Figure 2” Acceptokay

DCEG


ed Change “shown in 4” to read “shown in figure 4” Acceptokay

DCEG


ed Add comma after “Regulations” Acceptokay

DCEG


ed Change “The following types of dataset may” to read “Table 2-10 shows the types of datasets which may”

Acceptokay

DCEG



Acceptokay

DCEG



Acceptokay

DCEG

NGA 2.7.1 Paragraph 5—Line 1


Acceptokay


page 17 of 31



1 2 (3) 4 5 (6) (7)

Com

ponent


No./Annex

(e.g. 3.1)


Note(e.g. Table 1)

Type of

com-ment2



DCEG



Acceptokay

DCEG


ed Change “represent” to read “represents” Acceptokay

DCEG



Acceptokay

DCEG


ed Change “The following table lists” to read “Table 2-11 lists”

Acceptokay

DCEG

NGA 3 Table ed Category of beer Change “pilsener” to “pilsner” It is from the IHO template in S-100, 11-D. No action.

DCEG


ed After the word dataset change the comma to a semi-colon

Acceptokay

DCEG

NGA 4.4 Table 4-4—INT 1 Reference—Para-graph 4—line 1

ed Add comma after “quality of position” Acceptokay

DCEG

FI 5.4 Definition te Consider updating the definition for Reportable service area, to reflect the general use of "reporting".

IHO Definition: REPORTABLE SERVICE

IHO Definition: REPORTABLE SERVICE AREA A service area including requirements for submission of information.

Action postponed to Ver. 0.3. NIPWG should approve change.


page 18 of 31



1 2 (3) 4 5 (6) (7)

Com

ponent


No./Annex

(e.g. 3.1)


Note(e.g. Table 1)

Type of

com-ment2



AREA A service feature generally involving one or more reports from the requester, including communications not strictly considered “reporting.”

Word comment with adapted revised definition added in DCEG.SRSArea and LPSArea added in response to earlier comment.

DCEG

NGA 5.5 Radio Calling-in Point

ed INT 1 Reference Box—line 3 Change the word “vessel” to read “vessels” Acceptokay

DCEG

NGA 5.7 Traffic Signal Station

ed INT 1 Reference box—Paragraph 3—line 2 Add comma after word “docking” Acceptokay

DCEG

NGA 5.13 Routeing Measures

ed Section of table on page 54—Column 2—row 5 Change type size of text “Recommended traffic lane part” to 10-point

Acceptokay

DCEG

NGA 5.13 Routing Measures

ed Section of table titled Remarks on page 55—Paragraph 2—line 1

Change the word “defined” to read “define” Acceptokay

DCEG

NGA 5.14 Waterway Area

ed Remarks—Paragraph 1—line 1 Change the word “section” to read “sections” Acceptokay

DCEG

JP 5.15 TE Some quay that follows ISPS is specified in the form of line.The geometry should have Curve geometry.

Add geometry “CURVE” Acceptokay


page 19 of 31



1 2 (3) 4 5 (6) (7)

Com

ponent


No./Annex

(e.g. 3.1)


Note(e.g. Table 1)

Type of

com-ment2



DCEG

JP 5.15 TE ISPS security level is not written in nautical publications from Japan, and it seemed there is no content in paper test data. Therefore, it is not clear how this feature will be used. Is there any example in nautical publications?

It can be given the standard treatment of missing mandatory attribute values, i.e., encoded as NULL.Will add a remark in the encoding saying this.This question should be put to NIPWG as a whole.Okay with the NULL solution and the remark.Information on ISPS level was requested by NIPWG members. So, keep it.

DCEG

NGA 5.16 Military Practice Area

ed INT 1 Reference box—Paragraph 2—line 2 Add comma after the word “torpedo” Acceptokay

DCEG

NGA 5.16 Military Practice Area

ed INT 1 Reference box—Paragraph 9—line 2 Add comma after the word “beacons” Acceptokay

DCEG

NGA 5.16 Military Practice

ed INT 1 Reference box—Paragraph 10—line 1 Change word “minelaying” to read “mine-laying” Acceptokay


page 20 of 31



1 2 (3) 4 5 (6) (7)

Com

ponent


No./Annex

(e.g. 3.1)


Note(e.g. Table 1)

Type of

com-ment2



AreaDCEG

NGA 5.18 Restricted Area Navigational

ed INT 1 Reference box—Paragraph 3—line 1 Change to word “apply” to read “applies” Acceptokay

DCEG

NGA 5.19 Underkeel Clearance Allowance Area

ed Remarks box—Paragraph 3—line 1Remarks box—Paragraph 4—line 1

Change the word “ships” to read “ship’s”This indicates the proper possessive of the word and applies to both locations

Acceptokay

DCEG

NGA 5.20 Underkeel Clearance Manage-ment Area

ed Remarks box—paragraph 1—line 1 Change to words “encode a underkeel” to read “encode an underkeel”

Acceptokay

DCEG

NGA 5.21 Piracy Risk Area

ed Remarks box on page 67—line 7 Change to words “must be using a” to read “must be done using a”

Acceptokay

DCEG

JP 5.22 GE It is difficult to think this is good or not, because there is no example or how this feature is used. What kind of area (spatial) is expected to be covered? and also, what range of “refuge” information (not about the spatial extent of area) will be provided using this feature?Is such target information expressible with certain geographical feature?

An example and some material have been added in the DCEG. NIPWG is invited to discuss this matter. Comments should be submitted as comments on Ver. 0.2.

DCEG

NGA 5.23 Vessel Traffic

ed Remarks box on page 70—paragraph 2—line 1 Add comma after the word “anchoring” Acceptokay


page 21 of 31



1 2 (3) 4 5 (6) (7)

Com

ponent


No./Annex

(e.g. 3.1)


Note(e.g. Table 1)

Type of

com-ment2



Service Area

DCEG

NGA 5.23 Vessel Traffic Service Area

ed Remarks box on page 70—paragraph 4—line 3 Add comma after the word “Traffic)” Acceptokay

DCEG


ed Remarks box on page 70—paragraph 5—line 2 Change “serviceAccessProcedure” to bold-face Acceptokay

DCEG


ed Remarks box on page 70—paragraph 6—line 2 Change “requirementsForMaintenanceOfListeningWatch” to bold-faced

Acceptokay

DCEG


ed Change “type are allowable” to read “type is allowable”

Acceptokay

DCEG

JP 7.8 Call name TE In some case, Call name in each language is different.The multiplicity (0.1) should be changed to (0.*)

Change multiplicity 0.1 to 0.* Accept, but modify. Add language attribute to CONDET and associate multiple instances of CONDET.

DCEG

JP 7.8 All TE When Nautical publications are published in multiple language (Japanese and English), how the attributes should be filled in is unknown.

Accept, but each language can have a separate CONDET


page 22 of 31



1 2 (3) 4 5 (6) (7)

Com

ponent


No./Annex

(e.g. 3.1)


Note(e.g. Table 1)

Type of

com-ment2



object (see the previous row).

DCEG

JP 7.9 Noticetime/ operation

GE It is difficult to use whether max or min in the case of pre entry report. It will be good to explain in Remarks column.

Write how to use in Remarks Accept. Will formulate text for encoding remarks.okay

DCEG

NGA 7.12 Applicability ed Remarks section—Paragraph 13—line 1Remarks section—Paragraph 16—line 1

Change “vessels with LOA with more than” to read “vessels with an LOA greater than”Note—This change applies in both locations.

Acceptokay

E (Val.)

NGA 3.2 ed Use of the term “section” when referring to other parts of this document. Highlighted in red in original document.


“clause”okay

E (Val.)

NGA Annex A 1.1 ed Use of the term “section” when referring to other parts of this document. Highlighted in red in original document.


“clause”okay

E (Val.)

NGA Annex A 2.0 (two items)

ed Use of the term “section” when referring to other parts of this document. Highlighted in red in original document.


“clause”okay

E (Val.)

NGA 3.1 Title ed Change uppercase “Classification” to read lowercase “classification”

Acceptokay

E NGA 3.1 Table 3.1 ed Grammar correction Change “make a MTM” to read “make an MTM” Accept1 CO = Contributing Organisation (HOs should use 2 character codes e.g. FR AU etc.)2 Type of comment: ge = general te = technical ed = editorial3 Whilst not compulsory, comments are more likely to be accepted if accompanied by a proposed change. NOTE Columns 1, 2, 4, 5 are compulsory.

page 23 of 31



1 2 (3) 4 5 (6) (7)

Com

ponent


No./Annex

(e.g. 3.1)


Note(e.g. Table 1)

Type of

com-ment2



(Val.)

okayE (Val.)

NGA 3.2 Paragraph 1 ed Should “Section 9 or the” be changed to read “Section 9 of the”

Yesokay

E (Val.)

NGA 3.2 Table 3.1 ed Header row—column 5 Delete colon Acceptokay

E (Val.)

NGA 3.2 Table 3.2 on Page 4

ed Row 103—column 4Row 104—column 3Row 105—column 2Row 107—columns 2, 3, and 4Row 108—columns 3 and 4Row 113—columns 2, 3, and 4Row 114—columns 2 and 4

Add closing period Acceptokay

E (Val.)

NGA 3.2 Table 3.2 on page 4

ed Row 103—column 4 Delete word “meta” Reject. these are meta type features.

E (Val.)


ed Row 104—column 2 Change uppercase “Present” to lowercase “present”

Acceptokay

E (Val.)


ed Row 123—column 2—line 1Row 124—column 2—line 1Row 125—column 2—line 1

Delete comma Acceptokay

E (Val.)

NGA 3.2 Table 3.2 Ed Row 116—column 2 Add closing period Accept


page 24 of 31



1 2 (3) 4 5 (6) (7)

Com

ponent


No./Annex

(e.g. 3.1)


Note(e.g. Table 1)

Type of

com-ment2



NGA 3.2on Page 5Table 3.2 on Page 5

edRow 117—column 2Row 119—column 3Row 120—columns 3 and 4Row 122—column 2Row 126—column 4

Add closing periodokay

E (Val.)


ed Row 128—column 2Row 133—column 3Row 134—column 3Row 136—column 4Row 137—column 4

Add closing period Acceptokay

E (Val.)


ed Row 132—column 2Row 135—column 2Row 136—column 2Row 137—column 2Row 138—column 2Row 139—column 2

Delete comma Acceptokay

E (Val.)


ed Row 134—column 2 Change “ServicesHours has more” to read “Servicehours with more”

Acceptokay

E (Val.)


Ed Row 140—column 4Row 141—column 4Row 143—column 3Row 144—column 4

Add ending period Acceptokay


page 25 of 31



1 2 (3) 4 5 (6) (7)

Com

ponent


No./Annex

(e.g. 3.1)


Note(e.g. Table 1)

Type of

com-ment2




ed

Row 147—column 2Row 148—columns 2 and 4Row 149—column 2 Add ending period

E (Val.)


ed Row 141—column 2Row 142—columns 2 and 3

Change “file, does” to read: “file that does” Acceptokay

E (Val.)


ed Row 144—column 3Row 146—column 3Row 147—column 3

Change uppercase “Populated” to lowercase “populated”

Acceptokay

E (Val.)

NGA Table 3.2row 144

ed Begin “Null” with a lower case letter Reject. “Null” has specific significance in these tests.I agree with the rejection.

E (Val.)


ed Row 150—columns 2 and 4Row 151—column 4Row 152—columns 2 and 4Row 153—columns 2 and 4Row 154—columns 2 and 4Row 155—column 2Row 158—column 2Row 167—columns 2 and 4

Add ending period Acceptokay


page 26 of 31



1 2 (3) 4 5 (6) (7)

Com

ponent


No./Annex

(e.g. 3.1)


Note(e.g. Table 1)

Type of

com-ment2



E (Val.)


ed Row 176—column 3 Change lowercase “underkeel” to read uppercase “Underkeel”

Acceptokay

E (Val.)


ed Row 176—column 4 Change “lease” to read “least” Acceptokay

E (Val.)

NGA

NGA

3.2

3.2

Table 3.2 on page 9

Table 3.2 on page 9

ed

ed

Row 169—column 3Row 170—columns 2, 3, and 4Row 171—columns 2, 3, and 4Row 172—columns 2, 3, and 4Row 173—columns 2, 3, and 4Row 176—columns 2, 3, and 4Row 177—columns 2 and 3Row 178—columns 2, 3, and 4

Add ending period

Add ending period

Acceptokay

E (Val.)

NGA Annex A—Section 1.1.1

Paragraph 1—line 2

ed Add comma after “single Line” Acceptokay

E (Val.)

NGA Annex A—Section1.1.1


ed Change “it’s” to read “its” Acceptokay

E (Val.)



ed Change lowercase “points” to uppercase “Points” Is this correct?

Reject.“Point” means a point primitive in the dataset, “point” means a generic point which may not be a distinct spatial


page 27 of 31



1 2 (3) 4 5 (6) (7)

Com

ponent


No./Annex

(e.g. 3.1)


Note(e.g. Table 1)

Type of

com-ment2



object in the dataset.Okay with the rejection

E (Val.)



ed Change lowercase “points” to uppercase “Points” Is this correct?

Reject.“Point” means a point primitive in the dataset, “point” means a generic point which may not be a distinct spatial object in the dataset.Okay with the rejection

E (Val.)



ed Add ending period Acceptokay

E (Val.)


Table ed Row 3—column 2 Change lowercase “outer” to read uppercase “Outer”

Acceptokay

E (Val.)

NGA Annex A—Section 1.1.2

Line 12 ed Add comma after “LineStrings” Acceptokay

E (Val.)

NGA Annex A—Section 1.2


ed Add comma after “COVERED_BY” Acceptokay


page 28 of 31



1 2 (3) 4 5 (6) (7)

Com

ponent


No./Annex

(e.g. 3.1)


Note(e.g. Table 1)

Type of

com-ment2



E (Val.)


Paragraph 1—lines 2 and 3

ed Add commas after “Line” and after “geometry” Acceptokay

E (Val.)



ed Add comma after “vertexes” Acceptokay

E (Val.)


Paragraph 5—lines 2 and 4

ed Should “vertexes” be changed to “vertices” Acceptokay

E (Val.)


Line 1 ed Delete comma after “section” Acceptokay

E (Val.)


Line 1 on Page 14

ed Should “S-58” read “S-57” Changed to read S-127 Validation Checks.

E (Val.)


Line 15 on Page 14

ed Add comma after “Point/Area” Acceptokay

E (Val.)


Page 15—Upper graphic

ed Change format of caption to “Ariel 10-point boldface”

Acceptokay

E (Val.)


Page 16—last line

ed Change “applies Line/Line” to read “applies to Line/Line”

Acceptokay

E (Val.)


Page 18—Graphic

ed Graphic needs a caption Acceptokay


page 29 of 31



1 2 (3) 4 5 (6) (7)

Com

ponent


No./Annex

(e.g. 3.1)


Note(e.g. Table 1)

Type of

com-ment2



E (Val.)


Page 19—upper graphic

ed Change caption to read: “Example of two COINCIDENT geometric LINES” (Ariel 10-point boldface)

Acceptokay

E (Val.)


Page 19—lower graphic

ed Add caption:“Examples of COINCIDENT objects”(Ariel 10-point boldface)

Acceptokay

E (Val.)


Page 19—last paragraph

ed Add comma after “be true” and after “”or TOUCHES”

Acceptokay

Testdata

JP GE I think paper test data should be projected to GML test data. But some content such as Ice transit, ISPS report, and Emergency refuge is not written in GML test data. And whether such format is appropriate or not is clear.(1)The information of whether the content of paper is projected to S-127 GML or not is useful to understand whether the S-127 PS is well reflected or not.(2)Additionally, GML test data introduce how the attributes or position will be encoded. It will help consider whether the method to input is simple/easy or not.

The example will be expanded. Part of the test sample, e.g., the AMVER portion, belongs in an S-123 dataset and will not be converted for the S-127 dataset.DCEG can also provide some guidance about what should not be converted and about geometry.Action pending for Ver 0.3.

Testd JP All feature TE The latitude and longitude of S-127 test data should Latitude and Longitude is changed to in 7 decimal Accept.


page 30 of 31



1 2 (3) 4 5 (6) (7)

Com

ponent


No./Annex

(e.g. 3.1)


Note(e.g. Table 1)

Type of

com-ment2



ata type be written in the 7 decimal places.Though this check should be done, when nearly finished.

places. okay


page 31 of 31

Date post:	30-Dec-2018
Category:	Documents
Upload:	buikiet
View:	214 times
Download:	0 times

€¦ · Web viewReplace “TRF” with MTM. Accept . okay. ... Word comment with adapted revised...

Documents