Hi! My understanding is that using versioning system for XML requires some discipline, cause not all the changes in XML textual file are actually change the XML document.
Just google for "version control of xml documents" P.S. I found some tips regarding XML versioning from Oracle documentation useful for me: http://www.oracle.com/webapps/online-help/jdeveloper/10.1.3/state/content/navId.4/navSetId._/vtTopicFile.teamworking%7Cscs%7Cscs_u_writingversioncontrollablexml~html/ Best regards, Ivan On 2/23/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
I'm not really sure what you want exactly, however, the 'good for versioning' argument for XML you're quoting usually refers to its textual nature. Text files are very easy to maintain in a versioning system like subversion, perforce, or CVS, because with such a system you can turn back time and look at older versions of the file. Thing is, with a file in a textual format (like XML), you can use tools like Araxis Merge, WinDiff or TortoiseMerge to compare the files and get the changed lines highlighted. Also, since such a system typically only stores the differences, the repository (where all the data is stored) requires much less space. Xerces itself has no versioning support. If this is what you're looking for, you should have a look at http://www.subversion.org, which is a quite good open source versioning system. Uwe kaushik kaushik_zadoo-at-yahoo.com |xerces-c-users mailing list| schrieb: > I am a novice in XML and Xerces. I came to know that the main > advantage of XML is that we can work with multiple versions > of XML documents. We can do it either by having a seperate > Version Attribute in the XML or we can have a schema based > versioning system. But i could not find a good example for > doing(understand how to doit) it. > If you are aware of how to do it, it would be of great help if > you could share it with me or point me to some good web > links. > Thanks. > >
