PS NGA 3.1, 4.1, 4.2, 5 (two 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. What is the proper term? Clause/Chapter/Paragraph/Sector/Section? Pick one term for consistency. Reject. Only one 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 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. What is the proper term? Clause/Chapter/Paragraph/Sector/Section? Pick one term for consistency. Accept. Will use “clause” okay PS NGA 1.1 Line 9 ed Add 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… Accept PS NGA 3.1 Line 24 ed On page 8--Add comma Change to read: …end use, or other… Accept PS NGA 3.2 Line 8 teed Add acronym for Marine Traffic Management Add: MTM Marine Traffic Management Accept 3,
“shown below” -> “in this clause” – given that the PS will use “clause” okay PS NGA 6.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 features SRS port service Multiplicity of category attribute in VTSArea made 0..*. Listed values for SRS and LPS removed from category attribute.. PS ntou 6.2.1.1 Paragraph 1 Fig.4 & 5 te Marine 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 PS NGA 6.2.1.2 Figure 7 te 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: Accept okay
“A geographic feature type carries…” because “a real entity” is singular. okay PS NGA 7.2.5.1 Para 1 ed Change “in the following table.” To read “in Table 10.” Accept okay PS NGA 9.3 Para 1 ed Change “…in the to read “…in Table 9.1.” Accept okay PS NGA 9.4 Para 3 ed Change .”…in the table below.” to read “…in Table 9.2.” Accept okay PS NGA 10.1.2 Para 2 ed Change to read: “Table 10.2 lists the types of MTM datasets which may “ Accept okay PS NGA Table 10.2 Column 1 ed Delete the period Accept (delete colon) okay PS NGA Table 10.2 Column 2 ed Delete the period Accept (delete colon) okay PS NGA Table 10.2 Column 1 ed Change “…are…” to “…is…” Accept okay PS JP 10.1.2 10.10 10.11 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 row Row
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 PS NGA 11.4 Para 3 ed Delete Delete comma after the word “standard” Accept okay PS NGA 11.4 Para 6 ed Add comma Change to read “…images, and text…” Accept okay PS NGA 11.6 Para 3 ed Add Change to read “…replacement, and deletion).” Accept okay PS NGA 12.1 Para 6 ed Add: See 12. Accept (12.1). okay PS NGA 12.4 Para 3 ed Add comma Change to read: “…picture, or application…” Accept okay PS NGA 12.4 Para 5 ed Delete comma Change to read: “…file before…” Accept okay PS NGA 12.4 Para 2 ed Add comma Change to read “…fileReference, and…” Accept okay
NGA 2.4.8.1 Paragraph 1—Line 1 ed Add the word “or” after Regulations Accept okay NGA 2.4.8.1 Paragraph 2—line 2 ed Add the word “or” after Recommendations Accept okay NGA 2.4.8.5 Paragraph 1—line 4 ed Add comma after “NonStandardWorkingDay” Accept okay NGA 2.4.10 Paragraph 1—line 4 ed Add comma after the word “month” Accept okay NGA 2.4.10.2 Paragraph 1—line 5 ed Add comma after the word “month” Accept okay NGA 2.4.10.2 Paragraph 1—line 7 ed Change “define” to read “defines” Change “allow” to read “allows” Accept okay NGA 2.4.10.2 Paragraph 4—line 2 ed Add comma after the word “month” Accept okay 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: timeofDayStart = 080000 timeofDayStart = 130000 timeofDayStart - 190000 timeofDayEnd = 120000 timeofDayEnd = 170000 Yes. No action needed.
timeofDayEnd = 210000 NGA 2.5.1 Paragraph 3—line 2 ed Change “In the figure” to read (Figure 2” Accept okay NGA 2.5.4.2 Paragraph 4—line 4 ed Change “shown in 4” to read “shown in figure 4” Accept okay NGA 2.5.5.3 Paragraph 1—line 1 ed Add comma after “Regulations” Accept okay NGA 2.6.1 Paragraph 2—line 1 ed Change “The following types of dataset may” to read “Table 2-10 shows the types of datasets which may” Accept okay NGA 2.6.3 Paragraph 1—line 1 ed Change “Traffic Management” to read “Marine Traffic Management” Accept okay NGA 2.6.7 Paragraph 1—line 1 ed Change “Traffic Management” to read “Marine Traffic Management” Accept okay NGA 2.7.1 Paragraph 5—Line 1 ed Change “Traffic Management” to read “Marine Traffic Management” Accept okay NGA 2.8 Paragraph 1—line 1 ed Change “Traffic Management” to read “Marine Traffic Management” Accept okay NGA 2.8 Paragraph 2—line 5 ed Change “represent” to read “represents” Accept okay
response to earlier comment. NGA 5.5 Radio Calling-in Point ed 1 Box—line 3 Change the word “vessel” to read “vessels” Accept okay NGA 5.7 Traffic Signal Station ed INT 1 Reference box—Paragraph 3—line 2 Add comma after word “docking” Accept okay 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 Accept okay NGA 5.13 Routing Measures ed Section of table titled Remarks on page 2—line 1 Change the word “defined” to read “define” Accept okay NGA 5.14 Waterway Area ed Remarks—Paragraph 1—line 1 Change the word “section” to read “sections” Accept okay JP 5.15 TE Some quay that follows ISPS is specified in the form of line. The geometry should have geometry. Add geometry “CURVE” Accept okay JP 5.15 TE ISPS security 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.
Service Area NGA 5.23 Vessel Traffic Service Area ed Remarks box on page 70—paragraph 5—line 2 Change “serviceAccessProcedure” to bold-face Accept okay NGA 5.23 Vessel Traffic Service Area ed Remarks box on page 70—paragraph 6—line 2 Change “requirementsForMaintenanceOfListeningWatch” to bold-faced Accept okay NGA 6.1.1 Paragraph 3—line 1 ed Change “type are allowable” to read “type is allowable” Accept okay 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. 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 object (see the previous row). JP 7.9 Noticetime / operation GE It is difficult to use whether max or min in the case of pre report. It will be good to explain in Remarks column. Write how to use in Remarks Accept. Will formulate text for encoding remarks.
okay E (Val.) NGA 3.2 Table 3.2 on Page 4 ed 103—column 4 Row 104—column 3 Row 105—column 2 Row 107—columns 2, 3, and 4 Row 108—columns 3 and 4 Row 113—columns 2, 3, and 4 Row 114—columns 2 and 4 Add closing period Accept okay E (Val.) NGA 3.2 3.2 on page 4 ed Row 103—column 4 Delete word “meta” Reject. these are meta type features. E (Val.) NGA 3.2 3.2 on page 4 ed Row 104—column 2 Change uppercase “Present” to lowercase “present” Accept okay E (Val.) NGA 3.2 Table 3.2 on page 5 ed Row 123—column 2—line 1 Row 124—column 2—line 1 Row 125—column 2—line 1 Delete comma Accept okay E (Val.) NGA NGA 3.2 3.2 Table 3.2 on Page 5 Table 3.2 on Page 5 Ed ed Row 116—column 2 Row 117—column 2 Row 119—column 3 Row 120—columns 3 and 4 Row 122—column 2 Row 126—column 4 Add closing period Add closing period Accept okay
E (Val.) NGA 3.2 Table 3.2 on Page 6 ed Row 128—column 2 Row 133—column 3 Row 134—column 3 Row 136—column 4 Row 137—column 4 Add closing period Accept okay E (Val.) NGA 3.2 Table 3.2 on Page 6 ed Row 132—column 2 Row 135—column 2 Row 136—column 2 Row 137—column 2 Row 138—column 2 Row 139—column 2 Delete comma Accept okay E (Val.) NGA 3.2 Table 3.2 on page 6 ed Row 134—column 2 Change “ServicesHours has more” to read “Servicehours with more” Accept okay E (Val.) NGA NGA 3.2 3.2 Table 3.2 on page 7 Table 3.2 on page 7 Ed ed Row 140—column 4 Row 141—column 4 Row 143—column 3 Row 144—column 4 Row 147—column 2 Row 148—columns 2 and 4 Row 149—column 2 Add ending period Add ending period Accept okay E (Val.) NGA 3.2 Table 3.2 on page 7 ed Row 141—column 2 Row 142—columns 2 and 3 Change “file, does” to read: “file that does” Accept okay
E (Val.) NGA Annex 2.0 1 on Page 14 ed Should “S-58” read “S-57” Changed to read Validation Checks. E (Val.) NGA 2.0 15 on Page 14 ed Add comma after “Point/Area” Accept okay E (Val.) NGA Annex 2.0 Page graphic ed Change format of caption to “Ariel 10-point boldface” Accept okay E (Val.) NGA Annex 2.0 Page line ed Change “applies Line/Line” to read “applies to Line/Line” Accept okay E (Val.) NGA 2.0 Page ed Graphic needs a caption Accept okay E (Val.) NGA 2.0 Page graphic ed Change caption to read: “Example of two COINCIDENT geometric (Ariel 10-point boldface) Accept okay E (Val.) NGA Annex 2.0 Page graphic ed Add caption: “Examples of COINCIDENT objects” 10-point boldface) Accept okay E (Val.) NGA Annex 2.0 Page paragraph ed Add after “be true” and after “”or TOUCHES” Accept okay 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 The example will be expanded. Part of the test sample, e.g., the
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. 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. JP All feature type TE The latitude and longitude of S-127 test data should be written in the 7 decimal places. Though this check should be done, when nearly finished. Latitude and Longitude is changed to in 7 decimal places. Accept. okay