On 02/10/2013 01:51 PM, tcb wrote:
> I suppose I would be much happier with the complexity of graphml if it
> could guarantee seamless transfer of graphs between different tools. I
> would like to be able to work in graph-tool, networkx and occasionally
> some others (gephi perhaps) without having to maintain a bunch of
> conversion scripts.

I find this desirable as well, but it won't happen without some
coordination between the projects. In the case of networkx and
graph-tool, this should probably happen, since there is interest on both
sides, and it is not a very difficult problem. In the case of gephi, I
expect them to be interested as well. At the very least it should be
easy for them to simply ignore graphml types which they to not
understand, such as vectors. I don't use gephi much, but I tried
importing graphml files generated with graph-tool some time ago, and it
seemed to work as expected.

> I'm not sure how much effort is warranted to get complete support- I
> haven't needed to store pickled python objects yet, so I'll stick with
> the vector_* and see how it goes with that first.

Yes, this is more important than the pickled object type. However, I may
be able to contribute with something towards full compatibility.


> For working with multiple tools I am leaning towards a json
> approach. The networkx node_link format is quite useful:
>
>   
> http://networkx.github.com/documentation/latest/reference/readwrite.json_graph.html
>
> and extremely easy to work with (at least for my purposes). You can
> easily encode pretty much every type of data. For graph-tool you would
> just need to include a small bit of information about the property
> maps, which networkx et al can easily ignore.

Json may be interesting, but again, there must be an agreement on how to
encode the data. It seems to me one would simply replace xml for json,
and one would still need to define a graphml equivalent for it.

I have the following questions:

   Is there any documentation on how exactly is the networkx graph
   stored as json, other than looking at the source code?

   Are there other programs which currently read/write the same format
   used by networkx?

   Can you parse it with Python in an event-based manner (this is
   important for large graphs)? Is this done in networkx?

Cheers,
Tiago


--
Tiago de Paula Peixoto <[email protected]>

Attachment: signature.asc
Description: OpenPGP digital signature

_______________________________________________
graph-tool mailing list
[email protected]
http://lists.skewed.de/mailman/listinfo/graph-tool

Reply via email to