You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I understand that GEXF's design is mostly done around Gephi, nonetheless, it may be a good idea to try to keep track of other Graph XML formats providing similar support. This could bring ideas about needed/desired features for both GEXF and Gephi. Here are a few examples:
Hello!
I'd like to mention another format, .dgs, used by the Java library GraphStream. Like .gexf, (and unlike all the formats you've listed?), it allows encoding graph dynamics. I'd say it's main strong suit is streamability (i.e. it can be used for online algorithms and transmission), plus it's more succinct than XML-based formats.
However, it doesn't allow specifying dynamics using intervals - it's always "next timestep: this and that happens", never e.g. "this edge exists from timestamp1 to timestamp2". It also lacks the other "advanced concepts" (hierarchy, phylogeny structure) which can be handily represented in .gexf. In general, I find .gexf much more readable + easily (machine-)parsable and would (did) choose it for offline storage/transmission.
edit: oops, I overlooked that you specified "Other Graph XML formats". .dgs is not XML based at all.
I understand that GEXF's design is mostly done around Gephi, nonetheless, it may be a good idea to try to keep track of other Graph XML formats providing similar support. This could bring ideas about needed/desired features for both GEXF and Gephi. Here are a few examples:
XML formats used in Phylogenetics (some interesting features to consider for GEXF)
The text was updated successfully, but these errors were encountered: