Oxygen XML Forum

My colleague and I get different results running the DITA Map Completeness Check with the same files, same oXygen version, same validation type (XML Schema) on two different machines/local drives. She gets a clean validation, but mine results in a list of errors that existed in long-ago file versions, not the current ones we're using. The result is the same regardless of whether I place files downloaded from source control in a new folder or place them in my existing development environment. Also, my build is clean. It seemed to happen out of the blue.

Any ideas what would cause this?

Hi Andrea,

The validate and check for completeness just parses the XML documents and then follows links between them. If it reports a problem in some content, then that content is there, on your local drive.
For example if you double click one of those reported problems, Oxygen will open that topic and you can see if the problem is still there or not.
Are you sure you opened the right map in the DITA Maps Manager? Maybe you opened a map from a previous branch of your project.

Regards,
Radu

I don't see how it's possible to have the wrong map. I have removed all other instances of the ditamap from my machine,restarted my machine, uninstalled/reinstalled oXygen 14.2, only to have the same problem. I'm also seeing "No profile" on my errors. What does that mean?

Hi Andrea,

The No profile part of the message means that you have not applied any specific profiling/filtering when validating the DITA Map. So it does not have any relation to your problem.

Please double click one of the errors and the corresponding topic will be opened in Oxygen. Then you can right click the opened editor's tab and choose "Copy location".
You can then paste this location in the Windows Explorer and navigate to the place where that topic was found by Oxygen. You can then open that topic in a different application (Notepad for example) and see if the problem is there or not.

Do you use a shared network drive to store all topics? Or some kind of version control like SVN or GIT?

Regards,
Radu

I'm concluding that we may have source control issues that caused this problem.

If you know how to eliminate the warning about the mailto: xref not having the correct format attribute--the one remaining map warning--please post it here.

Thank you for the support.

Hi,

A proper mailto reference should have the form:
We fixed in Oxygen 15.1 a problem of Oxygen incorrectly reporting mailto: xrefs as not valid.
So you should ignore that error reported in Oxygen 14.2 or upgrade to 15.1.

Regards,
Radu