Hi, > I'm glad I could express myself a bit clearer this time:))) > > IMHO there's another argument: Remember how often people (me included ;) > had corruptive DBs. Such exports can make inspections less painful.
It would definitely help. >> Fine. Are you aware of any (more or less widespread) no xml based >> format (I am not sure if there is an standard) which would fit here? > > you mean in general or sport/geo-specific? Well in general: > > JSON > http://en.wikipedia.org/wiki/JSON > could fit. (I prefer to use it for my work / projects, where before > often CSV was established for data exchange) > > Pros: > - objects with their data attributes can easily be mapped to > - today python supports JSON out of the box, very easy to parse i.e. map > back to dictionaries etc. > - more human readable than XML (three exclamation marks ;) > - well established, non-exotic > > Cons: > - unlike CSV you cannot directly load it into some spreadsheet. So CSV > could still be useful. I was talking in general. Anyway, my concers were regarding how to display lap info within an activity, but after taking a look at layout shown in JSON's wikipedia page (I have always used it to exchange data, not taking into account any kind of nice representation), I think it will work pretty well. >> If not, there is always the option to export into GPX+ format >> including extensions for data like equipment. > > Good point, also thought about that. > Question: is a GPX+ without any geodata (ie waypoints) but extensions > also a valid one? If so one had to define a new schema to put in > <extensions>. Sure, why not? Currently GPX+ format is a valid one and include extension tags. Another different story would be if this kind of data is parsed if not expected, then it would depend on how "smart" parser is. > Nice about this approach is that all data of an activity would be > combined. Not so nice: this could become a real Frankenstein-GPX+ ;) > Hard to read and parse :/ Some people love xml files ;) (not me btw) > another option is: > YAML > http://en.wikipedia.org/wiki/YAML > pro & con somehow similar to JSON, but there is one interesting > difference: one can include any XML (e.g. gpx) *as is* into YAML. (in > JSON all " and \ will become escaped) No experience so far with it, but I would prefer to be consistent about format: xml based or text. > I also wonder whether other software (eg SportTracks) does have some > kind of exchange formats. No clue, never used. Regards, David ------------------------------------------------------------------------------ RSA® Conference 2012 Save $700 by Nov 18 Register now! http://p.sf.net/sfu/rsa-sfdev2dev1 _______________________________________________ Pytrainer-devel mailing list Pytrainer-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/pytrainer-devel
