[
Lists Home |
Date Index |
Thread Index
]
Good day!
(First, Tim, sorry for my laconic first post: I hit the sent button
before I intended to.)
As I said before, I have misgivings about not being able to specify the
encoding.
At a more fundamental level, it got me thinking that I personally doubt
I would use a XML API that is not bound to a parsing API.
I routinely pipe XML through successions of filters; XSLT being the
most obvious; I have appreciated some attempts at programmatic
filtering APIs (though I have not used them much)
I also often write programs that read a DOM, manipulate it and spit it
out.
Now, I am not saying there is not a good place for a simple XML writing
API: I also often need to take other data and XMLize it before running
it through the filters mentioned above...
But I would like the output of that library to be alternately a file, a
pipe, SAX events, maybe even a DOM tree...
anything that I can feed into other libraries that will read and
manipulate XML with minimal resources.
Would that distort the intent of the API beyond recognition?
Marc-Antoine
|
