| -----Original Message----- | From: [EMAIL PROTECTED] | [mailto:[EMAIL PROTECTED] | Behalf Of Lars Martin | Sent: donderdag 26 juli 2001 16:52 | To: [EMAIL PROTECTED] | Subject: Re: No xupdate:move element? | | Hi Jeroen, | thanks for reading (using?) the XUpdate specification. :-)
Hi Lars, I'm also working on a treediff algorithm to implement versioning on documents stored in our XML database. I want to use XUpdate (a part of it) to output the changes from one version to the other in human readable way. In the future we may allow clients to do XUpdate queries but for the moment it's only going to be used for output. | The spec was developed to provide an easy possibility to modify an | existing document. With this premise we decided to omit the "move" | method because one can achieve the same with "delete" and "insert". | You're certainly right that "move" could be faster the solution. | | The spec isn't finally, so why not extending the current spec in | the future? If there serious arguments for a "move" element I'm not | against an update. | | Lars One argument could be that it is a lot faster in DOM to move a child from one node to the other than it is to insert and delete nodes. I don't have any numbers on that, but I'm going to do some testing. Another arguments that's more important for use is that the representation of a move operation is smaller than the representation of a delete and insert, because the insert has to hold all the information that needs to be inserted. I'll be happy to help you extend to current spec. greetings, Jeroen ---------------------------------------------------------------------- Post a message: mailto:[EMAIL PROTECTED] Unsubscribe: mailto:[EMAIL PROTECTED] Contact adminstrator: mailto:[EMAIL PROTECTED] Read archived messages: http://archive.xmldb.org/ ----------------------------------------------------------------------
