xml-dev - Why do XML and OFX have subtle differences?

[Giovanni Flammia <flammia@sls.lcs.mit.edu>]

As I get more and more interested in XML and its applications beyond
GUIs,
I wonder why Open Financial Exchange (OFX) and XML have at least one
subtle difference that bothers me. The one difference that I see is this
one. When the data
being transmitted is a simple list of of key-value pairs, XML would do
it like this:

<userid>name</userid>
<userpassword>mypassword</userpassword>

or like this:

<userid value=name />
<userpassword value=mypassword />

(I personally prefer the <key>value</key> scheme, but that's just me)
while OFX would do it more parsimoniously as:

<userid>name
<userpassword>mypassword

Otherwise, the tagging scheme is pretty much compatible (correct me if
I'm wrong).

I think it would be highly desirable that either XML incorporates the
simpler OFX listing
with no ending tag, or OFX comply to XML. It seems to me that OFX is
gaining
wide industry support, so I propose that XML somehow incorporate a
provision to
list simple key-value pairs like OFX. Of course, I would be happy also
if OFX was going
to add those </tag> ending tags that are missing from their DTDs.

This way, XML can ride the wave started by OFX,
and XML developers can build OFX compliant tools with no worry.


Giovanni Flammia
flammia@sls.lcs.mit.edu
http://www.sls.lcs.mit.edu/flammia




begin:          vcard
fn:             Giovanni Flammia
n:              Flammia;Giovanni
org:            MIT LCS Spoken Language Systems
email;internet: flammia@sls.lcs.mit.edu
title:          Mr.
note:           Ciao
x-mozilla-cpt:  ;0
x-mozilla-html: TRUE
end:            vcard