Talk:NtM Chart-correction XML

Images and Symbols

Format

LS: Italy prefers to have them in a true type font format (like Arial, Times New Roman etc). They can be easily managed by all the production systems, while I see difficulties of tiff and svg formats.
How to display a wreck with the least depth known? With a tiff image of a general wreck and beside the text with the depth value and Wk abbreviation?

JS-F: The True Type Format could be seen as along term goal. Germany could possibly provide a tool which generates TIFF images for symbols with variable values on the fly. However, the XML should be written in a way that the symbols format is of less relevance. More inportant is to check the IHO capability to host a set of symbols and the provision of a "text description" of each symbol. The latter could be used as a universal translation tool between different symbol libraries.

LS: I agree with Jens about not going to deep into symbols (format and so on): HO can decide to use one or the other. At the moment I guess that we come to a common structure of the XML for the “core of a chart notice” (i.e. attributes of ChartCorrectionContent element in Stephan’s UML Diagram). My idea is to have the following schema/tags:

Language 1 Symbol Textual description Additional text Language 2 Symbol Textual description Additional text Language n Symbol Textual description Additional text

The “Symbol+Textual description” make the part Jens explained in his email letter b). The Symbol will consist in one of the following type: FILE or TEXT. The FILE is ok either for tiff images or SVG file (there are XML files). The TEXT will be ok for True Type Font (actually it is only text, formatted: i.e. 1). HOs can choose where they need to use: 1) only Symbol:  or 2) Symbol+Textual description: Racon(B) or Fl(2)G3s

3) only Textual description: a lighted spherical safe buoy and a radio transponder beacon

4) Symbol+Additional text: joining the followings positions…

or the other possible combinations of elements.

SE: A. Based on Ludovicos explanation of how TTF is used, I made a small update to the UML- diagram at; http://wp12183585.server-he.de/npubwiki/wiki/index.php/NtM_Chart-correction_XML#Format By the update, a symbol can be based on either TTF or Image. Hopefully I understood correctly. If not, let me know.

Q: Do we need color indication for TTF? Q: Is TTF symbol always one character, or could it be a longer string?

B. ‘Textual description’ in the sample below could be either a chart label or an explanation. We separate text fields based on whether it is text that is actually shown on the chart (and normally does not need translation, like names on charts, light characteristics etc.), or a description that needs to be translated. In the UML this is indicated by the fact that only some strings are type “MultilangString”.

My suggestion would be to separate descriptions from chart labels, like; • ChartLabel (no translation) o Fl(2)G3s o Racon(B) • TextualDescription (needs translation) o a lighted spherical safe buoy and a radio transponder beacon

For visual display the empty fields could be collapsed, so this would mainly be a way to keep a structure of the data.

..on the other hand this is further making me think that the easiest way would be to provide only one language in each file.

C. Formatting of the chart labels / textual descriptions. The Racon (B) in magenta caught my attention from the sample below. Should we allow some kind of text-formatting within the textual descriptions? HTML- tags within the XML provide some difficulties if translated for use in systems without HTML- support. On the other hand, formatting of text using different colors could improve readability. Is there a need for us to define / restrict the allowed ways of formatting text?