Steve Pietrowicz I'm adding a prototype of a generic DAX generator to my code base. It's not "plugged in" yet but I would appreciate any remarks regarding its design and functionalities it may be missing e.g. from the perspective of the campaign manager.

The stub of the documentation which may shed some light on the current design is available here (on branch /u/mxk62/graph).

ok, I'll take a look

Took a look, and added a couple of comments. Since this isn't yet a package which will be used in the stack, you don't have to have the standard up-directory layout, (ups/ directory with table file, etc), but keep in mind you'll have to add it later.

The only other functionality I can think that you might want to include is inputing YAML, however, I'm not sure if we've standardized on that in DM yet or not.

Support for YAML would be a nice feature indeed. However, I didn't come across a YAML-based graph format which would be close to a standard the way GraphML, GEXF (or even JSON-based node-link format) are.

Actually, networkx already has methods for reading and writing YAML files. However, what they really do is loading (or dumping) YAML representation of package's own, internal graph representation which can hardly be considered as a generic data exchange format.

I'll keep digging and definitely implement support for YAML when I find something more adequate.