Specific syntax for conversion in textual attribute

[Christian-Shom]

During yesterday meeting, Friedhelm suggested that a standardized specific syntax (ex. use of semicolon) could be used in S-57 textual attributes (typically INFORM/NINFOM) to drive conversion to S-101.
The idea was supported by the subgroup, and it was agreed to open an issue to discuss on the various options.
As a base for discussion, an example would to populate INFORM on a CTNARE = "Discoloured water; Navigate with caution in this area."
The text string before the semicolon "Discoloured water" will be used by the converter to create S-101 Feature Discoloured water, and the text string after the semicolon "Navigate with caution in this area." will be transferred in the sub-attribute text of complex attribute information.
We now wait for comments/alternative proposals.

[Richard-Fowle]

As semicolon may already be present in the text contained within the attribute INFORM, I think that it may be better to enclose the conversion text within square or curly brackets e.g '[Discoloured water] Navigate with caution in this area.' or '{Discoloured water} Navigate with caution in this area'

[HermanSchouten]

Taking into account that backwards conversion from S-101 to S-57 will be done as well (Annex C) a specific Syntax must be in place. The conversion mapping has to know what to fill in the INFORM when doing conversion from S-101 to S-57 and should convert other information to INFORM too.
The placement of that specific syntax within the INFORM field seems quite important for backwards conversion as well and should match with conversion from S-57 to S-101. It seems that quite some HO will prepare their current data for conversion to S-101 data. Wouldn't it be sufficient to put the conversion text in the beginning of the INFORM attribute, and set it apart from other information by a semicolon.

[Christian-Shom]

I tend to agree with Richard's suggestion to use [ or {.

Another extended example would be to use such characters for local magnetic anomalies. Having INFORM populated with "{From [-27] degrees to [3] degrees}" could help the converter:

• Populate magnetic anomaly value1 = 27 and reference direction1 = 13 (west)
• Populate magnetic anomaly value2 = 3 and reference direction2 = 5 (east)
• Not retain the entire text string between the curly brackets for conversion into S-101 information attribute.

I don't think we should change the guidance in the UOC, but only in the Guidance document, for specific population of INFORM to help the automated conversion.

[abinashi-d]

Regardless of the delimiter we use, if white spacing or case sensitivity is required, the guidance should also include that, otherwise automatic conversion will need to make assumption such as case insensitivity and will strip off any white space between and around. So, Discoloured water , DISCOLOURED Water and discoloured Water will be treated same.