office-collab — archive

[Robin LaFontaine]

I apologize for my lateness in commenting. It's taken quite a while to catch up from missing September. A few questions... In section 3 Definitions, #15 (caching deleted content) and #16 (caching attribute changes) each say that only one of the two methods (in situ vs. cached elsewhere) must be chosen. Can those choices be made independently or is the choice made once for both? Would an implementation need to apply an XSLT on every document load or parse the document before determining whether one is needed? There is no provision for a doc-level property indicating what storage choice was made and thus whether an implementation really needs to apply the XSLT. Of course, load code ought not blindly trust such a property anyway. What about SAX parsers? I believe applying an XSLT requires having the entire XML document in memory, which essentially implies DOM, or at least something DOM-like. If so, wouldn't that preclude an implementation from taking advantage of the performance and memory benefits of SAX streamed reading? Thanks, John