I like serialize myself! ;-) Scott Boag/CAM/Lotus wrote:
> The question is, when would the usage conflict? Semantically, what the two > are doing is the same. If you did node.writeObject, I would think the > default output would be an XML file... or at least it ought to be. The DOM > is an object (or at least it's implementation is) that holds state, and the > XML representation is a fine representation of that state. > > If you can think of another word instead of "serialize" that describes > writing a bunch of events, or a tree, to a stream... > > candidates: > linearize/linearizer - to give a linear form to; also : to project in > linear form > characterize/characterizer - I don't think this works > stream/streamer - hmm... > write/writer - you think we have problems with serialize... > > Linearize/linearizer might work. > > -scott > > > "Tom Palmer" > <[EMAIL PROTECTED] To: <[EMAIL PROTECTED]> > pia.com> cc: (bcc: Scott Boag/CAM/Lotus) > Subject: Re: [Proposal] Printer > package > 11/15/99 > 06:08 PM > Please > respond to > xerces-dev > > > > > people confuse because Java semantics are a bit different and more > > common. > > > The trick is having to cope with two groups using the same > word in slightly different ways, and any name picked that is > nice for Java may end up being bad for another language. > > It would be good to use the terms that the W3C uses. > > Adding a qualifier may help at times: DOM serialization vs. > Java serialization. Of course, this would only be useful for > normal conversation and so on. Package naming is a > different issue. > > - Tom Palmer
