Alan Jenkins | 2 Mar 2005 12:07
Picon

OFX versions

The README says the library is based on version 1.6 of the
specification, and I notice there are dtds for 1.6 and 2.01

Version 2.02 of the spec is now available, but I'm not bothered about
this since my bank (NatWest, a UK bank), uses version 1.02.

I haven't encountered any problems using libofx on these files (it uses
the 1.6 dtd), but I am curious as to whether it would be desirable
and/or possible to go the whole hog and provide dtds for every single
version of the published specification.

I think version 1.6 is when the switch from SGML to XML occurred (my
files are "OFXSGML").

Obviouslly the file format maintains a high degree of inter-version
compatability (I'm not sure whether the phrase I'm looking for is
forwards compatability or backwards compatability), so its probably not
important.

I ask because I'm working on a personal accounting program.  I'm trying
to write it in python, so I need to decide between making bindings for
libofx, parsing the results of ofxdump, or writing my own
implementation.  Flexibility is not a key concern - I just want
something that works for me.

Thanks!

Alan

-------------------------------------------------------
(Continue reading)

Benoit Grégoire | 2 Mar 2005 20:27
Picon
Picon

Re: OFX versions

On Wednesday 02 March 2005 06:07, Alan Jenkins wrote:
> The README says the library is based on version 1.6 of the
> specification, and I notice there are dtds for 1.6 and 2.01
>
> Version 2.02 of the spec is now available, but I'm not bothered about
> this since my bank (NatWest, a UK bank), uses version 1.02.
>
> I haven't encountered any problems using libofx on these files (it uses
> the 1.6 dtd), but I am curious as to whether it would be desirable
> and/or possible to go the whole hog and provide dtds for every single
> version of the published specification.
>
> I think version 1.6 is when the switch from SGML to XML occurred (my
> files are "OFXSGML").

<=1.6 is SGML, >=2.0 is XML

> Obviouslly the file format maintains a high degree of inter-version
> compatability (I'm not sure whether the phrase I'm looking for is
> forwards compatability or backwards compatability), so its probably not
> important.

De facto, OFX 1.6 is completely backward compatible and mostly forward 
compatible.  Ofx 2.0 isn't backward compatible.

> I ask because I'm working on a personal accounting program.  I'm trying
> to write it in python, so I need to decide between making bindings for
> libofx, parsing the results of ofxdump, or writing my own
> implementation.  Flexibility is not a key concern - I just want

(Continue reading)


Gmane