Re: [xml-dev] Is CVS A Practical Means to Manage XML Versions In AProduc

["Ghislain Fourny" <gfourny@inf.ethz.ch>]

Hi David,

Yes, I share your vision - for example, one can imagine that eventually even programs (C++, Java) could be versioned on top of an XML layer (i.e., the abstract syntax tree is serialized as XML). It would mean that language constructs would be recognized and tracked, instead of lines of text.

Kind regards,
Ghislain


On Sep 20, 2011, at 2:29 PM, David Lee wrote:

> This thread got me thinking along with the recent thread on optimal xml
> editing.
> Imagine an editor where the only operations allowed are those specified by
> XQuery update.
> Now some of these would have to be 'chunked' up in the GUI as you probably
> don't want every single character entered doing an XQuery update ... so
> maybe an inline text field as you edit text and when you hit enter or tab or
> click out of it, it commits the edit.
> Otherwise the only edits which 'commit' are XQuery updates.
> 
> Combine this with the versioning history mechanism described in this thread
> (although likely much of it in memory unless the DB can keep up in
> real-time) ...  Or maybe a transactional model where you can 'undo' edits
> back to the last save point before they are 'live'.
> 
> For non-XML or for WYSIWYG documents the xml tags could be 'hidden' but
> still use the same technique.
> 
> Ok, I seriously don't know where I'm going with this but it's what I was
> thinking as I fell asleep last night :)
> 
> 
> 
> 
> 
> 
> 
> ----------------------------------------
> David A. Lee
> dlee@calldei.com
> http://www.xmlsh.org