Table 3.
Output → Input↓ |
IUPAC | KCF | LINUCS | Linear Code | GlydeII | GlycoCT |
---|---|---|---|---|---|---|
IUPAC | RINGS | GLYCOSCIENCES.de, GlycomeDB, GlycanBuilder |
Glycan Builder | GlycomeDB, Glycan Builder | GlycomeDB, UniCarbKB*, Glycan Builder |
|
KCF | UniCarbKB* | RINGS, GlycomeDB |
RINGS | GlycomeDB, RINGS |
GlycomeDB, RINGS | |
LINUCS | GLYCOSCIENCES.de | RINGS | Glycan Builder | GlycomeDB, Glycan Builder | GlycomeDB, Glycan Builder |
|
Linear Code | RINGS | GlycomeDB, GlycanBuilder | GlycomeDB, Glycan Builder |
GlycomeDB, Glycan Builder |
||
Glyde II | - | RINGS | GlycomeDB | - | GlycomeDB | |
GlycoCT | UniCarbKB* | RINGS | GlycomeDB, GlycanBuilder |
Glycan Builder | GlycomeDB, Glycan Builder |
Summary of existing software for parsing and translating the most popular formats (partly illustrated in Figures 1 and 2) and the web resource (described in Table 2) where the tool can be run or downloaded. For instance, a LINUCS (Figure 2A) structure can be translated to KCF (Figure 2E) in the RINGS website. Input formats are listed in the rows, and the output formats in the columns. The asterisk indicates that the parsers/translators are available on request but not directly accessible yet as on other websites.