Re: Simplicity
Benoit Grégoire <[email protected]> Thu, 31 Oct 2013 10:51:12 -0400
| Newsgroups | gmane.comp.finance.libofx.devel |
|---|---|
| Organization | Technologies Coeus inc. |
| Message-ID | <1614357.3SgJozoOrd@benoitg-laptop> |
--===============7430800935522270208==
Content-Type: multipart/signed; boundary="nextPart30744417.UcS6ggWT70";
micalg="pgp-sha1"; protocol="application/pgp-signature"
--nextPart30744417.UcS6ggWT70
Content-Type: multipart/alternative; boundary="nextPart4981600.u1cpVSTqLv"
Content-Transfer-Encoding: 7Bit
This is a multi-part message in MIME format.
--nextPart4981600.u1cpVSTqLv
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"
On October 27, 2013 04:18:01 PM Mike wrote:
> I'm interested about what the home page said about "Simplicity".
>=20
> Your page also says that convertion to .QIF looses information. So,
> .QIF is too simple, I take it.
>=20
> In the accounting data I will mess with, I'd like to not lose data. =
At
> the same time, I might like to prune away Quicken-isms or GnuCash-ism=
s
> from the data.
>=20
> Do you recommend subsets of .OFX? (Like what OpenGL ES did for=20
OpenGL?
No, I don't. =20
OFX is banking-transaction centric. While overly complex (otherwise li=
bofx=20
wouldn't need to exist), it probably wouldn't be that bad for exchangin=
g=20
transaction data if it were implemented properly (sadly it is not well=20=
implemented by banks either). What it is not at all meant to represent=
is=20
collections of general accounting data.
QIF, for all it's numerous faults, is actually not as bad as OFX for=20=
accounting data storage.
--=20
Benoit Gr=E9goire, ing., PMP, PSM
--nextPart4981600.u1cpVSTqLv
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html; charset="iso-8859-1"
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN" "http://www.w3.org/TR/=
REC-html40/strict.dtd">
<html><head><meta name=3D"qrichtext" content=3D"1" /><style type=3D"tex=
t/css">
p, li { white-space: pre-wrap; }
</style></head><body style=3D" font-family:'Monospace'; font-size:9pt; =
font-weight:400; font-style:normal;">
<p style=3D" margin-top:0px; margin-bottom:0px; margin-left:0px; margin=
-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">On =
October 27, 2013 04:18:01 PM Mike wrote:</p>
<p style=3D" margin-top:0px; margin-bottom:0px; margin-left:0px; margin=
-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">>=
; I'm interested about what the home page said about "Simplicity&q=
uot;.</p>
<p style=3D" margin-top:0px; margin-bottom:0px; margin-left:0px; margin=
-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">>=
; </p>
<p style=3D" margin-top:0px; margin-bottom:0px; margin-left:0px; margin=
-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">>=
; Your page also says that convertion to .QIF looses information. So,<=
/p>
<p style=3D" margin-top:0px; margin-bottom:0px; margin-left:0px; margin=
-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">>=
; .QIF is too simple, I take it.</p>
<p style=3D" margin-top:0px; margin-bottom:0px; margin-left:0px; margin=
-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">>=
; </p>
<p style=3D" margin-top:0px; margin-bottom:0px; margin-left:0px; margin=
-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">>=
; In the accounting data I will mess with, I'd like to not lose data. =
At</p>
<p style=3D" margin-top:0px; margin-bottom:0px; margin-left:0px; margin=
-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">>=
; the same time, I might like to prune away Quicken-isms or GnuCash-ism=
s</p>
<p style=3D" margin-top:0px; margin-bottom:0px; margin-left:0px; margin=
-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">>=
; from the data.</p>
<p style=3D" margin-top:0px; margin-bottom:0px; margin-left:0px; margin=
-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">>=
; </p>
<p style=3D" margin-top:0px; margin-bottom:0px; margin-left:0px; margin=
-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">>=
; Do you recommend subsets of .OFX? (Like what OpenGL ES did for OpenG=
L?</p>
<p style=3D"-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px=
; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0p=
x; "> </p>
<p style=3D" margin-top:0px; margin-bottom:0px; margin-left:0px; margin=
-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">No,=
I don't. </p>
<p style=3D"-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px=
; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0p=
x; "> </p>
<p style=3D" margin-top:0px; margin-bottom:0px; margin-left:0px; margin=
-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">OFX=
is banking-transaction centric. While overly complex (otherwise libof=
x wouldn't need to exist), it probably wouldn't be that bad for exchang=
ing transaction data if it were implemented properly (sadly it is not w=
ell implemented by banks either). What it is not at all meant to repre=
sent is collections of general accounting data.</p>
<p style=3D"-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px=
; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0p=
x; "> </p>
<p style=3D" margin-top:0px; margin-bottom:0px; margin-left:0px; margin=
-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">QIF=
, for all it's numerous faults, is actually not as bad as OFX for accou=
nting data storage.</p>
<p style=3D" margin-top:0px; margin-bottom:0px; margin-left:0px; margin=
-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">-- =
</p>
<p style=3D" margin-top:0px; margin-bottom:0px; margin-left:0px; margin=
-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">Ben=
oit Gr=E9goire, ing., PMP, PSM</p></body></html>
--nextPart4981600.u1cpVSTqLv--
--nextPart30744417.UcS6ggWT70
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part.
Content-Transfer-Encoding: 7Bit
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.14 (GNU/Linux)
iEYEABECAAYFAlJybmAACgkQmZ6zzPlLuwN9ZgCgr6rSaAsOmPbzkCDrq/IRdq0f
S3oAoJnCiFzBdWSty6Uu0uugXfIXfOk8
=2BU0
-----END PGP SIGNATURE-----
--nextPart30744417.UcS6ggWT70--
--===============7430800935522270208==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
------------------------------------------------------------------------------
Android is increasing in popularity, but the open development platform that
developers love is also attractive to malware creators. Download this white
paper to learn more about secure code signing practices that can help keep
Android apps secure.
http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk
--===============7430800935522270208==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
_______________________________________________
Libofx-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/libofx-devel
--===============7430800935522270208==--