Hi, first of all thanks for working on this Jo, had a look at the code and it seems quite fine.
Second I think your first version "[1]" was good, almost just fine and much better than the second. I would prefer having dxf as root but if you really really want to have isolated datavalusets I guess we can pipe the message through an xslt and end up with dxf since the datavalueset part can be similar. The important thing for me is that we have one parser. We will see enough complexity through maintenance of new minor/major versions of the format/parser and I would really like to only have one of these things to maintain:) Re the dxf objective there is no doubt that there is currently more use than complete serialization. To be concrete we can already create "tailored" export files through the detailed meta-data export UI, we do almost-full meta-data exports to update meta-data in different databases and in India/SL they do lots of exports of datavalues only between offline and online systems. Now we are sending datavaluesets. And I think all of these messages can belong in a common DXF2 schema. Anyway, I think this will be good. I am hoping you can take the effort to put it back to [1]. We can then build on the parser you have made to make it work with DXF 2 when we have more time. cheers Lars
_______________________________________________ Mailing list: https://launchpad.net/~dhis2-devs Post to : dhis2-devs@lists.launchpad.net Unsubscribe : https://launchpad.net/~dhis2-devs More help : https://help.launchpad.net/ListHelp
