|
Rank: Newbie
Joined: 7/11/2017 Posts: 2 Location: Belgium
|
Good morning, We are really interested in your DiffDog program but we first need to check some functionalities. We are publishing XSDs zip regularly and we would like to be able to generate a report that would list all the changes made between the previous version of the XSDs and the new version. Our publication follow always the same folder structure like the one here under
XSD folder __document ____RequestStartAccess ______ebIX_MessageBusinessInformationEntities_RequestStartAccess_02-02p002.xsd ______ebIX_MessageDataType_RequestStartAccess_02-02p002.xsd ______ebIX_RequestStartAccess_02-02p002.xsd ____NotificationTicketProcessing ______ebIX_MessageBusinessInformationEntities_NotificationTicketProcessing_02-06p001.xsd ______ebIX_MessageDataType_NotificationTicketProcessing_02-06p001.xsd ______ebIX_NotificationTicketProcessing_02-06p001.xsd ____Message ... __generic ____5_000001_0p1pA.xsd ____5_BE000385_0p1pA.xsd ____260_000077_0p2pA.xsd ____...
But, as the version number is in the filename (the part in red in the example here above) we are not sure that your program will understand that he has to compare the 2 files. For the files that didn't changed between the 2 version of course there will not be any problem as the filename remains completely the same but for the ones that evolved the filename will be adapted.
On a clearer way, will DiffDog understand that he has to compare file from the following 2 folders structure?
Baseline: XSD folder __document ____RequestStartAccess ______ebIX_MessageBusinessInformationEntities_RequestStartAccess_02-02p002.xsd ______ebIX_MessageDataType_RequestStartAccess_02-02p002.xsd ______ebIX_RequestStartAccess_02-02p002.xsd ____NotificationTicketProcessing ______ebIX_MessageBusinessInformationEntities_NotificationTicketProcessing_02-06p001.xsd ______ebIX_MessageDataType_NotificationTicketProcessing_02-06p001.xsd ______ebIX_NotificationTicketProcessing_02-06p001.xsd ____Message ... __generic ____5_000001_0p1pA.xsd ____5_BE000385_0p1pA.xsd ____260_000077_0p2pA.xsd ____...
New Version: XSD folder __document ____RequestStartAccess ______ebIX_MessageBusinessInformationEntities_RequestStartAccess_02-02p003.xsd ______ebIX_MessageDataType_RequestStartAccess_02-02p003.xsd ______ebIX_RequestStartAccess_02-02p003.xsd ____NotificationTicketProcessing ______ebIX_MessageBusinessInformationEntities_NotificationTicketProcessing_02-07p001.xsd ______ebIX_MessageDataType_NotificationTicketProcessing_02-07p001.xsd ______ebIX_NotificationTicketProcessing_02-07p001.xsd ____Message ... __generic ____5_000001_1p0pA.xsd ____5_BE000385_0p1pA.xsd ____260_000077_0p3pA.xsd ____...
Thanks for your response
Have a nice day
Thibaut
|
|
Rank: Newbie
Joined: 10/28/2002 Posts: 1,283 Location: AT
|
Hi,
the files have to be named the same for comparison purposes. To make this work with Diffdog you would have to store the version number of the file in the schema file itself e.g. in a comment in the schema file , as opposed to storing the version number in the actual file name.
|
|
Rank: Newbie
Joined: 7/11/2017 Posts: 2 Location: Belgium
|
Thank you for your answer. Our file naming follows the Naming and Design Rules conventions for UMM2, the international standards from UN/CEFACT. Means that DiffDog is not the program we need. Have a nice day
Thibaut
|
|
Rank: Newbie
Joined: 9/10/2017 Posts: 1 Location: Hesperia Ca
|
Hellin_Th wrote:Good morning, We are really interested in your DiffDog program but we first need to check some functionalities. We are publishing XSDs zip regularly and we would like to be able to generate a report that would list all the changes made between the previous version of the XSDs and the new version. Our publication follow always the same folder structure like the one here under
XSD folder __document ____RequestStartAccess ______ebIX_MessageBusinessInformationEntities_RequestStartAccess_02-02p002.xsd ______ebIX_MessageDataType_RequestStartAccess_02-02p002.xsd ______ebIX_RequestStartAccess_02-02p002.xsd ____NotificationTicketProcessing ______ebIX_MessageBusinessInformationEntities_NotificationTicketProcessing_02-06p001.xsd ______ebIX_MessageDataType_NotificationTicketProcessing_02-06p001.xsd ______ebIX_NotificationTicketProcessing_02-06p001.xsd ____Message ... __generic ____5_000001_0p1pA.xsd ____5_BE000385_0p1pA.xsd ____260_000077_0p2pA.xsd ____...
But, as the version number is in the filename (the part in red in the example here above) we are not sure that your program will understand that he has to compare the 2 files. For the files that didn't changed between the 2 version of course there will not be any problem as the filename remains completely the same but for the ones that evolved the filename will be adapted.
On a clearer way, will DiffDog understand that he has to compare file from the following 2 folders structure?
Baseline: XSD folder __document ____RequestStartAccess ______ebIX_MessageBusinessInformationEntities_RequestStartAccess_02-02p002.xsd ______ebIX_MessageDataType_RequestStartAccess_02-02p002.xsd ______ebIX_RequestStartAccess_02-02p002.xsd ____NotificationTicketProcessing ______ebIX_MessageBusinessInformationEntities_NotificationTicketProcessing_02-06p001.xsd ______ebIX_MessageDataType_NotificationTicketProcessing_02-06p001.xsd ______ebIX_NotificationTicketProcessing_02-06p001.xsd ____Message ... __generic ____5_000001_0p1pA.xsd ____5_BE000385_0p1pA.xsd ____260_000077_0p2pA.xsd ____...
New Version: XSD folder __document ____RequestStartAccess ______ebIX_MessageBusinessInformationEntities_RequestStartAccess_02-02p003.xsd ______ebIX_MessageDataType_RequestStartAccess_02-02p003.xsd ______ebIX_RequestStartAccess_02-02p003.xsd ____NotificationTicketProcessing ______ebIX_MessageBusinessInformationEntities_NotificationTicketProcessing_02-07p001.xsd ______ebIX_MessageDataType_NotificationTicketProcessing_02-07p001.xsd ______ebIX_NotificationTicketProcessing_02-07p001.xsd ____Message ... __generic ____5_000001_1p0pA.xsd ____5_BE000385_0p1pA.xsd ____260_000077_0p3pA.xsd ____...
Thanks for your response
Have a nice day
Thibaut
|
|
guest |