Docbook Xinclude Link Validation

Having trouble installing Oxygen? Got a bug to report? Post it all here.
rawls
Posts: 2
Joined: Wed May 07, 2008 12:58 am

Docbook Xinclude Link Validation

Post by rawls »

I have searched the forums and can't find a solution to my problem.

I have a Docbook spread across multiple xml files, which are tied together in a main xml file using Xinclude. Now, each of the individual files have links that reference each other, however, Oxygen give a validation error for these links as there is no xinclude reference pointing each document to each other (this would repeat the text - all I want is the link id references). When I run the Docbook through Saxon/Fo (from a command line), html and pdf documents are created fine and correctly, so the the document appears to be valid.

My question is this - is there any way to let Oxygen know that link ids should be searched for from a pool of open (or project files)? Or, alternatively, can I shut off the checking of link ids? I tried to uncheck "Check ID/IDREF" box in the preferences>Xml>Xml Parser dialog, but the documents still don't validate.

If there is no way to do this, then it seems the only option is to put all of the docbook files in one gigantic XML file, which seems pretty ridiculous. Any help you can give me would be great.
rawls
Posts: 2
Joined: Wed May 07, 2008 12:58 am

Nevemind

Post by rawls »

Nevermind. I figured out that there is no real way to reliably validate this, in a general sense. Instead I am using Docbook's olink attribute to handle linking and to avoid validation errors.
sorin_ristache
Posts: 4141
Joined: Fri Mar 28, 2003 2:12 pm

Re: Docbook Xinclude Link Validation

Post by sorin_ristache »

Hello,
rawls wrote:I have a Docbook spread across multiple xml files, which are tied together in a main xml file using Xinclude. Now, each of the individual files have links that reference each other, however, Oxygen give a validation error for these links
...
My question is this - is there any way to let Oxygen know that link ids should be searched for from a pool of open (or project files)?
You should validate each XML file with a validation scenario which specifies the main XML file as the starting point for the validated XML document. When you create the validation scenario with the action Configure Validation Scenario available on the toolbar Validate and on the menu Document -> Validate just set the field URL of the file to validate of the validation scenario to the main XML file and associate the same validation scenario with each of the included XML files. When you press the Validate Document toolbar button the validation starts at the file specified in the validation scenario which is the main XML file so you will get no validation errors.


Regards,
Sorin
Post Reply