Matt, James; When working with XML, version control features (such as comparing changes) is in general difficult, perhaps impossible. Note that databases have problems with these kinds of features as well.
One idea is to use n3 instead of XML. n3 has a much more regular structure and won't re-order resources in different ways. It may not be a full solution for your purposes but will get you a lot closer to the ability to, for example, compare file versions. -- Scott On Dec 4, 8:31 am, jlapalme <[EMAIL PROTECTED]> wrote: > Personnally, > > I have been searching for some time now and I have found nothing. > > If you are able to share your code for comparing two models, I would > be very greatful. > > Cheers, > > James > > On Dec 3, 5:25 pm, Matt <[EMAIL PROTECTED]> wrote: > > > Hey, hopefully someone in the community has solved this problem. We > > have several models that are large enough to still keep in a file > > system. We are versioning these models using SVN. JENA standard says > > that models do not have to be written out in any consistent order. As > > a result, SVN seems to just consider .owl files .xml files and > > explodes because the ordering of the .owl files changes anytime I add > > stuff to it (either in code or in TBC). > > > I have code that I can run to compare 2 models using JENA and tell me > > what statements are in one model but not in the other. So I can then > > manually merge the files. However, someone has to have done this in a > > more elegant and user friendly capacity. Perhaps extending the > > default comparison modules in subclipse/subversive? > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TopBraid Composer Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/topbraid-composer-users?hl=en -~----------~----~----~----~------~----~------~--~---
