XOM API for Processing XML with Java

["Bradley S. Huffman" <hip AT cs.okstate.edu>]

Elliotte Rusty Harold writes:

> At 2:38 PM -0500 7/7/03, Bradley S. Huffman wrote:
> 
> >As opposed to having complicated rules about when escaping will/will not
> >occur? Ok, then make it super simple, cr, lf, and such in attribute values
> >will always be escaped as char. ref. regradless of any other settings.
> 
> It's a question of where to put the complexity. Right now it's all 
> hidden from the end user. That proposal makes end users do a lot more 
> work to achieve the same affect. The internals of XOM are more 
> complex, but making the outer API look simple is hard work. That's no 
> surprise. The bottom line is that if XOM gets this right, then the 
> client should not need to worry or care about how XOM does it. It 
> should just work.

Okay, again, then forget what the serializer says the line seperator is
and always escape.  If you convert line breaks in attribute values to
whatever the serializer says is the current line seperator, what does the
end user gain? It displays better in Notepad?

Keep it simple, when you serialize and re-parse, what you put in attribute
values through calls to Attribute.setValue is what you'll get on the
other end through calls to Attribute.getValue.

Brad