Currently, two SBGN files are generated for the same map. This was a temporary solution to the fact that some formats for elements’ identifiers in yEd were seen as invalid identifiers by some SBGN-support tools (such as SBGN-ED, VANTED). For example, in yEd, there are cases when glyph ids contain “::” (e.g. n0::n1) which is not accepted in SBGN-ED, VANTED etc. Thus, one SBGN file contained elements with ids like in the initial yEd-specific GraphML file and another with elements with ids slightly modified (e.g. “::” would be replaced by “__”).
However, this approach may be confusing and may create difficulties for managing two files referring to the same SBGN map.
Solution here would be generating an unique SBGN file, (with modified ids for elements if needed), which can be opened in SBGN-support softwares, including SBGN-ED and VANTED.
Currently, two SBGN files are generated for the same map. This was a temporary solution to the fact that some formats for elements’ identifiers in yEd were seen as invalid identifiers by some SBGN-support tools (such as SBGN-ED, VANTED). For example, in yEd, there are cases when glyph ids contain “::” (e.g. n0::n1) which is not accepted in SBGN-ED, VANTED etc. Thus, one SBGN file contained elements with ids like in the initial yEd-specific GraphML file and another with elements with ids slightly modified (e.g. “::” would be replaced by “__”).
However, this approach may be confusing and may create difficulties for managing two files referring to the same SBGN map.
Solution here would be generating an unique SBGN file, (with modified ids for elements if needed), which can be opened in SBGN-support softwares, including SBGN-ED and VANTED.