>At this point, maybe everyone's waiting for the version 3 spec, which
>apparently includes useful I/O. Maybe it sounds pessimistic, but I
>wouldn't count on it being straightforward.
Serialization isn't; there are more legitimate options than you may
realize, and some language-independence concerns. But it really isn't bad.
If you want to see what solutions the DOM is considering, there _is_ a
public working draft available from the W3C's website. It may not be fully
up to date with deliberations inside the group, but it'll give you some
idea of where we're going. If you have concerns you think we may have
missed, there's a public DOM mailing list.
If your company is a W3C member, you can get access to the non-public
drafts as well and see what our very latest thoughts are. You could even
get involved in the DOM Interest Group and contribute to the design.
Don't assume. Investigate. If you don't like what you see, consider getting
involved now, while your comments can be incorporated into the design
debate, rather than waiting for it to get all the way through the process.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
