-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SBGN-ML interoperability: Glyph IDs must not contain numeric as first digit #679
Comments
@lknegendorf Thanks for the feedback. If you create a map in Newt, the IDs for the glyphs and arcs should be starting with "nwtN_" for glyphs and "nwtE_" for arcs such as "nwtN_46cfbb24-c95b-4816-9e8a-2ae2c39bab1f". |
@ugurdogrusoz Thanks for your reply. |
Interesting! Were the maps with this problem constructed completely manually using Newt? Or were they perhaps partially taken from somewhere else and modified in Newt? |
If it was completely constructed in Newt, when was it first started? Looks like we changed the IDing mechanism (start with "nwt") a couple of years ago and it shouldn't be possible to create glyphs with such IDs any longer. |
Yes, the maps were constructed completely manually in Newt, we started the construction in June 2021. |
That's really odd. When you save your maps, do you use "File > Export > SBGNML Plain" or just "File > Save.." (.nwt)? |
We used both, but the problem I describe happends just when exporting it via "File > Export > SBGNML Plain" and then trying to reimport it into another tool (we used Vanted/SBGN-ED). |
@hasanbalci identified the cause of this (when cloning graph objects we neglect to prepend "newt_N/E", will fix it sometime. |
Hi,
we created a SBGN PD map in Newt and wanted to validate the exchangeability of the map in other tools supporting SBGN. We exported it as SBGN-ML version 0.2 and tried to import the SBGN-ML into VANTED (v2.8) with the corresponding SGBN-ED plugin (v1.6). This attempt throws a cvc-datatype-valid.1.2.1 exception.
We recognized, that glyph IDs with numerical value as first digit are not compatible with this tool. A manual renaming of all such glyph IDs in the SBGN-ML solved the issue for us.
Just wanted to let you know.
Cheers!
The text was updated successfully, but these errors were encountered: