search

gephi / gexf

GEXF Format Specifications
https://gexf.net/
Creative Commons Attribution 4.0 International
31 stars 6 forks source link

Is gexf 1.2 really deprecated? #11

Closed greebie closed 2 years ago

greebie commented 6 years ago

When using Gephi, I receive warnings that 1.2draft is deprecated. However, it also appears that 1.3 is a "work in progress."

Could you please advise on the appropriate way to produce a gexf for importing into Gephi? Thanks.

eduramiba commented 6 years ago

Hi, You can still use gexf 1.2, changes are not many, just make sure to look at import warnings.

I'm not sure the specification is available yet, but see this for examples https://github.com/gephi/gephi/issues/1152

dwcaraway commented 6 years ago

1.2 should not be deprecated until 1.3 is in widespread use. The GEXF support libraries in the community are still using 1.1 and 1.2 and will likely not change until the 1.3 spec is published. Similar issue at https://github.com/gephi/gephi/issues/2019

greebie commented 6 years ago

I agree with @dwcaraway. Deprecation implies that I should upgrade to something newer. When there is nothing to upgrade to, things get confusing and can result in problems.

kortschak commented 5 years ago

I've just spent a day covered in XML to put together a parses for GEXF for Go and as part of my testing I've written out GEXF from the examples using Gephi. This breaks the parser because it writes 1.3 (which is mentioned nowhere on gefx.net) and Go's XML handling requires namespace matching. It would be nice to have communication on things like this readily available from the canonical source (presumably gexf.net).

mbastian commented 2 years ago

Closing this issues as it has been resolved. All GEXF 1.3 specifications are now official and accessible online.

We recommend all users and tools to adapt to the 1.3 schema. See details in the release notes.