Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Re: [xml-dev] DOM's javascript roots (was Re: [xml-dev] Have JDOM/ XOM / etc. failed?)

From: James Britt <jbritt@--------.--->
To: xml-dev@-----.---.---
Date: 4/1/2006 3:37:00 AM
Charles Woerner wrote:
...

> 
> Standardizing an API such as DOM across different languages is a nice
> goal.  When I see a few lines of XML traversing code written in Ruby
> using DOM I immediately know what it's doing despite the fact that I've
> never coded a line of Ruby in my life.  

But XML manipulation in Ruby will more than likely be done using REXML, 
Ruby's bundled XML parser.  It has a Ruby-centric API.

When the idea of having Ruby support XML "out of the box" first came up 
a few years ago, the discussion centered on two views: Should Ruby 
support the W3C DOM, requiring Rubyists to use a decidedly non-Ruby API 
for XML tasks, or should a bundled parser have an API that would be 
intuitive to reasonably experienced Ruby hacker?

The latter point of view won, and Ruby ships with REXML.

One *can* use libxml2 with Ruby, but I suspect this is selected over 
REXML only when speed or memory are issues.  For most day-to-day XML 
handling, I think people are choosing the API that best meshes with the 
language.


James Britt


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