I agree that under the appropriate circumstances you wouldn't have
to lock the whole document. However, were you to do the trick with
what is currently XSL, it seems to me that you would have to create
a _replacement_ document and then replace the original document.
If in the time between reading the original and generating the
replacement another user reads the original, and if you the other
user posts his replacement after you post your replacement, then
your changes do not take.
Or maybe you are suggesting there is no need to replace the whole
document using an XSL approach. XSL or some other XML standard would
need to define a standard mechanism for identifying and modifying a
portion of a document. I am aware of some sort of 'chunking'
initiative, but I don't know exactly what the scope of the effort is.
-- Joe Lapp (Java Apps Developer/Consultant) Unite for Java! - http://www.javalobby.org jlapp@acm.orgxml-dev: A list for W3C XML Developers. To post, mailto:xml-dev@ic.ac.uk Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ To (un)subscribe, mailto:majordomo@ic.ac.uk the following message; (un)subscribe xml-dev To subscribe to the digests, mailto:majordomo@ic.ac.uk the following message; subscribe xml-dev-digest List coordinator, Henry Rzepa (mailto:rzepa@ic.ac.uk)