Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Re: [xml-dev] Why XML for Messaging?

From: 'Liam Quin' <liam@--.--->
To: "Bullard, Claude L (Len)" <len.bullard@----------.--->
Date: 6/1/2005 7:09:00 PM
On Wed, Jun 01, 2005 at 01:54:27PM -0500, Bullard, Claude L (Len) wrote:
> Now that's the bid.  Still, no one has answered why I need 
> pointy brackets for that given comma-delimited ascii worked 
> just as well and is smaller.
It's not self-describing? (unless you have headers and then you
have to separate them from the data)....
It doesn't handle sub-structure?  Most database dumnps don't need
substructure, though...
There are better tools for handling XML, both at API level and
at user/data level?

Interoperability means being general, means being less specific,
means in general not being the best for the job at hand, but
good enough, but good enough for lots of jobs is sometimes
better than perfect for only one job.

Liam

-- 
Liam Quin, W3C XML Activity Lead, http://www.w3.org/People/Quin/
http://www.holoweb.net/~liam/


transparent
Print
Mail
Like It
Disclaimer
.

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.

.
.

transparent

transparent