*Displaying* the new extension and actually doing something with it are
*completely* different
things.
With XML programmers might save a bit of coding time in the parser when a new
extension arrives, but
ultimately someone has to code and produce a new version of the MTA which is
actually going to
implement the new extension. No matter how you transmit the data for the new
extension, that is the
inescapable reality.
Terry Fielder
Manager Software Development and Deployment
Great Gulf Homes / Ashton Woods Homes
terry(_at_)greatgulfhomes(_dot_)com
Fax: (416) 441-9085
-----Original Message-----
From: owner-ietf-mxcomp(_at_)mail(_dot_)imc(_dot_)org
[mailto:owner-ietf-mxcomp(_at_)mail(_dot_)imc(_dot_)org]On Behalf Of
Hallam-Baker,
Phillip
Sent: Tuesday, June 22, 2004 3:20 PM
To: 'Roy Badami'; Hallam-Baker, Phillip
Cc: 'terry(_at_)ashtonwoodshomes(_dot_)com'; 'IETF MARID WG'
Subject: RE: Why XML
With XML it is a simple matter to add a feature to the DNS retreive
tool to format the data in a comprehensible way - take a look at how
IE displays XML.
that is not possible with the SPF syntax unless the tool
understands the
version of the syntax used.
With XML - extensions to the data structure do not affect tools
With SPF - extensions to the data structure require all tools to be
rewritten